Re: pg_config

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Cc: <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <andrew(at)dunslane(dot)net>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_config
Date: 2004-07-20 16:25:38
Message-ID: 200407201825.38126.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Andrew Dunstan wrote:
> To that extent is it not broken by relocated installations that we
> have now made some provision for?

Well, then it should be fixed to take relocated installations into
account.

Relocatable installations are by nature a pretty broken feature. When
you use pg_config to locate, say, libpq, then compile your third-party
package, and then move libpq somewhere else, nothing can save you
(except moving libpq back). At least on Unix, relocatable
installations are a walking cane when you need parallel installations
for upgrades, but they'll never work reliably in general.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Responses

  • pg_config at 2004-07-20 20:11:30 from Andrew Dunstan

Browse pgsql-hackers by date

  From Date Subject
Next Message Klaus Naumann 2004-07-20 16:29:30 Re: [HACKERS] Point in Time Recovery
Previous Message Steve Atkins 2004-07-20 16:25:28 Re: localhost redux

Browse pgsql-patches by date

  From Date Subject
Next Message Klaus Naumann 2004-07-20 16:29:30 Re: [HACKERS] Point in Time Recovery
Previous Message markw 2004-07-20 15:36:27 Re: [HACKERS] Point in Time Recovery