Re: security labels on databases are bad for dump & restore
| От | Andres Freund |
|---|---|
| Тема | Re: security labels on databases are bad for dump & restore |
| Дата | |
| Msg-id | 20150715090853.GH5520@alap3.anarazel.de обсуждение |
| Ответ на | Re: security labels on databases are bad for dump & restore (Alvaro Herrera <alvherre@2ndquadrant.com>) |
| Ответы |
Re: security labels on databases are bad for dump & restore
|
| Список | pgsql-hackers |
On 2015-07-15 12:04:40 +0300, Alvaro Herrera wrote: > 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. I'm not sure. I mean, it's not that an odd idea to assign a label to a database and then restore data into it, and expect the explicitly assigned label to survive. Not sure if there actually is a good behaviour either way here :/
В списке pgsql-hackers по дате отправления: