Re: interval_ops shall stop using btequalimage (deduplication)
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Noah Misch <noah@leadboat.com>
Cc: pgsql-hackers@postgresql.org
Date: 2023-10-11T03:51:10Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Dissociate btequalimage() from interval_ops, ending its deduplication.
- bf1c21c4fad0 16.1 landed
- 782be0f7124a 15.5 landed
- 6fd1dbdb21cb 13.13 landed
- 0834df90942d 14.10 landed
- 5f27b5f848a4 17.0 landed
On Tue, Oct 10, 2023 at 8:29 PM Noah Misch <noah@leadboat.com> wrote: > My friend got an amcheck "lacks matching index tuple" failure, and they asked > me about it. I ran into the assertion failure while reproducing things. Reminds me of the time that amcheck found a bug in the default btree opclass for PostGIS's geography type. The opclass wasn't really intended to be used for indexing. The issue with the opclass (which violated transitive consistency) would probably never have been detected were it not for the tendency of PostGIS users to accidentally create useless B-Tree indexes on geography columns. Users sometimes omitted "using gist", without necessarily noticing that the index was practically useless. > > Do we really need to change the catalog contents when backpatching? > > Not really. I think we usually do. On the other hand, unlike some past > cases, there's no functional need for the catalog changes. The catalog > changes just get a bit of efficiency. No strong preference here. I'll defer to you on this question, then. I don't see any reason to delay committing your fix. The issue that you've highlighted is exactly the kind of issue that I anticipated might happen at some point. This seems straightforward. -- Peter Geoghegan