From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Frank van Vugt <ftm.van.vugt@foxi.nl>
Cc: pgsql-general@postgresql.org
Subject: Re: intentional or oversight? pg_dump -c does not restore default priviliges on schema public
Date: Sat, 11 Feb 2017 15:28:55 -0800
Message-ID: <3026.1486855735@sss.pgh.pa.us> (raw)
In-Reply-To: <20170211220617.GG9812@tamriel.snowman.net>
References: <3534542.o3cNaKiDID@techfox>
<20170211220617.GG9812@tamriel.snowman.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-general>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, sfrost@snowman.net, ftm.van.vugt@foxi.nl
Subject: Re: intentional or oversight? pg_dump -c does not restore default priviliges on schema public
In-Reply-To: <3026.1486855735@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox