Re: GIN - Generalized Inverted iNdex. Try 3.

Поиск
Список
Период
Сортировка
От Teodor Sigaev
Тема Re: GIN - Generalized Inverted iNdex. Try 3.
Дата
Msg-id 4450FB0B.2000301@sigaev.ru
обсуждение исходный текст
Ответ на Re: GIN - Generalized Inverted iNdex. Try 3.  (Alvaro Herrera <alvherre@commandprompt.com>)
Список pgsql-hackers
> How about adding a column to pg_am indicating "these indexes must always
> keep same tuple count as heap".  This would be true for all current AMs,
> false for GIN.

Yes, it's simplest solution, but it doesn't check of index consistency.

Possible, we can count number of itempointers to heap tuple during build/insert, 
and during bulkdelete we count number of deleted and leaved itempointers. So,

N[before bulkdelete] == N[after bulkdelete] + N[deleted]




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


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

Предыдущее
От: Taral
Дата:
Сообщение: Re: ANSI-strict pointer aliasing rules
Следующее
От: Zdenek Kotala
Дата:
Сообщение: AMD64 dual core mutex/spinlock problem