Re: cache lookup failed from empty plpythonu function - Mailing list pgsql-bugs

From Tom Lane
Subject Re: cache lookup failed from empty plpythonu function
Date
Msg-id 1566.1359143499@sss.pgh.pa.us
Whole thread Raw
In response to Re: cache lookup failed from empty plpythonu function  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: cache lookup failed from empty plpythonu function
List pgsql-bugs
Andres Freund <andres@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

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: cache lookup failed from empty plpythonu function
Next
From: Alvaro Herrera
Date:
Subject: Re: Re: BUG #7748: "drop owned by" fails with error message: "unrecognized object class: 1262"