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 20190517013456.GH20887@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  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Thu, May 16, 2019 at 03:29:36PM -0400, Robert Haas wrote:
> I'm not sure how much value it really has to define
> opt_boolean_or_string_or_numeric.  It saves 1 line of code in each of
> 3 places, but costs 6 lines of code to have it.
>
> Perhaps we could try to unify at a higher level.  Like can we merge
> vac_analyze_option_list with explain_option_list?

var_value has also similar semantics, and it uses makeAConst().  At
this point of the game, I'd like to think that it would be just better
to leave all the refactoring behind us on HEAD, to apply the first
patch presented on this thread, and to work more on that for v13 once
it opens for business if there is a patch to discuss about.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: VACUUM fails to parse 0 and 1 as boolean value
Next
From: Thomas Munro
Date:
Subject: Re: Fixing order of resowner cleanup in 12, for Windows