Re: PostgreSQL 12: Feature Highlights
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: David Rowley <david.rowley@2ndquadrant.com>
Cc: Bruce Momjian <bruce@momjian.us>,
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, "Jonathan S. Katz" <jkatz@postgresql.org>, PostgreSQL Advocacy <pgsql-advocacy@lists.postgresql.org>
Date: 2019-05-18T01:47:37Z
Lists: pgsql-hackers
On Fri, May 17, 2019 at 6:39 PM David Rowley <david.rowley@2ndquadrant.com> wrote: > FWIW, I do think the release notes should be meant as a source of > information which give a brief view on changes made that have a > reasonable possibility of affecting people (either negative or > positively) who are upgrading. Leaving out important details because > they might confuse a small group of people seems wrong-headed If the only thing that comes out of the developer meeting discussion item on release notes is that we make the commits behind each listing *discoverable* from the web, then that will still be a big improvement. I would prefer it if we went further, but that seems like it solves a lot of problems without creating new ones. -- Peter Geoghegan
Commits
-
doc: PG 12 relnotes, add mention of single-child optimization
- b9a0724cf7a3 12.0 landed
-
docs: split out sort-skip partition item in PG 12 release notes
- 05685897f07e 12.0 landed
-
docs: update partition item in PG 12 release notes
- 356c83795aaa 12.0 landed