Re: a common place for pl/perlu modules - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: a common place for pl/perlu modules
Date
Msg-id 4B742F25.7050704@dunslane.net
Whole thread Raw
In response to a common place for pl/perlu modules  (Alexey Klyukin <alexk@commandprompt.com>)
Responses Re: a common place for pl/perlu modules
List pgsql-hackers

Alexey Klyukin wrote:
> Hello,
>
> When developing pl/perlu functions common definitions and methods are often stored in external .pm modules. During
deploymentthe modules should be installed somewhere in @INC to be reachable by the perl interpreter. However,
installingthe modules to a location outside of the PG installation makes it hard to have a consistent environment when
runningmultiple PG versions on the same host. What do you think about defining a canonical place for pl/perlu .pm
modules(i.e. PKGLIBDIR) and adding this location to @INC during the interpreter initialization ? Another idea is to
allowa user to specify such location by adding a new custom GUC variable.
 
>
>
>   

Why won't setting this in the new on_perl_init setting work? It's even 
included in to documented examples using the standard lib module: 
<http://developer.postgresql.org/pgdocs/postgres/plperl-under-the-hood.html#PLPERL-CONFIG>

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Hostnames in pg_hba.conf
Next
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while