Re: security labels on databases are bad for dump & restore
| От | Josh Berkus |
|---|---|
| Тема | Re: security labels on databases are bad for dump & restore |
| Дата | |
| Msg-id | 55B7D5A5.1010908@agliodbs.com обсуждение исходный текст |
| Ответ на | security labels on databases are bad for dump & restore (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: security labels on databases are bad for dump & restore
|
| Список | pgsql-hackers |
On 07/28/2015 11:58 AM, Robert Haas wrote: > I'd be strongly in favour of teaching GRANT, SECURITY LABEL, COMMENT >> ON DATABASE, etc to recognise CURRENT_DATABASE as a keyword. Then >> dumping them in pg_dump --create, and in pg_dump -Fc . >> >> In practice I see zero real use of pg_dumpall without --globals-only, >> and almost everyone does pg_dump -Fc . I'd like to see that method >> case actually preserve the whole state of the system and do the right >> thing sensibly. >> >> A pg_restore option to skip database-level settings could be useful, >> but I think by default they should be restored. +++++1 Let's get rid of pg_dumpall -g. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
В списке pgsql-hackers по дате отправления: