Re: Assembling "top features" list for beta announcement

From: Josh Berkus <josh(at)berkus(dot)org>
To: Justin Clift <justin(at)postgresql(dot)org>
Cc: Michael Banck <michael(dot)banck(at)credativ(dot)de>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Assembling "top features" list for beta announcement
Date: 2017-04-08 20:26:33
Message-ID: 6dc3e28d-5df1-4fef-8057-f24ca855e84c@berkus.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On 04/08/2017 12:53 PM, Justin Clift wrote:
> On 8 Apr 2017, at 20:48, Josh Berkus <josh(at)berkus(dot)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!

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Darren Duncan 2017-04-08 20:49:54 Re: Assembling "top features" list for beta announcement
Previous Message Justin Clift 2017-04-08 19:53:12 Re: Assembling "top features" list for beta announcement