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

From Fabrízio de Royes Mello
Subject Re: security labels on databases are bad for dump & restore
Date
Msg-id CAFcNs+o2CBzq8AA6UbSYUYoJ9qA5qJs+w-REsMb7hFQQT8LfWw@mail.gmail.com
Whole thread Raw
In response to Re: security labels on databases are bad for dump & restore  (Adam Brightwell <adam.brightwell@crunchydatasolutions.com>)
List pgsql-hackers
On Wed, Jul 22, 2015 at 4:42 PM, Adam Brightwell <adam.brightwell@crunchydatasolutions.com> wrote:
>
> [...]
>
> Also, I think this would potentially conflict with what Fabrízio is
> doing with CURRENT_DATABASE on COMMENT, though, I think it might be a
> preferable solution.
>
> https://commitfest.postgresql.org/5/229/
>

Unfortunately this code is a bit weird and will be better to move to the next commitfest (I have no time to improve it yet), so we can join efforts and implement all ideas and make the reviewers life easier with a more consistency patch.

Seems reasonable?

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello

pgsql-hackers by date:

Previous
From: Adam Brightwell
Date:
Subject: Re: security labels on databases are bad for dump & restore
Next
From: Peter Eisentraut
Date:
Subject: MultiXact member wraparound protections are now enabled