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

Re: Relocatable locale

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>,Andrew Dunstan <andrew(at)dunslane(dot)net>,PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Relocatable locale
Date: 2004-05-27 02:26:04
Message-ID: 5757.1085624764@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Peter Eisentraut wrote:
>> The problem boils down to the fact that libpq needs to find its data 
>> files (in this case locale data, but it could be anything), but it 
>> doesn't know its own location, so it can't use a relative path 
>> reference as has been proposed.

> I am wondering if we should use environment variables, and have our apps
> use putenv() to set it to the proper relative path.

*Our* apps are not the problem.  The problem comes when libpq is
embedded in somebody else's app --- which is not going to be that
cooperative, and would have no good way to know what path to supply
if it did want to be cooperative.

I can't say I care for the environment variable idea either; though
there may not be any better alternative.

			regards, tom lane

In response to

Responses

pgsql-patches by date

Next:From: Bruce MomjianDate: 2004-05-27 02:41:55
Subject: Re: Relocatable locale
Previous:From: Tom LaneDate: 2004-05-27 01:47:27
Subject: Re: .cvsignore update...

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