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

From David E. Wheeler
Subject Re: First feature patch for plperl - draft [PATCH]
Date
Msg-id D52625E7-BD7A-4D93-8FC3-EAED7E822F47@kineticode.com
Whole thread Raw
In response to Re: First feature patch for plperl - draft [PATCH]  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: First feature patch for plperl - draft [PATCH]
List pgsql-hackers
On Dec 4, 2009, at 10:36 AM, Tom Lane wrote:

>> Are multiline GUCs allowed in the postgresql.conf file?
>
> I don't think so.  In any case this seems like an extreme abuse of the
> concept of a GUC, as well as being a solution in search of a problem,
> as well as being something that should absolutely not ever happen inside
> the postmaster process for both reliability and security reasons.
> 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 PGInit
orsomething, and then just make the GUC: 
   plperl.on_perl_init = 'use PGInit;'

Best,

David

pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: CVS HEAD: Error accessing system column from plpgsql trigger function
Next
From: Andrew Dunstan
Date:
Subject: Re: First feature patch for plperl - draft [PATCH]