From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(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 16:17:42 |
Message-ID: | 20100211161742.GA3145@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Euler Taveira de Oliveira escribió:
> Tom Lane escreveu:
> > 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 ...
> >
> AFAICS, we have > 40 configure options. If we want this to fit in 24 rows (i)
> we should choose popular options or (ii) print only features/packages that
> have a non-default option/value.
Or (iii) display more than one per line, for example
Configured PL languages: Perl Python Tcl
Configued block sizes: WAL: 8192 data: 8192 sth else: 16384
There you have six configure options in two lines.
> Both ideas aren't ideal for machine-readable
> format (as someone mentioned pgbuildfarm) because the summary is partial
My idea regarding buildfarm was to have it for human consumption, not
machine readable.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-02-11 16:21:46 | Re: Hostnames in pg_hba.conf |
Previous Message | Tom Lane | 2010-02-11 16:17:40 | Re: Avoiding bad prepared-statement plans. |