Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH] - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH]
Date
Msg-id 603c8f071002030655n743098abo920d1d0b12d8b6bd@mail.gmail.com
Whole thread Raw
In response to Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH]  (Alex Hunsaker <badalex@gmail.com>)
Responses Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH]
List pgsql-hackers
On Wed, Feb 3, 2010 at 9:51 AM, Alex Hunsaker <badalex@gmail.com> wrote:
> Hey! I don't think were quite to that nasty B word yet :)  I would
> argue that treating plperl and plperlu as the same language just
> because it shares the same code is a mistake.  But I hate the idea of
> two custom_variable_classes for plperl(u) as well.  Which is why I
> quickly switched to plperl.on_plperl(u)_init.  Any thoughts on those?
> Again maybe people think the original names are fine... *shrug*.

I like plperl.on_plperl(u)_init better than plperl.on_(un)trusted_init.

...Robert


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Review of Writeable CTE Patch
Next
From: Bruce Momjian
Date:
Subject: Partial Page Writes documentaiton mention