Re: First-draft release notes for next week's back-branch releases - Mailing list pgsql-hackers

From Tom Lane
Subject Re: First-draft release notes for next week's back-branch releases
Date
Msg-id 22929.1462741017@sss.pgh.pa.us
Whole thread Raw
In response to Re: First-draft release notes for next week's back-branch releases  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: First-draft release notes for next week's back-branch releases  (Gavin Flower <GavinFlower@archidevsys.co.nz>)
Re: First-draft release notes for next week's back-branch releases  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
[ I think you meant to attach this to the other thread, but anyway... ]

"David G. Johnston" <david.g.johnston@gmail.com> writes:
> "...replacement_sort_tuples, which see for further details." needs
> rewording.

Hmm, "which see" is perfectly good English to my knowledge, and I'm not
sure that other possible ways of wording this would be less awkward.

> Is it worth mentioning the deprecation of exclusive backups in the notes
> introducing non-exclusive ones?

It's not clear to me that we're actually deprecating them; there did not
seem to be consensus on that.

I adopted your other suggestions.  Thanks for reviewing!
        regards, tom lane



pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: ALTER TABLE lock downgrades have broken pg_upgrade
Next
From: Clément Prévost
Date:
Subject: parallel.c is not marked as test covered