From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
Cc: | PostgreSQL Advocacy Group <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL 10: Call for Quotes |
Date: | 2017-08-31 15:38:27 |
Message-ID: | a2c99917-6c31-f87d-af5c-588493dc6577@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
On 08/31/2017 08:32 AM, Simon Riggs wrote:
> On 26 July 2017 at 20:16, Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
> Given this info also earlier noted this post
> https://www.infoq.com/news/2017/04/postgresql-10-features
>
> I propose the feature list as this
>
> * Logical Replication
> * Native Table Partitioning
> * Improved Query Parallelism
> * Quorum Commit for Synchronous Replication
> * SCRAM-SHA-256 strong authentication
>
> Any objection to me updating the docs to say that now, subject to
> further discussion?
I would argue that Traceable commit is just as interesting as Quorum
Commit (and likely applies to a larger audience). I would also argue
that SCRAM-SHA-256 isn't as "big feature" as we would like it to be as
we have supported strong authentication through external mechanisms for
a very long time.
Other than that, I have no comments and yes we should update the page.
JD
>
> It's better to have something in place soon, even if it is updated later.
>
--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
PostgreSQL Centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://pgconf.us
***** Unless otherwise stated, opinions are my own. *****
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-08-31 16:48:09 | Re: PostgreSQL 10: Call for Quotes |
Previous Message | Simon Riggs | 2017-08-31 15:32:53 | Re: PostgreSQL 10: Call for Quotes |