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

From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: VACUUM fails to parse 0 and 1 as boolean value
Date: 2019-05-20 19:22:34
Message-ID: CA+q6zcXcfcxU3QXXvT0b+fKRk507HJi-s1EhmyJBq8LFsjr-KA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Mon, May 20, 2019 at 9:20 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> Hi,
>
> On May 20, 2019 12:14:30 PM PDT, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> wrote:
> >> On Thu, May 16, 2019 at 8:56 PM Fujii Masao <masao(dot)fujii(at)gmail(dot)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;
>
> That has since been fixed, right?

Yep, right, after I've checkout 47a14c99e471. Sorry for the noise.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2019-05-20 20:08:42 Re: Question about new pg12 feature no-rewrite timestamp to timestamptz conversion
Previous Message Andres Freund 2019-05-20 19:20:35 Re: VACUUM fails to parse 0 and 1 as boolean value