Re: Missing mapping in 8.3/tsearch2.sql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Missing mapping in 8.3/tsearch2.sql
Date: 2009-04-10 05:10:51
Message-ID: 13956.1239340251@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus <josh(at)agliodbs(dot)com> writes:
> The Tsearch2.sql compatibility fuctions in
> /contrib/tsearch2/tsearch2.sql don't include an important compatibility
> object. For 8.2 Tsearch2 usage, a lot of queries were written calling
> the "default" config, like:

> to_tsvector('default',somedata)

> In 8.3 this fails with a "No such config 'default'" error, even after
> loading the compatibility SQL. We need to add this to the compatibility
> SQL generation code:

No, we should not. It's up to the user to create a "default" config
that matches whatever they were using before.

Now, if you are volunteering to create a translation facility for the
whole contents of the old configuration tables, step right up and have
at it. But we should *not* insert a bogus substitute configuration.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2009-04-10 05:29:45 Re: Missing mapping in 8.3/tsearch2.sql
Previous Message Andrew Dunstan 2009-04-10 04:49:22 pg_restore dependencies