From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
cc: Frank van Vugt <ftm.van.vugt@foxi.nl>, pgsql-general@postgresql.org
Subject: Re: intentional or oversight? pg_dump -c does not restore default
 priviliges on schema public
In-reply-to: <20170211220617.GG9812@tamriel.snowman.net>
References: <3534542.o3cNaKiDID@techfox>
 <20170211220617.GG9812@tamriel.snowman.net>
Comments: In-reply-to Stephen Frost <sfrost@snowman.net>
	message dated "Sat, 11 Feb 2017 17:06:17 -0500"
Date: Sat, 11 Feb 2017 15:28:55 -0800
Message-ID: <3026.1486855735@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-general-owner@postgresql.org

Stephen Frost <sfrost@snowman.net> writes:
> I'm not seeing a very simple answer for this, unfortunately.

I'm inclined to argue that it was a mistake to include any non-pinned
objects in pg_init_privs.  The reason initdb leaves some objects unpinned
is exactly because they can be dropped and recreated, and that means
that their "initial" privileges are not static system properties.

We might need to fix pg_dump too, but I think these entries in
pg_init_privs should simply not be there.

			regards, tom lane


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general