| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Dumping roles improvements? |
| Date: | 2011-10-11 19:47:11 |
| Message-ID: | 201110111947.p9BJlBx00694@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus wrote:
>
> > What is the logic for not dumping passwords but the CREATE ROLE
> > statement? I don't see how anyone would recognize that behavior as
> > logical. If you want to add a --no-passwords option to pg_dumpall, that
> > seems more logical to me.
>
> That's what I'm suggesting.
>
> Incidentally, what's the difference between -g and -r in terms of actual
> output, anyway?
Acording the docs, I assume -r is only roles, while -g includes
tablespace, so what you want is already available in pg_dumpall.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2011-10-11 19:50:57 | Re: Dumping roles improvements? |
| Previous Message | Tom Lane | 2011-10-11 19:46:28 | Re: Intermittent regression test failure from index-only scans patch |