Horton

Re: default_text_search_config and expression indexes

Pavel Stehule <pavel.stehule@gmail.com>

View thread View on postgr.es
From: "Pavel Stehule" <pavel.stehule@gmail.com>
To: "Oleg Bartunov" <oleg@sai.msu.su>
Cc: "Bruce Momjian" <bruce@momjian.us>, "Tom Lane" <tgl@sss.pgh.pa.us>, "Michael Paesold" <mpaesold@gmx.at>, "Joshua D. Drake" <jd@commandprompt.com>, "Gregory Stark" <stark@enterprisedb.com>, "Teodor Sigaev" <teodor@sigaev.ru>, pgsql-hackers@postgresql.org
Date: 2007-07-27T07:15:18Z
Lists: pgsql-hackers 
2007/7/27, Oleg Bartunov <oleg@sai.msu.su>:
> On Fri, 27 Jul 2007, Pavel Stehule wrote:
>
> >>
> >>         1) Document the problem and do nothing else.
> >>         2) Make default_text_search_config a postgresql.conf-only
> >>            setting, thereby making it impossible to change by non-super
> >>            users, or make it a super-user-only setting.
> >>         3) Remove default_text_search_config and require the
> >>            configuration to be specified in each function call.
> >>
> >
> > Hello,
> >
> > 2+.
>
>
> One of the most important purpose of integrating tsearch2 was to
> facilitate full-text search for people in hosting environment. Usually,
> they have no superuser rights. I'm asking don't forget about them !
>
> There is no problem with current behaviour once user understand what he do.
>
>

I am not sure if postgresql is well for multilangual hosting
environment. There is problem with locales. Without COLLATE support
postgresql can't be used in similar environment. :(

nice a day
Pavel Stehule