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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-25 01:59:18
Message-ID: 4CC4E476.6080903@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-10-25 02:40:07 Re: Range Types, discrete and/or continuous
Previous Message Andrew Dunstan 2010-10-25 01:38:41 Re: WIP: extensible enums