Re: add list of major features to the v19 release notes

On Thu, Jul 02, 2026 at 01:15:39PM +0200, Michael Banck wrote:
> On Wed, Jul 01, 2026 at 04:38:14PM -0500, Nathan Bossart wrote:
>> + <listitem>
>> + <para>
>> + Logical replication now
>> + <link linkend="logical-replication-sequences">replicates sequence values</link>,
>> + and it can be enabled without a server restart when
>> + <xref linkend="guc-wal-level"/> is set to <literal>replica</literal>.
>> + </para>
>> + </listitem>
>
> Maybe it's because I'm not a native speaker, but I tripped over the
> second part and parsed it as a function of the replicate sequence
> values, not logical replication. Would it help readers to drop the "it",
> i.e. write "and can be enabled [...]"?

Fixed.

>> + <listitem>
>> + <para>
>> + Faster performance in many areas, including automatic scaling of the
>> + number of <link linkend="guc-io-max-workers">I/O worker processes</link>,
>> + quicker foreign-key checks, and further planning and execution
>> + optimizations.
>> + </para>
>> + </listitem>
>
> (This is kinda a catch-all statement and might go well as last item,
> dunno).

Moved.

>> + <listitem>
>> + <para>
>> + Data checksums can now be
>> + <link linkend="checksums-online-enable-disable">enabled or disabled while the database is running</link>.
>> + </para>
>> + </listitem>
>
> I think we still don't say "the database" when we talk about a
> server/instance/cluster. It should either be "the cluster" or "the
> database server".

Fixed.

>> + <listitem>
>> + <para>
>> + <xref linkend="sql-update"/> and <xref linkend="sql-delete"/> can now
>> + change or remove data for just part of a time range via the new
>> + <literal>FOR PORTION OF</literal> clause.
>> + </para>
>> + </listitem>
>
> I think this sentence should include something about temporal
> ranges/keys, or maybe just s/time range/temporal range/?

How about something like this?

Support for temporal updates and deletes via the new FOR PORTION OF
clause.

--
nathan