| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_config |
| Date: | 2004-07-20 05:59:43 |
| Message-ID: | 200407200759.43970.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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...)
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. I don't know if Windows users have a
similar need.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-07-20 06:47:21 | Re: Patch for pg_dump: Multiple -t options and new -T option |
| Previous Message | Christopher Kings-Lynne | 2004-07-20 05:26:06 | Re: Patch for pg_dump: Multiple -t options and new -T option |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-07-20 06:47:21 | Re: Patch for pg_dump: Multiple -t options and new -T option |
| Previous Message | Christopher Kings-Lynne | 2004-07-20 05:26:06 | Re: Patch for pg_dump: Multiple -t options and new -T option |