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

From Amit Kapila
Subject Re: min_safe_lsn column in pg_replication_slots view
Date
Msg-id CAA4eK1+O2yHQ6O4PYa=zjyazaZcD10SoAtR5DUbMTnC3_b1BxA@mail.gmail.com
Whole thread Raw
In response to Re: min_safe_lsn column in pg_replication_slots view  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: min_safe_lsn column in pg_replication_slots view
List pgsql-hackers
On Sat, Jun 20, 2020 at 7:12 AM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
>
> On 2020-Jun-19, Michael Paquier wrote:
>
> > If we want to make this happen, I am afraid that the time is short as
> > beta2 is planned for next week.  As the version will be likely tagged
> > by Monday US time, it would be good to get this addressed within 48
> > hours to give some room to the buildfarm to react.  Attached is a
> > straight-forward proposal of patch.  Any thoughts?
>
> I don't disagree with removing the LSN column, but at the same time we
> need to provide *some* way for users to monitor this, so let's add a
> function to extract the value they need for that.  It seems simple
> enough.
>

Isn't this information specific to checkpoints, so maybe better to
display in view pg_stat_bgwriter?

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: pg_regress cleans up tablespace twice.
Next
From: Michael Paquier
Date:
Subject: Re: pg_regress cleans up tablespace twice.