Skip site navigation (1) Skip section navigation (2)

Re: why does plperl cache functions using just a bool for is_trigger

From: Alex Hunsaker <badalex(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Urbański <wulczer(at)wulczer(dot)org>, Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: why does plperl cache functions using just a bool for is_trigger
Date: 2010-10-31 21:24:20
Message-ID: AANLkTinQhv3PLD1K7Y4UR524z_LUQUZ2yNXjL5Q02AXE@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sun, Oct 31, 2010 at 15:17, Andrew Dunstan <andrew(at)dunslane(dot)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 ?

In response to

pgsql-hackers by date

Next:From: Greg SmithDate: 2010-10-31 21:31:44
Subject: SR fails to send existing WAL file after off-line copy
Previous:From: Andrew DunstanDate: 2010-10-31 21:17:56
Subject: Re: why does plperl cache functions using just a bool for is_trigger

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group