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

From Alexey Klyukin
Subject a common place for pl/perlu modules
Date
Msg-id FDD4AD42-84B1-43D8-AE79-115E7F2D0F9E@commandprompt.com
Whole thread Raw
Responses Re: a common place for pl/perlu modules
List pgsql-hackers
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. 

--
Alexey Klyukin                    http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while
Next
From: Priit Laes
Date:
Subject: Re: [PATCH] Output configuration status after ./configure run.