Re: pg_config - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: pg_config
Date
Msg-id 3805.24.211.141.25.1090319673.squirrel@www.dunslane.net
Whole thread Raw
In response to Re: pg_config  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: pg_config  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: pg_config  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut said:
> Tom Lane wrote:
>> I doubt it.  People can always just read the file to see what
>> settings are in it, and it's not like nonexperts are going to have a
>> variety of different configurations that we're gonna have to ask them
>> about. (Even in the Unix world, pg_config is not really needed when
>> most people are installing one of a small number of RPM-type
>> packages...)

ISTM that if it's not useful we should rip it out and if it is then we
should make it portable.

>
> The point of pg_config is not primarily to debug the installation
> layout  for us.  pg_config is used in configure scripts to find
> PostgreSQL  libraries and header files.

To that extent is it not broken by relocated installations that we have now
made some provision for?

> I don't know if Windows users
> have a  similar need.
>

I don't see why not.

cheers

andrew




pgsql-hackers by date:

Previous
From: Harald Fuchs
Date:
Subject: Re: pg_dump bug fixing
Next
From: Simon Riggs
Date:
Subject: Re: PITR COPY Failure (was Point in Time Recovery)