| From: | Euler Taveira <euler(at)timbira(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: postgres long options without value |
| Date: | 2012-04-04 20:50:05 |
| Message-ID: | 4F7CB3FD.8000006@timbira.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04-04-2012 17:07, Peter Eisentraut wrote:
> postgres -D ... --debug-print-plan
>
> which fails, because you need to write --ssl=on or
> --debug-print-plan=true etc.
>
> Have others had the same experience? Would it be worth supporting the
> case without value to default to on/true?
>
Please, don't do it. You can be fooled when we change a parameter default
value (specially if you have it in a script that is used in different
versions) from major versions.
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-04-04 21:07:31 | Re: log chunking broken with large queries under load |
| Previous Message | Simon Riggs | 2012-04-04 20:34:21 | Re: patch: improve SLRU replacement algorithm |