Re: Fixing GIN for empty/null/full-scan cases
От | Robert Haas |
---|---|
Тема | Re: Fixing GIN for empty/null/full-scan cases |
Дата | |
Msg-id | AANLkTimSzna-1tkQkWoBJUegkG4xNP3QvLR3vKtyNBA3@mail.gmail.com обсуждение исходный текст |
Ответ на | Fixing GIN for empty/null/full-scan cases (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Fixing GIN for empty/null/full-scan cases
|
Список | pgsql-hackers |
On Tue, Jan 4, 2011 at 4:09 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > * Existing GIN indexes are upwards compatible so far as on-disk storage > goes, but they will of course be missing entries for empty, null, or > null-containing items. Users who want to do searches that should find > such items will need to reindex after updating to 9.1. This is the only part of this proposal that bothers me a little bit. It would be nice if the system could determine whether a GIN index is "upgraded from 9.0 or earlier and thus doesn't contain these entries" - and avoid trying to use the index for these sorts of queries in cases where it might return wrong answers. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: