From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump bug fixing |
Date: | 2004-08-02 21:23:19 |
Message-ID: | 200408021423.19172.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Chris,
I've just found a bit of undesirable functionality which I would call a bug in
pg_dump. I'm not sure everyone would, but we'll see.
Problem: the script which dumps globals such as users (pg_dumpall -g)
involves deleting *all* users from the pg_shadow table via a direct update to
that table. What this means in effect is that, should you attempt to use
"pg_dumpall -g" to *move* a set of users from one active server to another
(such as for transferring a database) the resulting pg_dump file will delete
all of the users which previously existed on that server.
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.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-02 21:39:12 | Re: pg_dump bug fixing |
Previous Message | Dave Page | 2004-08-02 20:39:27 | Re: Open items |