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

From Masahiko Sawada
Subject Re: PG 13 release notes, first draft
Date
Msg-id CA+fd4k62hYtce8VrEMGm6Y+1c24QBgCksXvOaH5kE8PbY+68sA@mail.gmail.com
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
List pgsql-hackers
Hi,

I realized that PG 13 release note still has the following entry:

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

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

Regards,

-- 
Masahiko Sawada            http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Ought to use heap_multi_insert() for pg_attribute/dependinsertions?
Next
From: Kasahara Tatsuhito
Date:
Subject: Re: Creating a function for exposing memory usage of backend process