From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Priit Laes <plaes(at)plaes(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] Output configuration status after ./configure run. |
Date: | 2010-02-11 03:02:12 |
Message-ID: | 603c8f071002101902i41317b24rc2adaed72c5527af@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 10, 2010 at 9:17 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Wed, Feb 10, 2010 at 3:30 PM, Alvaro Herrera
>> <alvherre(at)commandprompt(dot)com> wrote:
>>> If this doesn't fit in 24x80 maybe we need to find a more compact way to
>>> display things.
>
>> +1. I wouldn't mind a one-line summary, but a two page summary seems
>> like a lot.
>
> So it seems there's some consensus that:
>
> 1. This printout should display everything configurable from a configure
> option, and nothing else (ie, not any of the platform-dependent
> conclusions that configure draws).
>
> 2. The printout has to be made to fit in 24x80 or so.
>
> I'm still quite dubious about the usefulness, but I could live with this
> if someone explains to me how the printout is going to stay within 24x80
> given the inevitable growth in number of configure options ...
I'm dubious too. I'm +1 for shorter, but neutral on the idea in general.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-02-11 03:12:41 | Re: Avoiding bad prepared-statement plans. |
Previous Message | Tom Lane | 2010-02-11 02:47:15 | Re: Odd cruft in .psql_history in HEAD |