pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: michael@paquier.xyz
Cc: amit.kapila16@gmail.com
Cc: pgsql-hackers@postgresql.org
Subject: Re: min_safe_lsn column in pg_replication_slots view
Date: Fri, 19 Jun 2020 17:34:01 +0900
Message-ID: <81f74732-fca5-4f4b-1f52-645f84a8d9fa@oss.nttdata.com> (raw)
In-Reply-To: <20200619.164304.392203744101291087.horikyota.ntt@gmail.com>
References: <20200619013958.GC453547@paquier.xyz>
	<3b016893-9638-4f99-a1d0-bce007e8242a@oss.nttdata.com>
	<20200619073609.GF453547@paquier.xyz>
	<20200619.164304.392203744101291087.horikyota.ntt@gmail.com>



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
>> 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.

Sounds reasonable.

Regards,


-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION





view thread (72+ messages)  latest in thread

Message-ID: <81f74732-fca5-4f4b-1f52-645f84a8d9fa@oss.nttdata.com>
Permalink:  ../81f74732-fca5-4f4b-1f52-645f84a8d9fa@oss.nttdata.com/
Also on:    postgresql.org/message-id/81f74732-fca5-4f4b-1f52-645f84a8d9fa@oss.nttdata.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: masao.fujii@oss.nttdata.com, horikyota.ntt@gmail.com, michael@paquier.xyz, amit.kapila16@gmail.com
  Subject: Re: min_safe_lsn column in pg_replication_slots view
  In-Reply-To: <81f74732-fca5-4f4b-1f52-645f84a8d9fa@oss.nttdata.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox