Re: [HACKERS] Refactor handling of database attributes betweenpg_dump and pg_dumpall
| От | Robert Haas |
|---|---|
| Тема | Re: [HACKERS] Refactor handling of database attributes betweenpg_dump and pg_dumpall |
| Дата | |
| Msg-id | CA+TgmoYocht4=sMswrdFZyR-tx_1UQng33saHgSyz74DJiaXJQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Refactor handling of database attributes betweenpg_dump and pg_dumpall (Haribabu Kommi <kommi.haribabu@gmail.com>) |
| Ответы |
Re: [HACKERS] Refactor handling of database attributes betweenpg_dump and pg_dumpall
|
| Список | pgsql-hackers |
On Mon, Oct 23, 2017 at 7:36 AM, Haribabu Kommi <kommi.haribabu@gmail.com> wrote: > Apologies for not providing much details. > > pg_dumpall is used to produce the following statements for database, > > "Create database" (other than default database) or > "Alter database set tablespace" for default database (if required) > > ACL queries related to database > Alter database config > Alter database role config > > whereas, pg_dump used to produce only "create database statement". How about adding a new flag --set-db-properties that doesn't produce CREATE DATABASE but does dump the other stuff? -C would dump both CREATE DATABASE *and* the other stuff. Then you could dump built-in databases with --set-db-properties and others with -C. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: