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-19T07:36:09Z
Lists: pgsql-hackers
On Fri, Jun 19, 2020 at 04:13:27PM +0900, Fujii Masao wrote: > Agreed. But isn't it too late to remove the columns (i.e., change > the catalog) for v13? Because v13 beta1 was already released. > IIUC the catalog should not be changed since beta1 release so that > users can upgrade PostgreSQL without initdb. Catalog bumps have happened in the past between beta versions: git log -p REL_12_BETA1..REL_12_BETA2 src/include/catalog/catversion.h git log -p REL_11_BETA1..REL_11_BETA2 src/include/catalog/catversion.h git log -p REL_10_BETA1..REL_10_BETA2 src/include/catalog/catversion.h 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. -- 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