From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PG 13 release notes, first draft |
Date: | 2020-06-26 20:20:36 |
Message-ID: | 20200626202036.GA5474@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)alvh(dot)no-ip(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-06-26 20:22:37 | Re: should libpq also require TLSv1.2 by default? |
Previous Message | Fabrízio de Royes Mello | 2020-06-26 18:10:17 | Re: pg_dump bug for extension owned tables |