From: | Neil Conway <neilc(at)samurai(dot)com> |
---|---|
To: | tswan(at)idigx(dot)com |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump, pg_dumpall and createdb privilege |
Date: | 2002-08-19 19:46:36 |
Message-ID: | 87d6se1vj7.fsf@mailbox.samurai.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Swan <tswan(at)idigx(dot)com> writes:
> 1. create a user with createdb privilege.
> 2. create a database as that user (allowing that user full reign over
> that particular db)
> 3. drop the createdb from the user.
> 4. pg_dumpall the databases to a single file
> 5. either use pg_restore or psql < infile to restore the databases and
> it fails.
This is a known problem, I remember raising it on hackers several
months ago.
> Is it possible to address this before the 7.3 release or is this
> concern no longer a problem in the 7.3 branch?
It's fixed in CVS. Databases are now created using CREATE DATABASE xxx
WITH OWNER yyy: this technique can also be used by the DBA in the
first place, avoiding the need to manually add and then remove
CREATEDB privs from the new user account.
Cheers,
Neil
--
Neil Conway <neilc(at)samurai(dot)com> || PGP Key ID: DB3C29FC
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Swan | 2002-08-19 20:06:19 | Re: pg_dump, pg_dumpall and createdb privilege |
Previous Message | Thomas Swan | 2002-08-19 19:40:06 | pg_dump, pg_dumpall and createdb privilege |