Jan Wieck <janwieck@yahoo.com> writes:
> Is an invalid search path really that critical (read security
> issue)?
It's not a security issue (unless the OID counter wraps around soon
enough to let someone else get assigned the same OID for a namespace).
But it could be pretty annoying anyway, because the front element of
the search path is also the default creation target namespace. You
could create a bunch of tables and then be unable to access them later
for lack of a way to name them.
I'm not really excited about establishing positive interlocks across
backends to prevent DROPping a namespace that someone else has in their
search path ... but I do want to handle the simple local-effect cases,
like rollback of creation of a namespace.
regards, tom lane