Josh Berkus <j...@agliodbs.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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
