Re: why does plperl cache functions using just a bool for is_trigger - Mailing list pgsql-hackers

From Alex Hunsaker
Subject Re: why does plperl cache functions using just a bool for is_trigger
Date
Msg-id AANLkTinQhv3PLD1K7Y4UR524z_LUQUZ2yNXjL5Q02AXE@mail.gmail.com
Whole thread Raw
In response to Re: why does plperl cache functions using just a bool for is_trigger  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Sun, Oct 31, 2010 at 15:17, Andrew Dunstan <andrew@dunslane.net> wrote:
> On 10/31/2010 04:40 PM, Alex Hunsaker wrote:
>> And with the change we get the same
>> proc_desc for triggers and non triggers, so if the trigger function
>> gets called first, any call to the direct function will use the same
>> proc_desc with the wrong input/out conversion.
>
>
> How does that happen given that the function Oid is part of the hash key?

They are the same function and so have the same Oid ?


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: why does plperl cache functions using just a bool for is_trigger
Next
From: Greg Smith
Date:
Subject: SR fails to send existing WAL file after off-line copy