Horton
Menu

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

David E. Wheeler <david@kineticode.com>

View thread
From: "David E. Wheeler" <david@kineticode.com>
To: Alex Hunsaker <badalex@gmail.com>
Cc: Tim Bunce <Tim.Bunce@pobox.com>, pgsql-hackers@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>
Date: 2010-02-03T17:27:27Z
Lists: pgsql-hackers 
On Feb 3, 2010, at 9:21 AM, Alex Hunsaker wrote:

>>>  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...
> 

I completely agree on using "plperl" and "plperlu" instead of "trusted" and "untrusted" in the GUC names. The latter are just too confusing (even Tom mixed them up in a post last week). They are among the worst names in the system, IMHO.

Best,

David