From: | "Nikolay Samokhvalov" <samokhvalov(at)gmail(dot)com> |
---|---|
To: | "Teodor Sigaev" <teodor(at)sigaev(dot)ru> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: tsearch in core patch, for inclusion |
Date: | 2007-01-25 16:35:25 |
Message-ID: | e431ff4c0701250835j27d4ff83qbf3da6ad8b22f979@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On 1/25/07, Teodor Sigaev <teodor(at)sigaev(dot)ru> wrote:
> It's should clear enough for now - dump data from old db and load into new one.
> But dump should be without any contrib/tsearch2 related functions.
Upgrading from 8.1.x to 8.2.x was not tivial because of very trivial
change in API (actually not really API but the content of "pg_ts_*"
tables): russian snowball stemming function was forked to 2 different
ones, for koi8 and utf8 encodings. So, as I dumped my pg_ts_* tables
data (to keep my tsearch2 settings), I saw errors during restoration
(btw, why didn't you keep old russian stemmer function name as a
synonym to koi8 variant?) -- so, I had to change my dump file
manually, because I didn't manage to follow "tsearch2 best practices"
(to use some kind of "bootstrap" script that creates tsearch2
configuration you need from default one -- using several INSERTs and
UPDATEs). And there were no upgrade notes for tsearch2.
So, I consider upgrading process for tsearch2 to be a little bit
tricky till present. I assume it will be improved with 8.3...
--
Best regards,
Nikolay
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-01-25 16:46:15 | Re: WAL Record Header Size Reduction |
Previous Message | Ray Stell | 2007-01-25 16:33:29 | Re: [HACKERS] how to plan for vacuum? |
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2007-01-25 16:48:23 | Re: guid/uuid datatype |
Previous Message | Tom Lane | 2007-01-25 16:33:50 | Re: Getting rid of warnings |