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

From Dmitry Dolgov
Subject Re: VACUUM fails to parse 0 and 1 as boolean value
Date
Msg-id CA+q6zcVzS7GxoCHJD6Qr80PK4JJaKuHv97Gp26LZKonF8OMw3w@mail.gmail.com
Whole thread Raw
In response to Re: VACUUM fails to parse 0 and 1 as boolean value  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: VACUUM fails to parse 0 and 1 as boolean value  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
> On Thu, May 16, 2019 at 8:56 PM Fujii Masao <masao.fujii@gmail.com> wrote:
>
> Yes. Thanks for the comment!
> Attached is the updated version of the patch.
> It adds such common rule.

If I understand correctly, it resulted in the commit fc7c281f8. For some reason
it breaks vacuum tests for me, is it expected?

     ANALYZE (nonexistent-arg) does_not_exist;
    -ERROR:  syntax error at or near "-"
    +ERROR:  syntax error at or near "arg"
     LINE 1: ANALYZE (nonexistent-arg) does_not_exist;
    -                            ^
    +                             ^
     ANALYZE (nonexistentarg) does_not_exit;



pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Avoiding hash join batch explosions with extreme skew and weird stats
Next
From: Mark Wong
Date:
Subject: Re: Why is infinite_recurse test suddenly failing?