| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dumpall --exclude-database option |
| Date: | 2018-12-25 09:05:59 |
| Message-ID: | 20181225090559.GA3413@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 25, 2018 at 09:36:05AM +0100, Fabien COELHO wrote:
> I do not see Michaël's issue, and do not see how it could be so, for me the
> whole database-specific section generated by the underlying "pg_dump" call
> is removed, as expected.
>
> All is well for me, I turned the patch as ready.
Sorry for the noise. I have been double-checking what I said
previously and I am in the wrong.
> --
> -- PostgreSQL database "foo" dump
> --
>
> Or "pg_dumpall" could issue a comment line in the output telling which
> database is being considered.
Mentioning which database dump has been completed in the end comment
could be additionally nice.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2018-12-25 09:25:46 | Re: Online verification of checksums |
| Previous Message | Dean Rasheed | 2018-12-25 09:00:19 | Re: Statement-level Triggers For Uniqueness Checks |