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

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: pgsql: Remove QueryOperand->istrue flag, it was used only in cover
Дата
Msg-id 46E6DC9E.2000500@enterprisedb.com
обсуждение исходный текст
Ответ на pgsql: Remove QueryOperand->istrue flag, it was used only in cover  (teodor@postgresql.org (Teodor Sigaev))
Ответы Re: pgsql: Remove QueryOperand->istrue flag, it was used only in cover  (Teodor Sigaev <teodor@sigaev.ru>)
Список pgsql-committers
Teodor Sigaev wrote:
> Remove QueryOperand->istrue flag, it was used only in cover ranking
> (ts_rank_cd). Use palloc'ed array in ranking instead of flag.

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.

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.

--
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

В списке pgsql-committers по дате отправления:

Предыдущее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Sync timezone data with 2007g zic release.
Следующее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Give ICC its preferred, documented form of the no-strict-aliasing