Re: snapshot too old issues, first around wraparound and then more. - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: snapshot too old issues, first around wraparound and then more.
Date
Msg-id CACjxUsMKLpDO_-A8p_oyp3FGdRc02we3=CopsicMk0ELm_XCpw@mail.gmail.com
Whole thread Raw
In response to Re: snapshot too old issues, first around wraparound and then more.  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Wed, Apr 1, 2020 at 6:59 PM Andres Freund <andres@anarazel.de> wrote:
index fetches will never even try to
detect that tuples it needs actually have already been pruned away.

I looked at this flavor of problem today and from what I saw:

(1) This has been a problem all the way back to 9.6.0.
(2) The behavior is correct if the index creation is skipped or if enable_indexscan is turned off in the transaction, confirming Andres' analysis.
(3) Pruning seems to happen as intended; the bug found by Peter seems to be entirely about failing to TestForOldSnapshot() where needed.

--
Kevin Grittner
VMware vCenter Server
https://www.vmware.com/

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: WAL usage calculation patch
Next
From: Mark Dilger
Date:
Subject: Re: Should we add xid_current() or a int8->xid cast?