Re: tsearch in core patch, for inclusion
От | Jeremy Drake |
---|---|
Тема | Re: tsearch in core patch, for inclusion |
Дата | |
Msg-id | Pine.BSO.4.64.0701241128590.23712@resin.csoft.net обсуждение исходный текст |
Ответ на | Re: tsearch in core patch, for inclusion (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: tsearch in core patch, for inclusion
Re: tsearch in core patch, for inclusion Re: tsearch in core patch, for inclusion |
Список | pgsql-hackers |
On Wed, 24 Jan 2007, Peter Eisentraut wrote: > Teodor Sigaev wrote: > > If there aren't objections then we plan commit patch tomorrow or > > after tomorrow. > > I still haven't heard any argument for why this would be necessary or > desirable at all, other than that it looks better for marketing > reasons, which I will counter by saying that it looks worse for > marketing reasons because our hailed plugin mechanism is apparently so > poor that it can't support some practical extension module such as > this. I for one am greatly looking forward to tsearch2 being in core. I was very fond of the plugin mechanism, until I signed up with a hosting provider. I do not have superuser privileges on the database cluster, and they will not install any plugins due to unspecified "security concerns". So ATM if I want full text indexing, my only choice would be to avail myself of their mysql instance which has it built in. So I have been jaded, and my opinion of optional plugins has gone from "wow, this is neat" to "man, this is a pain". They do not install plpgsql so I cannot write any triggers, they don't install tsearch2 so I don't get full text indexing, so all of the great features of postgres I have come to enjoy on my own box are suddenly taken away :( Sorry for the rant, I am just looking forward to 8.3 so I could get full text indexing... -- ARCHDUKE FERDINAND FOUND ALIVE -- FIRST WORLD WAR A MISTAKE
В списке pgsql-hackers по дате отправления: