Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH]
| От | Alex Hunsaker |
|---|---|
| Тема | Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH] |
| Дата | |
| Msg-id | 34d269d41002030921u327faf0ew997233d520cdbeb@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH] (Alex Hunsaker <badalex@gmail.com>) |
| Ответы |
Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH]
Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH] |
| Список | 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...".
В списке pgsql-hackers по дате отправления: