From: Achilleus Mantzios <achill@matrix.gatewaynet.com>
To: pgsql-general@postgresql.org
Cc: pgsql-bugs@postgresql.org
Subject: tsearch2,pgsql 7.4.[1|2], pg_dump problem
Date: Fri, 25 Jun 2004 09:08:13 +0300 (EEST)
Message-ID: <Pine.LNX.4.44.0406250859340.8529-100000@matrix.gatewaynet.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0406161511460.2590-100000@matrix.gatewaynet.com>
Hi, i noticed a failure when i pg_dump/reload a database with tsearch2.sql
installed.
I get ERRORS of the type:
dynacom=# SELECT lexize('en_stem','foo bar');
ERROR: cache lookup failed for function 4652394
dynacom=# SELECT lexize('en_stem','foo bar');
ERROR: cache lookup failed for function 4652394
dynacom=# SELECT lexize('en_stem','foo bar');
ERROR: cache lookup failed for function 4652394
dynacom=# SELECT lexize('en_stem','foo bar');
ERROR: cache lookup failed for function 4652394
dynacom=#
dynacom=# SELECT to_tsvector('default','foo bar');
ERROR: cache lookup failed for function 4652424
dynacom=# SELECT to_tsvector('default','foo bar');
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.
!>
!>
!> \q
Always the 1st call in a session to to_tsvector gives:
ERROR: cache lookup failed for function 4652424
and the very next call in the same session causes the postmaster
to SEGV.
This situation is demonstrated in FreeBSD 5.1-RELEASE-p10, pgsql 7.4.1
and in Debian 2.4.18-bf2.4, pgsql 7.4.2.
A workaround is to first load tsearch2.sql script in the newly created
database, reload the dump, and ignore any tsearch2 subsequent ERRORS.
Anyone has a clue?
--
-Achilleus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: achill@matrix.gatewaynet.com, pgsql-general@postgresql.org, pgsql-bugs@postgresql.org
Subject: Re: tsearch2,pgsql 7.4.[1|2], pg_dump problem
In-Reply-To: <Pine.LNX.4.44.0406250859340.8529-100000@matrix.gatewaynet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox