From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, "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-17 01:27:40 |
Message-ID: | 20190517012740.ntgy4pfgib63blds@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
On Thu, May 16, 2019 at 03:08:06PM -0400, Alvaro Herrera wrote:
> On 2019-May-16, Bruce Momjian wrote:
>
> > I think the more specific we make the partition description, the more
> > limited it will appear to be. I think almost all partition operations
> > will appear to be faster with PG 12, even if users can't articulate
> > exactly why.
>
> I don't understand why you want to make things such black boxes. It is
> what it is, and some users (not all) will want to understand. People
> who have already tested pg11 and found it insufficient may give pg12 a
> second look if we tell them we have fixed the deficiencies they found.
The release notes are written so it is clear to the average reader, and
is as short as it can be while remaining clear. If there is some other
criteria the community wants to use, I suggest you start a thread on the
hackers list.
--
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 +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2019-05-17 01:29:10 | Re: PostgreSQL 12: Feature Highlights |
Previous Message | Peter Geoghegan | 2019-05-17 00:05:13 | Re: PostgreSQL 12: Feature Highlights |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2019-05-17 01:29:10 | Re: PostgreSQL 12: Feature Highlights |
Previous Message | Kyotaro HORIGUCHI | 2019-05-17 01:24:25 | Re: VACUUM fails to parse 0 and 1 as boolean value |