From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PG 10 release notes |
Date: | 2017-04-25 15:01:57 |
Message-ID: | 20170425150157.GO7513@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 25, 2017 at 06:51:47AM +0200, Petr Jelinek wrote:
> On 25/04/17 03:31, Bruce Momjian wrote:
> > I have committed the first draft of the Postgres 10 release notes. They
> > are current as of two days ago, and I will keep them current. Please
> > give me any feedback you have.
> >
>
> Cool!
>
> > The only unusual thing is that this release has ~180 items while most
> > recent release have had ~220. The pattern I see that there are more
> > large features in this release than previous ones.
> >
>
> Well I think for example
>
> > Optimizer
> >
> > Add the ability to compute a correlation ratio and the number of distinct values on several columns (Tomas Vondra, David Rowley)
> >
>
> could be easily 2 or 3 items (explicitly defining additional statistics,
> multicolumn ndistinct and functional dependencies).
Yes, we have more wholistic improvements that are made of many complex
parts, e.g. logical replication, partitioning.
> I also wonder if ability to run SQL queries on walsender connected to a
> database is worth mentioning (replication=database kind of connection).
Uh, why would that be important to users?
> Or the ability of logical decoding to follow timeline switches.
I didn't think logical decoding was really more than a proof-of-concept
until now.
--
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 | 2017-04-25 15:03:13 | Re: PG 10 release notes |
Previous Message | Daniel Gustafsson | 2017-04-25 15:00:42 | Re: A note about debugging TAP failures |