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

From Robert Haas
Subject Re: security labels on databases are bad for dump & restore
Date
Msg-id CA+Tgmoa9dS3+72fusCJ05f5_BgSp=JEsZYWsq80mh-9-8Hx4nw@mail.gmail.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
List pgsql-hackers
On Fri, Jul 10, 2015 at 7:57 AM, Andres Freund <andres@anarazel.de> wrote:
> pg_dump dumps security labels on databases. Which makes sense. The
> problem is that they're dumped including the database name.
>
> Which means that if you dump a database and restore it into a
> differently named one you'll either get a failure because the database
> does not exist, or worse you'll update the label of the wrong database.
>
> So I think we need CURRENT_DATABASE (or similar) support for security
> labels on databases.
>
> I won't have time to do anything about this anytime soon, but I think we
> should fix that at some point.  Shall I put this on the todo? Or do we
> want to create an 'open items' page that's not major version specific?

I think adding it to the TODO would be great.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: RFC: replace pg_stat_activity.waiting with something more descriptive
Next
From: Robert Haas
Date:
Subject: Re: RLS fails to work with UPDATE ... WHERE CURRENT OF