Re: Fixing GIN for empty/null/full-scan cases

Поиск
Список
Период
Сортировка
От David E. Wheeler
Тема Re: Fixing GIN for empty/null/full-scan cases
Дата
Msg-id 6459A15B-83B0-41D1-ADF3-4DEC6334C344@kineticode.com
обсуждение исходный текст
Ответ на Re: Fixing GIN for empty/null/full-scan cases  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Fixing GIN for empty/null/full-scan cases  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Дерево обсуждения 
On Jan 18, 2011, at 1:39 PM, Tom Lane wrote:

> At the moment my opinion is that gist__int_ops is too broken to be
> usable, and it's also too uncommented to be fixable by anyone other
> than the original author.

That seems to jibe with your comments from last year:
 http://archives.postgresql.org/pgsql-performance/2009-03/msg00265.php

Best,

David

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Fixing GIN for empty/null/full-scan cases