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: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
