Re: PostgreSQL 12: Feature Highlights - Mailing list pgsql-advocacy

From Peter Geoghegan
Subject Re: PostgreSQL 12: Feature Highlights
Date
Msg-id CAH2-WznHtAuCcRMrNcocKNy1vN4w4e88d2XCT1fMMFnzjd-KiA@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL 12: Feature Highlights  (Michael Paquier <michael@paquier.xyz>)
Responses Re: PostgreSQL 12: Feature Highlights
List pgsql-advocacy
On Thu, May 16, 2019 at 4:52 PM Michael Paquier <michael@paquier.xyz> wrote:
> +1.  Another thing which may matter is that if some people do not see
> some improvements they were expecting then they can come back to pg13
> and help around with having these added.  Things are never going to be
> perfect for all users, and it makes little sense to make it sound like
> things are actually perfect.

Speaking of imperfections: it is well known that most performance
enhancements have the potential to hurt certain workloads in order to
help others. Maybe that was explicitly considered to be a good
trade-off when the feature went in, and maybe that was the right
decision at the time, but more often it was something that was simply
overlooked. There is value in leaving information that helps users
discover where a problem may have been introduced -- they can tell us
about it, and we can fix it.

I myself sometimes look through the release notes in an effort to spot
something that might have had undesirable side-effects, especially in
areas of the code that I am less knowledgeable about, or have only a
vague recollection of. Sometimes that is a reasonable starting point.

-- 
Peter Geoghegan



pgsql-advocacy by date:

Previous
From: Michael Paquier
Date:
Subject: Re: PostgreSQL 12: Feature Highlights
Next
From: Bruce Momjian
Date:
Subject: Re: PostgreSQL 12: Feature Highlights