From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: small proposal: pg_config record flag variables? |
Date: | 2005-08-09 20:06:42 |
Message-ID: | 42F90CD2.2050905@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>I wrote:
>
>
>>Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>
>>
>>>I would be tempted to have one flag called, say, --build-env which has
>>>all the interesting settings from the build environment in one hit.
>>>
>>>
>
>
>
>>The one-flag way would be human readable but not program friendly.
>>
>>
>
>OTOH there's nothing saying we can't do both.
>
>Actually, I now remember having also wished for a "pg_config --all"
>switch that would dump out everything the program knows. The existing
>UI makes you ask pretty-please for each tidbit, and that gets old fast.
>Would --all serve what you had in mind, or do you specifically want
>--build-env?
>
>
>
>
--all would be fine. In fact, why not make it the default? This has
always struck me as a bit lame:
[andrew(at)alphonso inst]$ bin/pg_config
pg_config: argument required
Try "pg_config --help" for more information
[andrew(at)alphonso inst]$
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-08-09 20:10:08 | Re: small proposal: pg_config record flag variables? |
Previous Message | Tom Lane | 2005-08-09 20:03:53 | Re: Simplifying wal_sync_method |