Re: security labels on databases are bad for dump & restore
От | Fabrízio de Royes Mello |
---|---|
Тема | Re: security labels on databases are bad for dump & restore |
Дата | |
Msg-id | CAFcNs+o2CBzq8AA6UbSYUYoJ9qA5qJs+w-REsMb7hFQQT8LfWw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: security labels on databases are bad for dump & restore (Adam Brightwell <adam.brightwell@crunchydatasolutions.com>) |
Список | pgsql-hackers |
<div dir="ltr"><div class="gmail_extra">On Wed, Jul 22, 2015 at 4:42 PM, Adam Brightwell <<a href="mailto:adam.brightwell@crunchydatasolutions.com">adam.brightwell@crunchydatasolutions.com</a>>wrote:<br />> <br/>> [...]<br />><br />> Also, I think this would potentially conflict with what Fabrízio is<br />> doing withCURRENT_DATABASE on COMMENT, though, I think it might be a<br />> preferable solution.<br />><br />> <a href="https://commitfest.postgresql.org/5/229/">https://commitfest.postgresql.org/5/229/</a><br/>><br /><br /></div><divclass="gmail_extra">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 lifeeasier with a more consistency patch. <br /><br /></div><div class="gmail_extra">Seems reasonable?<br /></div><div class="gmail_extra"><br/></div><div class="gmail_extra">Regards,<br /></div><div class="gmail_extra"><br />--<br />Fabríziode Royes Mello<br />Consultoria/Coaching PostgreSQL<br />>> Timbira: <a href="http://www.timbira.com.br">http://www.timbira.com.br</a><br/>>> Blog: <a href="http://fabriziomello.github.io">http://fabriziomello.github.io</a><br/>>> Linkedin: <a href="http://br.linkedin.com/in/fabriziomello">http://br.linkedin.com/in/fabriziomello</a><br/>>> Twitter: <a href="http://twitter.com/fabriziomello">http://twitter.com/fabriziomello</a><br/>>> Github: <a href="http://github.com/fabriziomello">http://github.com/fabriziomello</a></div></div>
В списке pgsql-hackers по дате отправления: