Tom Lane wrote: > The fact that schema ss might not exist is one of the scenarios that > we need to qualify the primary name in the DROP to protect against. > It's possible say that "complex" would get mis-resolved as some other > type "complex" in some other schema, but it doesn't matter since the > qualified function name will surely not match anything else. > > What I think we ought to do is just reset currSchema once, after the > DROP phase is completed, whether or not any schemas were dropped. > This will be considerably more bulletproof in partial-restore > situations. > > Will go fix.
OK. I did consider that option but was unsure of the ramifications. The problem is definitely subtle. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
