agora inbox for pgsql-hackers@postgresql.org
help / color / mirror / Atom feedFrom: Nathan Bossart <nathandbossart@gmail.com>
To: Michael Banck <mbanck@gmx.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: add list of major features to the v19 release notes
Date: Thu, 2 Jul 2026 09:36:46 -0500
Message-ID: <akZ3fkfhTe1C8iUm@nathan> (raw)
In-Reply-To: <6a46485d.2a10144b.ad66e.cd2bSMTPIN_ADDED_BROKEN@mx.google.com>
References: <akWIxtcathhoUuCQ@nathan>
<6a46485d.2a10144b.ad66e.cd2bSMTPIN_ADDED_BROKEN@mx.google.com>
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
Attachments:
[text/plain] v2-0001-Add-list-of-major-features-to-the-v19-release-not.patch (0B, ../akZ3fkfhTe1C8iUm@nathan/2-v2-0001-Add-list-of-major-features-to-the-v19-release-not.patch)
download
view thread (1366+ messages) latest in thread
Message-ID: <akZ3fkfhTe1C8iUm@nathan>
Permalink: ../akZ3fkfhTe1C8iUm@nathan/
Also on: postgresql.org/message-id/akZ3fkfhTe1C8iUm@nathan
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: nathandbossart@gmail.com, mbanck@gmx.net
Subject: Re: add list of major features to the v19 release notes
In-Reply-To: <akZ3fkfhTe1C8iUm@nathan>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox