postmaster segfault with tsearch2?

Started by Matover 22 years ago2 messagesgeneral
Jump to latest
#1Mat
psql-mail@freeuk.com

Help!
Postmaster is segfaulting i think.
I am running RH_AS_3beta, postgresql 7.3.4 compiled from postgresql-7.3.
4-1PGDG.src.rpm on ia64 arch.

Tsearch2 compiled from tsearch-v2-stable.tar.gz

I have no idea how to fix it, all help gratefully received!

Potentially useful output below:

test# SELECT 'Our first string used today'::tsvector;
tsvector
---------------------------------------
'Our' 'used' 'first' 'today' 'string'
(1 row)

test=# SELECT to_tsvector( 'default', 'this is many words' );
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!#

LOG: server process (pid 7698) was terminated by signal 11
LOG: terminating any other active server processes
LOG: all server processes terminated; reinitializing shared memory and
semaphores
LOG: database system was interrupted at 2003-09-02 13:26:42 UTC
LOG: checkpoint record is at 0/967458
LOG: redo record is at 0/967458; undo record is at 0/0; shutdown TRUE
LOG: next transaction id: 581; next oid: 25098
LOG: database system was not properly shut down; automatic recovery in
progress
FATAL: The database system is starting up
LOG: ReadRecord: record with zero length at 0/9674A0
LOG: redo is not required
LOG: database system is ready

--

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Mat (#1)
Re: postmaster segfault with tsearch2?

psql-mail@freeuk.com writes:

Postmaster is segfaulting i think.
I am running RH_AS_3beta, postgresql 7.3.4 compiled from postgresql-7.3.
4-1PGDG.src.rpm on ia64 arch.

test=# SELECT to_tsvector( 'default', 'this is many words' );
server closed the connection unexpectedly

This is the same bug recently solved by Nigel Andrews. See his patch
just posted in pgsql-patches.

regards, tom lane