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

From Robert Haas
Subject Re: VACUUM fails to parse 0 and 1 as boolean value
Date
Msg-id CA+TgmobcdBcpJg3G9PJHJ8N5qDATJLHm4u-DYqFPEAvwXYXcKA@mail.gmail.com
Whole thread Raw
In response to Re: VACUUM fails to parse 0 and 1 as boolean value  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: VACUUM fails to parse 0 and 1 as boolean value  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Thu, May 16, 2019 at 9:21 PM Kyotaro HORIGUCHI
<horiguchi.kyotaro@lab.ntt.co.jp> wrote:
> I think we don't need to support 1/0 as boolean here (it's
> unnatural) and the documentation of VACUUM/ANALYZE should be
> fixed.

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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Remove useless associativity/precedence from parsers
Next
From: Antonin Houska
Date:
Subject: Inaccurate header comment of issue_xlog_fsync_comment