| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
| Cc: | Vaishnavi Prabakaran <vaishnaviprabakaran(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Refactor handling of database attributes between pg_dump and pg_dumpall |
| Date: | 2017-10-26 11:01:32 |
| Message-ID: | CA+TgmoYocht4=sMswrdFZyR-tx_1UQng33saHgSyz74DJiaXJQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 23, 2017 at 7:36 AM, Haribabu Kommi
<kommi(dot)haribabu(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-10-26 11:14:33 | Re: How to determine that a TransactionId is really aborted? |
| Previous Message | Antonin Houska | 2017-10-26 10:42:51 | Re: Removing [Merge]Append nodes which contain a single subpath |