Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement - Mailing list pgsql-advocacy

From Josh Berkus
Subject Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement
Date
Msg-id 6dc3e28d-5df1-4fef-8057-f24ca855e84c@berkus.org
Whole thread Raw
In response to Re: [pgsql-advocacy] Assembling "top features" list for beta announcement  (Justin Clift <justin@postgresql.org>)
Responses Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement  (Michael Banck <michael.banck@credativ.de>)
List pgsql-advocacy
On 04/08/2017 12:53 PM, Justin Clift wrote:
> On 8 Apr 2017, at 20:48, Josh Berkus <josh@berkus.org> wrote:
> <snip>
>> From a PR standpoint, 5 is the absolute max, and 3 is better.  Really,
>> the ideal situation is a set of features which can be closely tied
>> together around a simple theme.
>
>  * Replication
>  * Performance
>  * Reliability

Well, if we take logical replication, quorum commit, connection failover
and partitioning, that together is a serious scale-out story.


--
Josh Berkus
Containers & Databases Oh My!


pgsql-advocacy by date:

Previous
From: Justin Clift
Date:
Subject: Re: [pgsql-advocacy] Assembling "top features" list for beta announcement
Next
From: Darren Duncan
Date:
Subject: Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement