On 12/8/06, Oleg Bartunov <oleg@sai.msu.su> wrote:
On Fri, 8 Dec 2006, Rajesh Kumar Mallah wrote:
> On 12/8/06, Oleg Bartunov <oleg@sai.msu.su> wrote:
>> On Fri, 8 Dec 2006, Rajesh Kumar Mallah wrote:
>>
>> > Dear
>> > Oleg,
>> > In local development server. the old functions still exists in
>> > postgresql catalogs. But probably they are missing in the
>> > newer version of tsearch2.so that came with 8.2.0 . And hence
>> > postgres is crashing. I feel this should have been informed in the
>> > release notes.
>>
>> yes, you're right. Someone has offered help to write this but then
>> silently dissapeared, so we stay without release notes. Could you
>> summarise your experience and write them and we add them for 8.2.1
>
> Sir,
>
> Dont you feel the incremental features should be available as upgrade
> patches. eg at one point of time i found that the = ( ts_vector ,
> ts_vector)
> operator is missing in my database. later i had to manually create
> the operator by looking at the tsearch2.sql file of later releases.
> this is becuse tsearch2.sql (i think) was not runnable on database
> having older versions of tsearch2.
> yes i would summarise my experience but lemme know if the above
> is an issue.
some people use separate scheme contrib to load all contrib stuff,
so upgrading is much easy.
Sir,
even with a seperate schema contrib one cannot drop the stuff
in contrib and reload the new version . Becoz DROPs have to be
cascaded to dependencies which contain real data. Eg
index and table columns that depend on existence of TYPE.
Regds
Mallah.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
