Re: VACUUM fails to parse 0 and 1 as boolean value - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: VACUUM fails to parse 0 and 1 as boolean value
Date
Msg-id 20190521053132.GG1921@paquier.xyz
Whole thread Raw
In response to Re: VACUUM fails to parse 0 and 1 as boolean value  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: VACUUM fails to parse 0 and 1 as boolean value
Re: VACUUM fails to parse 0 and 1 as boolean value
List 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

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: clean up docs for v12
Next
From: Paul A Jungwirth
Date:
Subject: Re: docs about FKs referencing partitioned tables