Re: min_safe_lsn column in pg_replication_slots view
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, amit.kapila16@gmail.com, pgsql-hackers@postgresql.org
Date: 2020-06-19T12:15:52Z
Lists: pgsql-hackers
Attachments
- repslot-min-safe-cleanup.patch (text/x-diff) patch
On Fri, Jun 19, 2020 at 05:34:01PM +0900, Fujii Masao wrote: > On 2020/06/19 16:43, Kyotaro Horiguchi wrote: >> At Fri, 19 Jun 2020 16:36:09 +0900, Michael Paquier <michael@paquier.xyz> wrote in >>> So we usually avoid to do that between betas, but my take here is that >>> a catalog bump is better than regretting a change we may have to live >>> with after the release is sealed. > > Sounds reasonable. 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? (The change in catversion.h is a self-reminder.) -- Michael
Commits
-
Fix uninitialized value in segno calculation
- b5b4c0fef9fb 14.0 landed
- 794e8e32bb5a 13.0 landed
-
Morph pg_replication_slots.min_safe_lsn to safe_wal_size
- c54b5891f415 13.0 landed
- a8aaa0c786b3 14.0 landed