Re: First feature patch for plperl - draft [PATCH] - Mailing list pgsql-hackers

From Tom Lane
Subject Re: First feature patch for plperl - draft [PATCH]
Date
Msg-id 28618.1259952660@sss.pgh.pa.us
Whole thread Raw
In response to Re: First feature patch for plperl - draft [PATCH]  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: First feature patch for plperl - draft [PATCH]  (Robert Haas <robertmhaas@gmail.com>)
Re: First feature patch for plperl - draft [PATCH]  ("David E. Wheeler" <david@kineticode.com>)
List pgsql-hackers
"David E. Wheeler" <david@kineticode.com> writes:
> On Dec 4, 2009, at 10:36 AM, Tom Lane wrote:
>> I vote a big no on this.

> That's fine. It's relatively simple for an admin to create a Perl module that does everything she wants, call it
PGInitor something, and then just make the GUC:
 

>     plperl.on_perl_init = 'use PGInit;'

No, you missed the point: I'm objecting to having any such thing as
plperl.on_perl_init, full stop.

Aside from the points I already made, it's not even well defined.
What is to happen if the admin changes the value when the system
is already up?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: First feature patch for plperl - draft [PATCH]
Next
From: Jeff
Date:
Subject: Re: First feature patch for plperl - draft [PATCH]