Re: Draft release notes for next week's releases

Поиск
Список
Период
Сортировка
Искать
От
Justin Pryzby
Тема
Re: Draft release notes for next week's releases
Дата
Msg-id
20211106024847.GH17618@telsasoft.com
Ответ на
Список
Дерево обсуждения
Draft release notes for next week's releases Tom Lane <tgl@sss.pgh.pa.us>
Re: Draft release notes for next week's releases Justin Pryzby <pryzby@telsasoft.com>
Re: Draft release notes for next week's releases Tom Lane <tgl@sss.pgh.pa.us>
Re: Draft release notes for next week's releases Peter Geoghegan <pg@bowt.ie>
Re: Draft release notes for next week's releases Tom Lane <tgl@sss.pgh.pa.us>
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 ?

+     
+      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.
+     
+    

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

-- 
Justin


В списке pgsql-hackers по дате отправления
От: Tomas Vondra
Дата:
От: Peter Geoghegan
Дата:
FAQ