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

From Andres Freund
Subject security labels on databases are bad for dump & restore
Date
Msg-id 20150710115735.GH26521@alap3.anarazel.de
Whole thread Raw
Responses Re: security labels on databases are bad for dump & restore
List pgsql-hackers
Hi,

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?

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: LANGUAGE sql functions don't use the custom plan logic
Next
From: Heikki Linnakangas
Date:
Subject: Re: Fillfactor for GIN indexes