| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Legacy GiST invalid tuples |
| Date: | 2018-07-04 15:22:10 |
| Message-ID: | 66377.1530717730@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrey Borodin <x4mmm(at)yandex-team(dot)ru> writes:
> There is bunch of code in current GiST implementation checking for GistTupleIsInvalid(). PostgreSQL since 9.1 do not create invalid tuples. Should we support this tuples forever?
The question is not whether we still create such tuples. The reason
the code is still there is that an index that's been pg_upgraded from
before 9.1 might still contain such tuples. We can't drop the support
unless either we provide logic to clean up invalid entries, or we're
willing to force users to REINDEX old GiST indexes to get rid of them
that way. The latter seems like a pretty high price just to get rid of
some crufty old code.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2018-07-04 15:57:56 | Re: Legacy GiST invalid tuples |
| Previous Message | Peter Geoghegan | 2018-07-04 15:01:08 | Re: Locking considerations of REINDEX |