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

From Kevin Grittner
Subject Re: [pgsql-advocacy] Assembling "top features" list for beta announcement
Date
Msg-id CACjxUsMunjmxTXQiu5fYuoiyUdcsb0hQb+KP-=sucVw_NtMpvg@mail.gmail.com
Whole thread Raw
In response to [pgsql-advocacy] Assembling "top features" list for beta announcement  (Josh Berkus <josh@berkus.org>)
Responses Re: [pgsql-advocacy] Assembling "top features" list for beta announcement  (Thomas Kellerer <spam_eater@gmx.net>)
Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement  (Andreas Karlsson <andreas@proxel.se>)
List pgsql-advocacy
On Fri, Apr 7, 2017 at 11:39 AM, Josh Berkus <josh@berkus.org> wrote:

> While 10 isn't 100% baked yet, I'd like to get started sorting out what
> our "top 2-4" features for the beta announcement are going to be.
> Traditionally, we've mentioned two to four features in detail, together
> with a bullet list of other significant features.  With the help of PVH,
> here's what I have so far:
>
> Banner features:
>
> - pglogical logical replication
> - table partitions in core
>
> Significant features:
>
> - XMLTABLE query expressions
> - hash indexes in wal
> - PGFDW: push down aggregates

> Notable note: pg_xlog => pg_wal
>
> So .., please add to the above lists.  Thanks!

I don't think it merits top 2-4 features, but transition tables for
AFTER triggers is a SQL standard feature that I think most products
have had and we have not ... until v10.

--
Kevin Grittner


pgsql-advocacy by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement
Next
From: Peter Geoghegan
Date:
Subject: Re: [pgsql-advocacy] Assembling "top features" list for beta announcement