Re: Draft release notes for next week's releases

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Draft release notes for next week's releases
Date: 2021-11-06 02:48:48
Message-ID: 20211106024847.GH17618@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 05, 2021 at 08:27:49PM -0400, Tom Lane wrote:
> First draft is up at
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=39387228c8b7043d168bada0c64e9f59e83285f5
> As usual, please send any comments/corrections by Sunday.

+ one more row than requested, so tha it can determine whether the

A little typo: tha it

+ Ensure prepared transactions are properly accounted for during
+ promotion of a standby server (Michael Paquier, Andres Freund)

Ensure *that*

+ It seems unlikely that this bug has yet been hit in practice, as it

Remove "yet" ?

+ Previously this was allowed, but the collation effectively vanished
+ into the ether because of the way collation lookup works: you could
+ not use the collation, nor even drop it.

Is "vanished into the ether" normal language style for the release notes ?

+ <para>
+ Unnecessarily stupid back-tracking logic could result in exponential
+ time spent looking for a match. Fortunately the problem is masked
+ in most cases by other optimizations; but it is possible to
+ demonstrate it with fairly simple, if contrived, regexps.
+ </para>
+ </listitem>

Same - it seems like this borrows too much from the commit message text (and
style).

--
Justin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2021-11-06 02:51:12 amcheck's verify_heapam(), and HOT chain verification
Previous Message Tomas Vondra 2021-11-06 02:16:02 Re: [PATCH] Don't block HOT update by BRIN index