Re: pgsql: Remove QueryOperand->istrue flag, it was used only in cover - Mailing list pgsql-committers

From Teodor Sigaev
Subject Re: pgsql: Remove QueryOperand->istrue flag, it was used only in cover
Date
Msg-id 46E79BB9.2010100@sigaev.ru
Whole thread Raw
In response to Re: pgsql: Remove QueryOperand->istrue flag, it was used only in cover  ("Heikki Linnakangas" <heikki@enterprisedb.com>)
List pgsql-committers
> Nice, I played around that myself as well today. I tried to use
> Bitmapsets, instead of bool arrays, but that turned out to be
> significantly slower than the way it used to be. It looks like that
> bool-array method isn't, so that's good.
Yeah, hope so.
>
> Increasing the length field in QueryOperand doesn't actually help,
> because TSVector still only uses 11-bits for the length. And there's
> checks in tsquery.c that forbid values longer than MAXSTRLEN=2^11-1 anyway.
I know, but I doubt that rename istrue field to unused is much better.


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

pgsql-committers by date:

Previous
From: h-saito@pgfoundry.org (User H-saito)
Date:
Subject: psqlodbc - psqlodbc: Duplication deletion.
Next
From: mkz@pgfoundry.org (User Mkz)
Date:
Subject: pgbouncer - pgbouncer: fix check for authfile changes silly typo made