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