From: | Adrien Nayrat <adrien(dot)nayrat(at)dalibo(dot)com> |
---|---|
To: | Rafael Martinez <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: Dumping database creation options and ACLs |
Date: | 2017-07-10 12:38:30 |
Message-ID: | 0c615837-cfea-e38d-73b3-635ff931b4bc@dalibo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 07/03/2017 05:16 PM, Rafael Martinez wrote:
> We have a discussion about this some time ago and we created a wiki page
> where we tried to write down some ideas/proposals and links to threads
> discussing the subject:
>
> https://wiki.postgresql.org/wiki/Pg_dump_improvements
Thanks for this link! I'll look at this.
On 07/03/2017 04:58 PM, Robert Haas wrote:
> Note that some progress has been made on the CURRENT_DATABASE thing:
>
>
https://www.postgresql.org/message-id/CAF3+xM+xSswcWQZMP1cjj12gPz8DXHcM9_fT1y-0fVzxi9pmOw@mail.gmail.com
>
> I tend to favor that approach myself, although one point in favor of
> your suggestion is that adding another flag to pg_dumpall is a heck of
> a lot less work to get to some kind of solution to this issue.
Thanks, I'll look. Even if my approach is simple, the question is "Do we want
another flag in pg_dumpall? Is it the role of pg_dumpall?".
Regards,
--
Adrien NAYRAT
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2017-07-10 13:01:50 | Re: pgsql: Allow multiple hostaddrs to go with multiple hostnames. |
Previous Message | Heikki Linnakangas | 2017-07-10 12:32:37 | Re: List of hostaddrs not supported |