Skip site navigation (1) Skip section navigation (2)

a common place for pl/perlu modules

From: Alexey Klyukin <alexk(at)commandprompt(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: a common place for pl/perlu modules
Date: 2010-02-11 16:10:30
Message-ID: FDD4AD42-84B1-43D8-AE79-115E7F2D0F9E@commandprompt.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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

pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group