Date: Fri, 26 Jun 2020 16:20:36 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Masahiko Sawada <masahiko.sawada@2ndquadrant.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 13 release notes, first draft
Message-ID: <20200626202036.GA5474@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20200626165503.GB3337@momjian.us>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On 2020-Jun-26, Bruce Momjian wrote:

> On Fri, Jun 26, 2020 at 05:24:16PM +0900, Masahiko Sawada wrote:

> > Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
> > 2020-03-20 [4e6209134] pg_dump: Add FOREIGN to ALTER statements, if appropriate
> > -->
> > 
> >       <para>
> >        Add <literal>FOREIGN</literal> to <command>ALTER</command> statements,
> >        if appropriate (Luis Carril)
> >       </para>

> > IIUC this entry is about that pg_dump adds FOREIGN word to ALTER TABLE
> > command. Please find the attached patch.
> 
> OK, so if that is, what used to happen before?  Did it still work
> without the FOREIGN keyword?  If so, I am thinking we should just remove
> this item.

I tend to agree, it's not a change significant enough to be documented
in the relnotes, i think.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services