Re: pg_dump bug fixing - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: pg_dump bug fixing
Date
Msg-id 410EBAA6.8060309@commandprompt.com
Whole thread Raw
In response to Re: pg_dump bug fixing  (Josh Berkus <josh@agliodbs.com>)
Responses Re: pg_dump bug fixing
List 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@commandprompt.com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Open items
Next
From: Josh Berkus
Date:
Subject: Re: pg_dump bug fixing