From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Dumping roles improvements? |
Date: | 2011-10-11 03:47:45 |
Message-ID: | CAFj8pRCwYkaM+8WB6hQZSgfUh1AidqXdWv4_CKrT3deH5DoV4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello
2011/10/11 Josh Berkus <josh(at)agliodbs(dot)com>:
> 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.
>
maybe some switch for "complete" dump of one database with related roles.
Pavel
> --
> Josh Berkus
> PostgreSQL Experts Inc.
> http://pgexperts.com
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-10-11 04:19:55 | Re: index-only scans |
Previous Message | Fujii Masao | 2011-10-11 02:46:37 | Re: unite recovery.conf and postgresql.conf |