"David G. Johnston" <david.g.johnston@xxxxxxxxx> writes: > It is what it is - and if one is not careful one can end up writing > hard-to-understand and possibly buggy code due to the various execution > environments and caches involved. Yeah, I don't see this changing. The actual answer is that we have search_path-aware caching of expressions and query plans within a plpgsql function, which is why the call to foo() reacts to the current search path. But the types of plpgsql variables are only looked up on the first use (within a session). Perhaps we ought to work harder on that, but it seems like a lot of overhead to add for something that will benefit next to nobody. > I’ve never really understood why “%TYPE’ exists… Compatibility with Oracle, I imagine. I agree it's a bizarre feature. But you could get the same behavior without %TYPE, just by referencing some other type that has different declarations in different schemas. > Add qualification or attach a “set search_path” clause to “create > function”. Code stored in the server should not rely on the session > search_path. Yeah, adding "set search_path" is recommendable if you don't want to think hard about this stuff. regards, tom lane
