Andres Freund <and...@2ndquadrant.com> writes:
> Its slightly more complex than just making it one hash table with an
> extended key. When validating a trigger function we don't have a
> relation to do the cache lookup. I chose to handle that case by not
> doing a cache lookup at all in that case which imo is a sensible
> choice.
Seems fair. However ... why is it safe for PLy_procedure_create to be
using the same name for multiple instances of a trigger function?
Should we not be including the rel OID when building the procName
string?
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
