Re: dumping database privileges broken in 9.6 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: dumping database privileges broken in 9.6
Date
Msg-id CA+TgmoZV-RioA4njyo6HGPJgG1p7wSLdQ9rdaVPfZ0fmhL6abg@mail.gmail.com
Whole thread Raw
In response to dumping database privileges broken in 9.6  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: dumping database privileges broken in 9.6  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Tue, Jun 28, 2016 at 11:12 PM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> Do this:
>
> CREATE DATABASE test1;
> REVOKE CONNECT ON DATABASE test1 FROM PUBLIC;
>
> Run pg_dumpall.
>
> In 9.5, this produces
>
> CREATE DATABASE test1 WITH TEMPLATE = template0 OWNER = peter;
> REVOKE ALL ON DATABASE test1 FROM PUBLIC;
> REVOKE ALL ON DATABASE test1 FROM peter;
> GRANT ALL ON DATABASE test1 TO peter;
> GRANT TEMPORARY ON DATABASE test1 TO PUBLIC;
>
> In 9.6, this produces only
>
> CREATE DATABASE test1 WITH TEMPLATE = template0 OWNER = peter;
> GRANT TEMPORARY ON DATABASE test1 TO PUBLIC;
> GRANT ALL ON DATABASE test1 TO peter;
>
> Note that the REVOKE statements are missing.  This does not correctly
> recreate the original state.

If I were a betting man, I'd bet that one of Stephen Frost's pg_dump
commits broke this.  But we'd have to bisect to be sure.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: pgbench unable to scale beyond 100 concurrent connections
Next
From: Stephen Frost
Date:
Subject: Re: dumping database privileges broken in 9.6