| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_dump bug fixing |
| Date: | 2004-08-02 22:05:26 |
| Message-ID: | 410EBAA6.8060309@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> This is a non-trivial accident to have happen on a shared machine; once users
> are dumped, all of their ownerships and permissions go with them. If you
> have a complex permissions system, better hope you backed up first!
>
> I find this behavior highly undesirable, and consider it a bug. The globals
> dump should just add users, and not delete any.
Unless the --clean option is passed, yes I agree with you. The other
issue is that it is silly to have to use pg_dumpall to get the globals.
A person should be able to pull a pg_dump on a particular database and
get everything that is required to run that database. Including users.
Joshua D. Drake
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
| Attachment | Content-Type | Size |
|---|---|---|
| jd.vcf | text/x-vcard | 640 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-08-02 22:12:37 | Re: pg_dump bug fixing |
| Previous Message | Tom Lane | 2004-08-02 21:55:11 | Re: Open items |