Re: pgsql: Fix memory arrangement of tsquery after removing stop words. - Mailing list pgsql-committers

From Teodor Sigaev
Subject Re: pgsql: Fix memory arrangement of tsquery after removing stop words.
Date
Msg-id 47D3C001.8060800@sigaev.ru
Whole thread Raw
In response to Re: pgsql: Fix memory arrangement of tsquery after removing stop words.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
> The buildfarm indicates there's something wrong with the 8.3 version
> of this patch ...

Oh, my mistake. That means that patch of CompareTSQ should be reverted, because
it change comparing of existing tsquery (it's important for existing btree indexes).

Computing tsquery->size and length of tsquery instead of using stored values
causes the same effect: it will affect existing btree indexes.

However, Btree index over tsquery is not very useful. IMHO, the single purpose
is a guarantee unique of stored tsquery.


--
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
                                                    WWW: http://www.sigaev.ru/

pgsql-committers by date:

Previous
From: teodor@postgresql.org (Teodor Sigaev)
Date:
Subject: pgsql: Revert changes of CompareTSQ: it affects existing btree indexes.
Next
From: gsmet@pgfoundry.org (User Gsmet)
Date:
Subject: pgfouine - pgfouine: Made date parsing more permissive