Re: security labels on databases are bad for dump & restore - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: security labels on databases are bad for dump & restore
Date
Msg-id 55B7D5A5.1010908@agliodbs.com
Whole thread Raw
In response to security labels on databases are bad for dump & restore  (Andres Freund <andres@anarazel.de>)
Responses Re: security labels on databases are bad for dump & restore  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 07/28/2015 11:58 AM, Robert Haas wrote:
> I'd be strongly in favour of teaching GRANT, SECURITY LABEL, COMMENT
>> ON DATABASE, etc to recognise CURRENT_DATABASE as a keyword. Then
>> dumping them in pg_dump --create, and in pg_dump -Fc .
>>
>> In practice I see zero real use of pg_dumpall without --globals-only,
>> and almost everyone does pg_dump -Fc . I'd like to see that method
>> case actually preserve the whole state of the system and do the right
>> thing sensibly.
>>
>> A pg_restore option to skip database-level settings could be useful,
>> but I think by default they should be restored.

+++++1

Let's get rid of pg_dumpall -g.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: security labels on databases are bad for dump & restore
Next
From: Stephen Frost
Date:
Subject: Re: security labels on databases are bad for dump & restore