| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: min_safe_lsn column in pg_replication_slots view |
| Date: | 2020-06-20 04:15:52 |
| Message-ID: | CAA4eK1+O2yHQ6O4PYa=zjyazaZcD10SoAtR5DUbMTnC3_b1BxA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jun 20, 2020 at 7:12 AM Alvaro Herrera <alvherre(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-06-20 06:46:27 | Re: pg_regress cleans up tablespace twice. |
| Previous Message | Thomas Munro | 2020-06-20 03:01:36 | Re: pg_regress cleans up tablespace twice. |