Re: Beta1 announcement: alpha1 draft

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Beta1 announcement: alpha1 draft
Date: 2016-04-26 18:27:44
Message-ID: 20160426182744.GD10850@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

* Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
> On Tue, Apr 26, 2016 at 1:58 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> > * Enable pg_dump ACL support
>
> I'm not entirely sure anyone will know what this is or why they should
> care. It might be worth mentioning if we can clarify that.

Err, worse, that particular comment is just wrong- pg_dump has supported
dumping ACLs for a very long time, we're just now supporting dumping
ACLs for objects in pg_catalog (and objects which are members of
extensions) which are changed from their default.

> Also note we now have:

Note sure why it isn't working at the moment (at least for me), but when
it does, you could also check out:

http://www.hagander.net/talks/

And look at Magnus' "A Look Inside the Elephant's Trunk - 9.6" talk.

> I think there are a decent number of people for whom the frozen page
> data in the visibility map will be a really big deal, even bigger than
> parallel query.

Agreed, for certain users, that's huge.

> And I think the combination of
> synchronous_commit=remote_apply and multiple synchronous standbys is
> also going to be really, really useful for anyone who wants to build a
> robust read-scaling cluster around PostgreSQL.

Agreed.

Thanks!

Stephen

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Joshua D. Drake 2016-04-26 18:34:28 Re: Beta1 announcement: alpha1 draft
Previous Message Robert Haas 2016-04-26 18:08:45 Re: Beta1 announcement: alpha1 draft