Hi Ho!
--- On Thu, 10/30/08, Tom Lane <[EMAIL PROTECTED]> wrote:
> Because it'd be extremely difficult to do otherwise
> (given the way that
> CREATE DATABASE works)
Understood.
> and it's not at all clear that
> it'd be a good
> idea anyway.
Can it be cleared up by looking at the kind of security breaches that can be
abused by users that are not the owner of the DB when the public schema is
owned by the owner of the DB (i.e., not a SUPERUSER) instead of by "postgres"?
I am hoping to get a list of achilles' heels that I need to consider when
assigning the ownership of a public schema of a DB to its owner that is not a
SUPERUSER from the default "postgres".
> regards, tom lane
Best regards,
Eus
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
