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

From Andrew Dunstan
Subject Re: why does plperl cache functions using just a bool for is_trigger
Date
Msg-id 4CC4E476.6080903@dunslane.net
Whole thread Raw
In response to Re: why does plperl cache functions using just a bool for is_trigger  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: why does plperl cache functions using just a bool for is_trigger
List pgsql-hackers

On 10/24/2010 09:34 PM, Tom Lane wrote:
>
>> For both trigger and non-trigger functions, we compile this ahead of the
>> user-set function code:
>>      our $_TD; local $_TD=shift;
>> Non-trigger functions get passed "undef" to correspond to this invisible
>> argument, while trigger functions get passed the hashref that the
>> trigger calling code has set up.
> Seems like we don't need it then.  You going to get rid of it?

Ok, will do.

cheers

andrew


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: WIP: extensible enums
Next
From: Robert Haas
Date:
Subject: Re: Range Types, discrete and/or continuous