From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Dumping roles improvements? |
Date: | 2011-10-11 21:36:54 |
Message-ID: | 4E94B6F6.90806@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/11/2011 03:50 PM, Josh Berkus wrote:
>> Acording the docs, I assume -r is only roles, while -g includes
>> tablespace, so what you want is already available in pg_dumpall.
> No, it's not. You don't seem to be actually reading any of my proposals.
>
> (1) I cannot produce a single file in custom dump format which includes
> both a single database and all of the roles I need to build that database.
>
> (2) I cannot dump a set of roles without md5 passwords.
>
> Both of these are things I need to support dev/stage/testing integration
> at multiple sites.
>
There seems to be agreement on something for (2), and it won't be hard.
(1) would probably be much more complex. Essentially we'd need to add a
new object type for roles, I think. But won't (2) give you most of what
you need for (1) anyway? AIUI, your problem is that the roles might not
exist, and so some or all of the dump will fail. But if you have (2) and
dump the roles without passwords and restore them before running
pg_restore that wouldn't happen. It won't be one command but it will be
two or three pretty easy commands.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2011-10-11 21:40:49 | Re: Overhead cost of Serializable Snapshot Isolation |
Previous Message | Simon Riggs | 2011-10-11 21:35:58 | Re: Overhead cost of Serializable Snapshot Isolation |