Re: [pgsql-advocacy] PostgreSQL 10: Call for Quotes - Mailing list pgsql-advocacy

From Joshua D. Drake
Subject Re: [pgsql-advocacy] PostgreSQL 10: Call for Quotes
Date
Msg-id a2c99917-6c31-f87d-af5c-588493dc6577@commandprompt.com
Whole thread Raw
In response to Re: [pgsql-advocacy] PostgreSQL 10: Call for Quotes  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: [pgsql-advocacy] PostgreSQL 10: Call for Quotes  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-advocacy
On 08/31/2017 08:32 AM, Simon Riggs wrote:
> On 26 July 2017 at 20:16, Jonathan S. Katz <jkatz@postgresql.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.   *****


pgsql-advocacy by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [pgsql-advocacy] PostgreSQL 10: Call for Quotes
Next
From: Robert Haas
Date:
Subject: Re: [pgsql-advocacy] PostgreSQL 10: Call for Quotes