public inbox for [email protected]  

help / color / mirror / Atom feed

From: Laurenz Albe <[email protected]>
To: Jonathan S. Katz <[email protected]>
To: Bruce Momjian <[email protected]>
To: PostgreSQL-development <[email protected]>
Subject: Re: First draft of PG 17 release notes
Date: Fri, 20 Sep 2024 22:13:57 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Fri, 2024-09-20 at 13:47 -0400, Jonathan S. Katz wrote:
> Please see attached.

> +    <listitem>
> +     <para>
> +      Various query performance improvements, including to sequential reads
> +      using streaming I/O, write throughput under high concurrency, and
> +      searches over multiple values in a <link linkend="btree">btree</link>
> +      index.
> +     </para>
> +    </listitem>

Perhaps that last part could be "and searches over IN-lists in a b-tree index".
It might be technically less correct, but I'd expect that it gives more people
the right idea.

> +        <para>
> +         <link
> +          linkend="app-pgcreatesubscriber"><application>pg_createsubscriber</application></link>,
> +          a utility that logical replicas from physical standbys
> +        </para>

There's a verb missing: "a utility that *creates* logical replicas..."

> +        <para>
> +         <link
> +          linkend="pgupgrade"><application>pg_upgrade</application></link> now
> +          preserves replication slots on both publishers and subscribers
> +        </para>

I wonder if we should omit "on both publishers and subscribers".
It preserves replication slots anywhere, right?

> +    <listitem>
> +     <para>
> +      New client-side connection option, <link
> +      linkend="libpq-connect-sslnegotiation"><literal>sslnegotiation=direct</literal></link>,
> +      that allows direct TLS handshakes that avoids a round-trip negotation.
> +     </para>
> +    </listitem>

It should be "that avoid".  Plural.

Yours,
Laurenz Albe

view thread (146+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: First draft of PG 17 release notes
  In-Reply-To: <[email protected]>

* 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