Re: plperl and inline functions -- first draft

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Joshua Tolley <eggyknap(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: plperl and inline functions -- first draft
Date: 2009-11-06 19:10:27
Message-ID: 4AF474A3.9030502@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joshua Tolley wrote:
>>> The basics seem to be there, with at least one notable
>>> exception, namely that plperl functions can do stuff only plperlu should do. I
>>> presume this is because I really don't understand yet how plperl's trusted
>>> interpreter initialization works, and have simply copied what looked like
>>> important stuff from the original plperl call handler.
>>>
>>>
>> I'll check that out.
>>
>
>
>

Ok, I have a handle on the trusted/nontrusted issue. But I think the
piece that's missing here is that it needs to save the calling context
etc. and use PG_TRY() and friends, just like plperl_call_handler(). I'll
work on that.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2009-11-06 19:11:28 Re: operator exclusion constraints
Previous Message Tom Lane 2009-11-06 19:05:26 Re: operator exclusion constraints