| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-02-03 17:31:12 | Re: Hot Standby and VACUUM FULL |
| Previous Message | Joe Conway | 2010-02-03 17:26:52 | Re: use of dblink_build_sql_insert() induces a server crash |