Re: full text search in 8.3

From: "Nikolay Samokhvalov" <samokhvalov(at)gmail(dot)com>
To: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
Cc: andy <andy(at)squeakycode(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: full text search in 8.3
Date: 2007-10-11 14:20:42
Message-ID: e431ff4c0710110720q2e3e7768g7f57bd7ad794bf1b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/11/07, Florian G. Pflug <fgp(at)phlo(dot)org> wrote:
>
> Maybe we could document some regexp, awk script, or similar that strips the
> tsearch stuff from such a table of contents?

Just my .02c for those who will work on migration manual.

In my case, all tsearch2 stuff was kept (before 8.3) in separate
schema, namely "tsearch2". So, in 8.2, I had tsearch2.tsvector and
tsearch2.tsquery data types and so on.

During restoration to 8.3 I've catched segfaults -- during INSERTs
into tables with "tsearch2"."tsvector" columns. What helped me is the
following procedure:
1. restore schema only;
2. restore data with replacing "tsearch2"."tsvector" datatype to "tsvector":
sed -e 's/tsearch2\.tsvector/tsvector/g' DATADUMP | psql DBNAME
2>restoration_errors.log
3. drop "tsearch2" schema since it isn't needed anymore.

After that -- everything works normally.
My case is specific since I use separate schemas for every single
contrib module.
--
Best regards,
Nikolay

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 2007-10-11 14:24:22 Re: full text search in 8.3
Previous Message Tom Lane 2007-10-11 14:18:01 Re: Plan invalidation vs temp sequences