X-Original-To: pgsql-bugs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 84BF2D1B1A5; Fri, 25 Jun 2004 04:00:19 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 29296-01; Fri, 25 Jun 2004 06:59:58 +0000 (GMT) Received: from matrix.gatewaynet.com (matrix.gatewaynet.com [217.19.69.50]) by svr1.postgresql.org (Postfix) with ESMTP id D1105D1B267; Fri, 25 Jun 2004 03:59:51 -0300 (ADT) Received: from matrix.gatewaynet.com (localhost.localdomain [127.0.0.1]) by matrix.gatewaynet.com (8.12.8/8.12.8) with ESMTP id i5P68DeR008563; Fri, 25 Jun 2004 09:08:13 +0300 Received: from localhost (achill@localhost) by matrix.gatewaynet.com (8.12.8/8.12.8/Submit) with ESMTP id i5P68DjO008559; Fri, 25 Jun 2004 09:08:13 +0300 Date: Fri, 25 Jun 2004 09:08:13 +0300 (EEST) From: Achilleus Mantzios To: pgsql-general@postgresql.org Cc: pgsql-bugs@postgresql.org Subject: tsearch2,pgsql 7.4.[1|2], pg_dump problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/142 X-Sequence-Number: 8566 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