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

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: VACUUM fails to parse 0 and 1 as boolean value
Дата
Msg-id CA+TgmobcdBcpJg3G9PJHJ8N5qDATJLHm4u-DYqFPEAvwXYXcKA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: VACUUM fails to parse 0 and 1 as boolean value  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Ответы Re: VACUUM fails to parse 0 and 1 as boolean value  (Michael Paquier <michael@paquier.xyz>)
Список 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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Remove useless associativity/precedence from parsers
Следующее
От: Antonin Houska
Дата:
Сообщение: Inaccurate header comment of issue_xlog_fsync_comment