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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
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-24 23:50:03
Message-ID: 23157.1287964203@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 10/24/2010 06:44 PM, Tom Lane wrote:
>> I'm not certain that plperl is actually correct to do it that way,
>> but that's the basic idea.

> Why do we need the is_trigger flag at all for the plperl hash key? At
> first glance it strikes me as unnecessary.

We might not. Does the presence or absence of the $_TD hash reference
have any impact on what we cache, or what Perl might cache internally?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-10-25 00:12:46 Re: WIP: extensible enums
Previous Message Kevin Grittner 2010-10-24 23:23:34 Re: Serializable snapshot isolation patch