| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Dumping roles improvements? |
| Date: | 2011-10-11 16:45:01 |
| Message-ID: | 4E94728D.2060609@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/11/2011 12:40 PM, Bruce Momjian wrote:
> Josh Berkus wrote:
>> It occurs to me that we could really use two things to make it easier to
>> move copies of database stuff around:
>>
>> pg_dump -r, which would include a CREATE ROLE for all roles needed to
>> restore the database (probably without passwords), and
>>
>> pg_dumpall -r --no-passwords which would dump the roles but without
>> CREATE PASSWORD statements. This would be useful for cloning databases
>> for use in Dev, Test and Staging, where you don't what to copy the md5s
>> of passwords for possible cracking.
> What would this do that pg_dumpall --globals-only doesn't?
>
As stated, it would not export the passwords.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-10-11 16:46:05 | Re: Overhead cost of Serializable Snapshot Isolation |
| Previous Message | Bruce Momjian | 2011-10-11 16:43:59 | Re: COUNT(*) and index-only scans |