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

From Andres Freund
Subject Re: security labels on databases are bad for dump & restore
Date
Msg-id 20150728191630.GG4726@alap3.anarazel.de
Whole thread Raw
In response to Re: security labels on databases are bad for dump & restore  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: security labels on databases are bad for dump & restore  (Stephen Frost <sfrost@snowman.net>)
Re: security labels on databases are bad for dump & restore  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 2015-07-28 15:14:11 -0400, Robert Haas wrote:
> On Tue, Jul 28, 2015 at 3:10 PM, Andres Freund <andres@anarazel.de> wrote:
> > DBA creates a database and sets some properties (security labels, gucs,
> > acls) on it. Then goes on to restore a backup. Unfortunately that backup
> > might, or might not, overwrite the properties he configured depending on
> > whether the restored database already contains them and from which
> > version the backup originates.
> 
> Well, I think that's just a potential incompatibility between 9.6 and
> previous versions, and a relatively minor one at that.  We can't and
> don't guarantee that a dump taken using the 9.3 version of pg_dump
> will restore correctly on any server version except 9.3.  It might
> work OK on a newer or older version, but then again it might not.

Even within a single major version it'll be a bit confusing that one
time a restore yielded the desired result (previously set property
survives) and the next restore it doesn't, because now the backup does
contain the property.



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: security labels on databases are bad for dump & restore
Next
From: Josh Berkus
Date:
Subject: Re: security labels on databases are bad for dump & restore