If there was a 7.2.2 release it would be wonderful for this to be knocked out, too.Thomas Swan <tswan@idigx.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.
This is a wonderful thing for those of us running postgresql in a hosting environment.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.