From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Subtle pg_dump problem... |
Date: | 2004-05-07 07:18:35 |
Message-ID: | 409B384B.2060104@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I have a table with a tsearch2 index on it. Now, I have all the
tsearch2 stuff installed into a 'contrib' schema. I have had to change
the default database schema to include the contrib schema as
behind-the-scenes, tsearch2 looks for its tables, and cannot find them
even if the function itself is schema-qualfified. This might well be a
tsearc2 bug.
Anyway, this means the table is dumped like this:
SET SESSION AUTHORIZATION 'auadmin';
SET search_path = public, pg_catalog;
COPY ...
Which give this error upon restoring:
ERROR: relation "pg_ts_cfg" does not exist
CONTEXT: COPY food_categories, line 1: "79 102 Vegetables,
Salads & Legumes \N 'legum':3 'salad':2 'veget':1"
It's because the search_path needs to be like this for it to work:
SET search_path = public, contrib, pg_catalog;
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2004-05-07 07:38:41 | Re: Subtle pg_dump problem... |
Previous Message | Vinay Jain | 2004-05-07 06:47:03 | Re: Is there any method to keep table in memory at startup |