Re: PG 13 release notes, first draft - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: PG 13 release notes, first draft
Date
Msg-id 20200626202036.GA5474@alvherre.pgsql
Whole thread Raw
In response to Re: PG 13 release notes, first draft  (Bruce Momjian <bruce@momjian.us>)
Responses Re: PG 13 release notes, first draft  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Fabrízio de Royes Mello
Date:
Subject: Re: pg_dump bug for extension owned tables
Next
From: Tom Lane
Date:
Subject: Re: should libpq also require TLSv1.2 by default?