Re: PostgreSQL 12: Feature Highlights

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
Cc: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, pgsql-advocacy(at)lists(dot)postgresql(dot)org
Subject: Re: PostgreSQL 12: Feature Highlights
Date: 2019-05-18 02:30:17
Message-ID: 20190518023017.nkucoc5xgoebtvfw@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-hackers

On Sat, May 18, 2019 at 01:38:49PM +1200, David Rowley wrote:
> On Sat, 18 May 2019 at 03:36, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > Yes, it does. I added this text and moved the commit item:
> >
> > Avoid sorting when partitions are already being scanned in the
> > necessary order (David Rowley)
>
> Thank you for moving that out.
>
> > I certainly strugged to understand the maze of commits related to
> > partitioning.
>
> With the utmost respect, because I certainly do appreciate the work
> you did on the release note, I think if that's the case, then it
> should only make you more willing to listen to the advice from the
> people who are closer to those commits. However I understand that
> consistency is also important, so listening to the heckling of
> individuals sometimes won't lead to a good overall outcome. That
> being said, I don't think that's what happened here, as most of the
> people who had a gripe about it were pretty close to the work that was
> done.
>
> 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, as it
> means the people who are not in that group are left to look at the
> commit history to determine what's changed, or worse, they might just
> assume that the thing has not changed which could either cause them to
> 1) Skip the upgrade because it's not interesting to them, or; 2)
> having something break because we didn't list some incompatibility.
> I know you know better than most people that extracting a useful
> summary from the commit history is a pretty mammoth task, so I doubt
> we should put that upon the masses.

No one has suggested new wording, so I don't know what you are
complaining about. In fact, the wording we have now is by Amit Langote.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Magnus Hagander 2019-05-18 08:13:17 Re: PostgreSQL 12: Feature Highlights
Previous Message Peter Geoghegan 2019-05-18 01:47:37 Re: PostgreSQL 12: Feature Highlights

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2019-05-18 06:44:55 Re: pglz performance
Previous Message Andres Freund 2019-05-18 02:20:00 Re: Pluggable Storage - Andres's take