Re: pgsql: Fix memory arrangement of tsquery after removing stop words.

From: Teodor Sigaev <teodor(at)sigaev(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Fix memory arrangement of tsquery after removing stop words.
Date: 2008-03-09 10:46:25
Message-ID: 47D3C001.8060800@sigaev.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message User Gsmet 2008-03-09 14:26:28 pgfouine - pgfouine: Made date parsing more permissive
Previous Message Teodor Sigaev 2008-03-09 10:42:48 pgsql: Revert changes of CompareTSQ: it affects existing btree indexes.