Re: default_text_search_config

>
> I'm not sure the locale per database solution is a silver bullet.
> With this, still we cannot solve the issue, for example, a LATIN1
> encoded text includes several languages at a time, thus it needs
> multiple locales. Or we cannot have multiple different language
> columns, tables at a time because it requires multiple locales. Same
> thing can be said to Unicode too. After all it seems a half baked
> solution to me.
> --

There is only one correct solution -> support of COLLATES. With
COLLATES you can choise locale per database, per table, per column,
per db operation. This is one point where PostgreSQL is late over
others.

Pavel Stehule