Re: min_safe_lsn column in pg_replication_slots view
От | Kyotaro Horiguchi |
---|---|
Тема | Re: min_safe_lsn column in pg_replication_slots view |
Дата | |
Msg-id | 20200619.164304.392203744101291087.horikyota.ntt@gmail.com обсуждение исходный текст |
Ответ на | Re: min_safe_lsn column in pg_replication_slots view (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: min_safe_lsn column in pg_replication_slots view
|
Список | pgsql-hackers |
At Fri, 19 Jun 2020 16:36:09 +0900, Michael Paquier <michael@paquier.xyz> wrote in > 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. FWIW if we decide that it is really useless, I agree to remove it now. regards. -- Kyotaro Horiguchi NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: