| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Dumping roles improvements? |
| Date: | 2011-10-11 20:19:35 |
| Message-ID: | 3164.1318364375@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 10/11/2011 12:40 PM, Bruce Momjian wrote:
>> Josh Berkus wrote:
>>> 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.
I can see some possible use in a --no-passwords option that's orthogonal
to all else. The rest of this seems rather confused...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-10-11 20:21:11 | Re: Overhead cost of Serializable Snapshot Isolation |
| Previous Message | Dimitri Fontaine | 2011-10-11 20:09:02 | Re: SET variable - Permission issues |