Re: PG 13 release notes, first draft

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: PG 13 release notes, first draft
Дата
Msg-id 20200626165503.GB3337@momjian.us
обсуждение исходный текст
Ответ на Re: PG 13 release notes, first draft  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
Ответы Re: PG 13 release notes, first draft  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список 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@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.

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@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: bugfix: invalid bit/varbit input causes the log file to be unreadable
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: Default setting for enable_hashagg_disk