Re: PG 16 draft release notes ready

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 16 draft release notes ready
Date: 2023-05-30 10:33:09
Message-ID: CAD21AoC+VihMWs3-xVB3Z=8LzLbsQc52TO29o25rzfqcnJDCUQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Thu, May 18, 2023 at 4:49 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> I have completed the first draft of the PG 16 release notes. You can
> see the output here:
>

I have one suggestion on this item:

<!--
Author: Amit Kapila <akapila(at)postgresql(dot)org>
2022-07-21 [366283961] Allow users to skip logical replication of data having o
Author: Amit Kapila <akapila(at)postgresql(dot)org>
2022-09-08 [875693019] Raise a warning if there is a possibility of data from m
-->

<listitem>
<para>
Allow logical replication subscribers to process only changes that
have no origin (Vignesh C, Amit Kapila)
</para>

<para>
This can be used to avoid replication loops.
</para>
</listitem>

I think it's better to mention the new 'origin' option as other new
subscription options are mentioned. For example,

<para>
This can be used to avoid replication loops. This can be controlled by
the subscription "origin" option.
</para>

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Drouvot, Bertrand 2023-05-30 10:34:30 Test slots invalidations in 035_standby_logical_decoding.pl only if dead rows are removed
Previous Message Dagfinn Ilmari Mannsåker 2023-05-30 10:28:24 Re: PG 16 draft release notes ready