The following bug has been logged online:

Bug reference: 1222
Logged by: radim kolar

Email address: hsn (AT) netmag (DOT) cz

PostgreSQL version: 7.4.1

Operating system: freebsd

Description: database owner should have implicit control over public
db schema

Details:

Problem 2

Database owner should have implicit control over public schema
and over all objects in his database as well.

dbmail=> \l
List of databases
Name | Owner | Encoding
------------+-----------+-----------
dbmail | dbmail | SQL_ASCII
template0 | pgsql | SQL_ASCII
template1 | pgsql | SQL_ASCII
dbmail=> SELECT current_user;
current_user
--------------
dbmail
(1 row)
dbmail=> GRANT CREATE on SCHEMA public to public;
ERROR: permission denied for schema public
dbmail=>



---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

"PostgreSQL Bugs List" <pgsql-bugs (AT) postgresql (DOT) org> writes:
The former is debatable, the latter simply wrong. Make the DB owner a
superuser if you want him to have absolute privileges.

There has been some discussion of causing the public schema to be owned
by the DB owner, but this has not happened yet, partly because we are
not sure of all the consequences.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo (AT) postgresql (DOT) org)