Re: intentional or oversight? pg_dump -c does not restore default priviliges on schema public

From: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: intentional or oversight? pg_dump -c does not restore default priviliges on schema public
Date: 2017-02-13 16:55:52
Message-ID: 2623240.ZhDaCM8aGs@techfox
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Stephen,

Op maandag 13 februari 2017 09:10:42 schreef Stephen Frost:
> We should be able to get it addressed shortly.

Great, 'as always', I'd like to add!

Thanks for the great work, people. This cannot be stated too often...

> For your specific case

Thanks for the additional info, interesting.

> Yes, it's unfortunate that many users aren't really familiar with
> schema-level privileges.

Well, I didn't run into this issue with any of my db's that 'nicely' use
tables in various schema's, it was actually the one 'older' db with everything
in the public schema that brought it up, so maybe keeping one of those around
isn't too bad an idea ;)

--

Best,

Frank.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stephen Frost 2017-02-13 16:57:53 Re: intentional or oversight? pg_dump -c does not restore default priviliges on schema public
Previous Message Adrian Klaver 2017-02-13 16:45:07 Re: Potential bug with pg_notify