<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body>
Neil Conway wrote:<br>
<blockquote type="cite" cite="mid87d6se1vj7(dot)fsf(at)mailbox(dot)samurai(dot)com">
<pre wrap="">Thomas Swan <a class="moz-txt-link-rfc2396E" href="mailto:tswan(at)idigx(dot)com"><tswan(at)idigx(dot)com></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap=""><!---->
This is a known problem, I remember raising it on hackers several
months ago.</pre>
</blockquote>
If there was a 7.2.2 release it would be wonderful for this to be knocked
out, too.<br>
<blockquote type="cite" cite="mid87d6se1vj7(dot)fsf(at)mailbox(dot)samurai(dot)com">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">Is it possible to address this before the 7.3 release or is this
concern no longer a problem in the 7.3 branch?
</pre>
</blockquote>
<pre wrap=""><!---->
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.</pre>
</blockquote>
This is a wonderful thing for those of us running postgresql in a hosting
environment.<br>
<br>
</body>
</html>