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
