Horton

Re: fine tune v11 release notes

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: "Jonathan S. Katz" <jkatz@postgresql.org>, pgsql-hackers@postgresql.org, Bruce Momjian <bruce@momjian.us>
Date: 2018-10-14T01:45:33Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Doc: still further copy-editing for v11 release notes.

  2. Doc: further copy-editing for v11 release notes.

  3. Doc: copy-editing for CREATE INDEX reference page.

Justin Pryzby <pryzby@telsasoft.com> writes:
> On Sat, Oct 13, 2018 at 05:31:46PM -0400, Tom Lane wrote:
>> I've pushed updates merging Jonathan's last with my work.  Please
>> look over what's in HEAD and see if you want to propose additional
>> changes.

> Find attached what's left.

I pushed some of this verbatim, tweaked some others, and left some
spots alone because I thought the existing wording was superior.

Notably, I ended up merging the two items about partitioned indexes and
rewriting them altogether, because it seemed more sensible to present it
that way.  See what you think.

Also, on the point of whether 11d8d72c2 requires a compatibility note,
I did think about that earlier today.  I think it's fine though; the
case in question is so odd that probably nobody's done it anyway.
We don't want the compatibility section to get impossibly long ...

			regards, tom lane