Re: VACUUM fails to parse 0 and 1 as boolean value

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: VACUUM fails to parse 0 and 1 as boolean value
Date: 2019-05-21 05:31:32
Message-ID: 20190521053132.GG1921@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 20, 2019 at 09:55:59AM -0400, Robert Haas wrote:
> Well, it's confusing that we're not consistent about which spellings
> are accepted. The GUC system accepts true/false, on/off, and 0/1, so
> it seems reasonable to me to standardize on that treatment across the
> board. That's not necessarily something we have to do for v12, but
> longer-term, consistency is of value.

+1.

Note: boolean GUCs accept a bit more: yes, no, tr, fa, and their upper
case flavors, etc. These are everything parse_bool():bool.c accepts
as valid values.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul A Jungwirth 2019-05-21 05:35:31 Re: docs about FKs referencing partitioned tables
Previous Message Michael Paquier 2019-05-21 05:22:18 Re: clean up docs for v12