Re: default_text_search_config and expression indexes
От | Pavel Stehule |
---|---|
Тема | Re: default_text_search_config and expression indexes |
Дата | |
Msg-id | 162867790707270015t13ddfc5ar47ef41382afa0ac0@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: default_text_search_config and expression indexes (Oleg Bartunov <oleg@sai.msu.su>) |
Ответы |
Re: default_text_search_config and expression indexes
|
Список | 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
В списке pgsql-hackers по дате отправления: