Re: Dumping roles improvements? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Dumping roles improvements?
Date
Msg-id 4E94B6F6.90806@dunslane.net
Whole thread Raw
In response to Re: Dumping roles improvements?  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Dumping roles improvements?  (Josh Berkus <josh@agliodbs.com>)
List 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


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_ctl restart - behaviour based on wrong instance
Next
From: "Kevin Grittner"
Date:
Subject: Re: Overhead cost of Serializable Snapshot Isolation