Re: [HACKERS] Dumping database creation options and ACLs - Mailing list pgsql-hackers

From Adrien Nayrat
Subject Re: [HACKERS] Dumping database creation options and ACLs
Date
Msg-id 0c615837-cfea-e38d-73b3-635ff931b4bc@dalibo.com
Whole thread Raw
In response to Re: [HACKERS] Dumping database creation options and ACLs  (Rafael Martinez <r.m.guerrero@usit.uio.no>)
List 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

http://dalibo.com - http://dalibo.org


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: [HACKERS] List of hostaddrs not supported
Next
From: Heikki Linnakangas
Date:
Subject: [HACKERS] Re: [COMMITTERS] pgsql: Allow multiple hostaddrs to go with multiplehostnames.