Re: min_safe_lsn column in pg_replication_slots view - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: min_safe_lsn column in pg_replication_slots view
Date
Msg-id 20200622054950.GC50978@paquier.xyz
Whole thread Raw
In response to Re: min_safe_lsn column in pg_replication_slots view  (Michael Paquier <michael@paquier.xyz>)
Responses Re: min_safe_lsn column in pg_replication_slots view
List pgsql-hackers
On Sat, Jun 20, 2020 at 03:53:54PM +0900, Michael Paquier wrote:
> On Sat, Jun 20, 2020 at 09:45:52AM +0530, Amit Kapila wrote:
>> Isn't this information specific to checkpoints, so maybe better to
>> display in view pg_stat_bgwriter?
>
> Not sure that's a good match.  If we decide to expose that, a separate
> function returning a LSN based on the segment number from
> XLogGetLastRemovedSegno() sounds fine to me, like
> pg_wal_last_recycled_lsn().  Perhaps somebody has a better name in
> mind?

I was thinking on this one for the last couple of days, and came up
with the name pg_wal_oldest_lsn(), as per the attached, traking the
oldest WAL location still available.  That's unfortunately too late
for beta2, but let's continue the discussion.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Failures with wal_consistency_checking and 13~
Next
From: David Rowley
Date:
Subject: Re: Parallel Seq Scan vs kernel read ahead