Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH]

Alex Hunsaker <badalex@gmail.com>

From: Alex Hunsaker <badalex@gmail.com>

To: Tim Bunce <Tim.Bunce@pobox.com>

Cc: pgsql-hackers@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>

Date: 2010-02-03T17:21:49Z

Lists: pgsql-hackers

On Wed, Feb 3, 2010 at 10:18, Alex Hunsaker <badalex@gmail.com> wrote:
> On Wed, Feb 3, 2010 at 09:31, Tim Bunce <Tim.Bunce@pobox.com> wrote:
>> On Tue, Feb 02, 2010 at 08:42:21PM -0700, Alex Hunsaker wrote:

>> If we're going to bikeshed the names, I'd suggest:
>>
>>  plperl.on_init             - run on interpreter creation
>>  plperl.on_plperl_init      - run when then specialized for plperl
>>  plperl.on_plperlu_init     - run when then specialized for plperlu
>
> Hrm, I think I agree with Tom that we should not have a global
> on_init.  And instead of two separate GUCs (we still end up with 3
> gucs total). Im still thinking through it...

Err
"And instead have two separate GUCs (3 in total)" not
"And Instead of two...".