Hello,

When developing pl/perlu functions common definitions and methods are often stored in external .pm modules. During deployment the modules should be installed somewhere in @INC to be reachable by the perl interpreter. However, installing the modules to a location outside of the PG installation makes it hard to have a consistent environment when running multiple 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 allow a user to specify such location by adding a new custom GUC variable.

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

Responses

• Re: a common place for pl/perlu modules at 2010-02-11 16:24:05 from Andrew Dunstan

pgsql-hackers by date

Next:	From: Robert Haas	Date: 2010-02-11 16:16:36
	Subject: Re: TCP keepalive support for libpq
Previous:	From: Tom Lane	Date: 2010-02-11 15:55:28
	Subject: Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while