Re: PostgreSQL 12: Feature Highlights
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Bruce Momjian <bruce@momjian.us>
Cc: Peter Geoghegan <pg@bowt.ie>, Alvaro Herrera <alvherre@2ndquadrant.com>, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, David Rowley <david.rowley@2ndquadrant.com>, "Jonathan S. Katz" <jkatz@postgresql.org>, PostgreSQL Advocacy <pgsql-advocacy@lists.postgresql.org>
Date: 2019-05-17T03:50:12Z
Lists: pgsql-hackers
On Thu, May 16, 2019 at 10:21:35PM -0400, Bruce Momjian wrote: > I think we expect people to read them fully because how would they know > what changed and what new features were added. I do think allowing more > detail by showing the commit messages would be helpful for people who > want to drill down on an item. This point is interesting. The release notes include in the sgml sources references to the related commits. Could it make sense to have links to the main commits of a feature which can be clicked on directly from the html docs or such? I understand that producing the notes is a daunting task already, and Bruce does an awesome job. Just wondering if we could make that automated in some way if that helps with the user experience... Anyway, this is unrelated to the topic of this thread. My apologies for the digression. -- Michael
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