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

From Alvaro Herrera
Subject Re: security labels on databases are bad for dump & restore
Date
Msg-id 20150715090440.GF2301@postgresql.org
Whole thread Raw
In response to Re: 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  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund wrote:

> One thing worth mentioning is that arguably the problem is caused by the
> fact that we're here emitting database level information in pg_dump,
> normally only done for dumpall.

... the reason for which is probably the lack of CURRENT_DATABASE as a
database specifier.  It might make sense to add the rest of
database-level information to pg_dump output, when we get that.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Support for N synchronous standby servers - take 2
Next
From: Andres Freund
Date:
Subject: Re: security labels on databases are bad for dump & restore