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

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
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:57:53
Message-ID: 20170213165753.GR9812@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Frank,

* Frank van Vugt (ftm(dot)van(dot)vugt(at)foxi(dot)nl) wrote:
> 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 ;)

Yeah, I'll be including this in a regression test also, to make sure we
don't end up breaking this special case again in the future.

Thanks!

Stephen

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message François Beaulieu 2017-02-13 17:04:20 Re: Potential bug with pg_notify
Previous Message Frank van Vugt 2017-02-13 16:55:52 Re: intentional or oversight? pg_dump -c does not restore default priviliges on schema public