Re: 8.2.6 > 8.3 blows up

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, 02 Mar 2008 15:46:25 -0600
Karl Denninger <karl(at)denninger(dot)net> wrote:

> I'm not quite clear what I have to do in terms of if/when I can drop
> the old tsearch config stuff and for obvious reasons (like not
> running into this in the future) I'd like to. Can I just run the
> "untsearch2" script against those databases or will that destroy the
> search functionality? Are there changes necessary in the SQL code
> (the documentation implies not unless I'm doing "odd" things)

One of the goals for 8.3 and the integrated tsearch was to remove
exactly this problem.

Sincerely,

Joshua D. Drake

- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHyzUtATb/zqfZUUQRAuyAAJ4vTqNjBvuNkyx2ygX55V3KPHxO+QCgl8yb
IAvNRUdlBg6G75KX9d95FiA=
=cqc6
-----END PGP SIGNATURE-----