From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PG 13 release notes, first draft |
Date: | 2020-06-26 16:55:03 |
Message-ID: | 20200626165503.GB3337@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 26, 2020 at 05:24:16PM +0900, Masahiko Sawada wrote:
> Hi,
>
> I realized that PG 13 release note still has the following entry:
>
> <!--
> 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>
>
> <para>
> WHAT IS THIS ABOUT?
> </para>
> </listitem>
>
> </itemizedlist>
>
> 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.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2020-06-26 17:45:13 | Re: Default setting for enable_hashagg_disk |
Previous Message | Tom Lane | 2020-06-26 16:45:43 | Re: bugfix: invalid bit/varbit input causes the log file to be unreadable |