Re: Tsearch2 dump/reload problem

From: Chris Gamache <cgg007(at)yahoo(dot)com>
To: Ian Barwick <barwick(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Tsearch2 dump/reload problem
Date: 2004-07-29 12:51:25
Message-ID: 20040729125125.73128.qmail@web13810.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

--- Ian Barwick <barwick(at)gmail(dot)com> wrote:

> I _think_ the way round this is to drop all the tsearch2 objects - you
> should have an untsearch2.sql file in a contrib directory somewhere
> which contains the appropriate statements. This does of course cascade
> to tsvector columns, which you will have to recreate and repopulate.
>
> FWIW I put all tsearch-related objects into their own schema, and
> recreate this before restoring other data to a fresh database.

Thank you. Dropping and re-loading tsearch2 objects worked like a charm.

The regprocedure_7.4.patch.gz actually works now! It's a great feature. I wish
I had noticed it sooner. I wonder why it didn't make it into pgsql-announce?

I am still considering your suggestion for putting the tsearch2 objects into
their own schema: Nice and clean.

CG


__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Parker 2004-07-29 14:17:53 tablespace spec
Previous Message LISTMAN 2004-07-29 12:38:19 Undefined symbol in plpgsql.so library