BUG #5561: Tsearch across schemas

From: "Satish Kumar" <satish(dot)kumar(at)icasework(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5561: Tsearch across schemas
Date: 2010-07-13 11:10:51
Message-ID: 201007131110.o6DBApRi096372@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 5561
Logged by: Satish Kumar
Email address: satish(dot)kumar(at)icasework(dot)com
PostgreSQL version: 8.2
Operating system: Ubuntu 9.04
Description: Tsearch across schemas
Details:

Hi,

We decided to use gist text search on two columns in our database (both on
different tables) and hence decided we required the tsearch2.sql
functionalities. We ran tsearch2.sql and create index across 5 schemas.

CREATE INDEX case_attributes_text ON case_attributes USING gist
(to_tsvector(value));

CREATE INDEX appl_categories_cat1 ON appl_categories USING gist
(to_tsvector(category1));

Thing seems to work fine until we encounter an occasion error message when
running our application and trying to insert into the appl_categories or
case_attributes table.

SEVERE: org.postgresql.util.PSQLException: ERROR: No tsearch cfg with id
698563
org.postgresql.util.PSQLException: ERROR: No tsearch cfg with id 698563

On further investigation we found out the OID 698563 was on pg_ts_cfg table
of a different schema.

Is there a known issue where even though we are passing in the right
search_path to point to the right schema, the index might fail to look into
the right schema for updating itself?

Regards,

Satish
iCasework Ltd.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Walker 2010-07-13 14:57:52 Fwd: Re: BUG #5556: "cannot drop active portal" and "ERRORDATA_STACK_SIZE exceeded" lead to server crash
Previous Message Shigeru Hanada 2010-07-13 10:31:50 BUG #5560: pg_dump generates invalid DDL