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

Re: Frustrating issue with PGXS

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Eddie Stanley <eddiewould(at)paradise(dot)net(dot)nz>, mux(at)elvis(dot)mu(dot)org
Subject: Re: Frustrating issue with PGXS
Date: 2007-06-27 11:02:45
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Dear Peter,

> What was the problem with just making all uses of pg_config in 
> use a hardcoded bindir directly?

Because bindir is given by pg_config:-)

ISTM that the underlying issue, which was not foreseen in the initial pgxs 
and fixed later, is that some distributions use a different installation 
prefix at compile time and once the software is actually installed. You 
would end up with a /tmp/build/.. path which does not exist. If the 
installations are movable, you can only rely on pg_config.


In response to


pgsql-hackers by date

Next:From: Michael EnkeDate: 2007-06-27 12:08:43
Subject: self defined data type "with limit"?
Previous:From: Manera, VilliamDate: 2007-06-27 09:37:01
Subject: R: [postgresql-it] no cascade triggers?

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