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 20190514232033.GB1440@paquier.xyz
Whole thread Raw
In response to Re: VACUUM fails to parse 0 and 1 as boolean value  (Andres Freund <andres@anarazel.de>)
Responses Re: VACUUM fails to parse 0 and 1 as boolean value  (Andres Freund <andres@anarazel.de>)
Re: VACUUM fails to parse 0 and 1 as boolean value  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Tue, May 14, 2019 at 10:52:23AM -0700, Andres Freund wrote:
> Might be worth having a common rule for such options, so we don't
> duplicate the knowledge between different places.
>
> CCing Robert and Sawada-san, who committed / authored that code.

Hmn.  I think that Robert's commit is right to rely on defGetBoolean()
for option parsing.  That's what we use for anything from CREATE
EXTENSION to CREATE SUBSCRIPTION, etc.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: vacuumdb and new VACUUM options
Next
From: Andres Freund
Date:
Subject: Re: VACUUM fails to parse 0 and 1 as boolean value