Andrew Dunstan <and...@dunslane.net> writes:
> In that case I think I'm in favor of the suggestion of an implied empty
> user mapping for PUBLIC, as long as it can be overridden.
But how would you do that (override it)? All you can do is create an
explicit mapping, and then you still have a mapping that allows access
to PUBLIC. (Or not, but if an empty one does, you're stuck.)
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
