Re: Why is get_actual_variable_range()'s use of SnapshotNonVacuumablesafe during recovery? - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Why is get_actual_variable_range()'s use of SnapshotNonVacuumablesafe during recovery?
Date
Msg-id CAH2-Wz=di9cyiqdby36YDKi4M33_U3KG-gzE3U7Uo-Mtm+h82Q@mail.gmail.com
Whole thread Raw
In response to Why is get_actual_variable_range()'s use of SnapshotNonVacuumablesafe during recovery?  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
On Wed, Nov 20, 2019 at 1:43 PM Peter Geoghegan <pg@bowt.ie> wrote:
> My understanding is that we can trust RecentGlobalXmin to be something
> useful and current during recovery, in general, so the selfuncs.c
> index-only scan (which uses SnapshotNonVacuumable + RecentGlobalXmin)
> can be trusted to work just as well as it would on the primary. Does
> that sound correct?

Nobody wants to chime in on this?

I would like to fix the nbtree README soon. It's kind of standing in
the way of my plan to finish off the work started by Simon's commit
3e4b7d87, and remove the remaining remnants of nbtree VACUUM "pin
scans". Apart from anything else, the current organisation of the code
is contradictory.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: non-exclusive backup cleanup is mildly broken
Next
From: Euler Taveira
Date:
Subject: Re: logical replication does not fire per-column triggers