Re: Incorrect result of bitmap heap scan. - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Incorrect result of bitmap heap scan.
Date
Msg-id CAH2-WznOtpQ=Pb7cO2ppigR+UDpTTuRUmiND042mwM1P3pdLNw@mail.gmail.com
Whole thread Raw
In response to Re: Incorrect result of bitmap heap scan.  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Mon, Dec 2, 2024 at 3:56 PM Peter Geoghegan <pg@bowt.ie> wrote:
> I took what you wrote, and repurposed it to prove my old theory about
> GiST index-only scans being broken due to the lack of an appropriate
> interlock against concurrent TID recycling. See the attached patch.

BTW, if you change the test case to use the default B-Tree index AM
(by removing "USING GIST"), you'll see that VACUUM blocks on acquiring
a cleanup lock (and so the test just times out). The problem is that
GiST VACUUM just doesn't care about cleanup locks/TID recycling safety
-- though clearly it should.

--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Incorrect result of bitmap heap scan.
Next
From: Alena Rybakina
Date:
Subject: Re: Vacuum statistics