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

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

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Alex Hunsaker <badalex(at)gmail(dot)com>
Cc: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, 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:27:27
Message-ID: 8274F9FA-2208-4C48-9841-765B7D707395@kineticode.com (view raw or flat)
Thread:
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


In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-02-03 17:31:12
Subject: Re: Hot Standby and VACUUM FULL
Previous:From: Joe ConwayDate: 2010-02-03 17:26:52
Subject: Re: use of dblink_build_sql_insert() induces a server crash

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