Skip site navigation (1) Skip section navigation (2)

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

From: Alex Hunsaker <badalex(at)gmail(dot)com>
To: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH]
Date: 2010-02-03 17:21:49
Message-ID: 34d269d41002030921u327faf0ew997233d520cdbeb@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Feb 3, 2010 at 10:18, Alex Hunsaker <badalex(at)gmail(dot)com> wrote:
> On Wed, Feb 3, 2010 at 09:31, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)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...".

In response to

Responses

pgsql-hackers by date

Next:From: Joe ConwayDate: 2010-02-03 17:26:52
Subject: Re: use of dblink_build_sql_insert() induces a server crash
Previous:From: Alex HunsakerDate: 2010-02-03 17:18:51
Subject: Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH]

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group