Re: VACUUM fails to parse 0 and 1 as boolean value
От | Dmitry Dolgov |
---|---|
Тема | Re: VACUUM fails to parse 0 and 1 as boolean value |
Дата | |
Msg-id | CA+q6zcXcfcxU3QXXvT0b+fKRk507HJi-s1EhmyJBq8LFsjr-KA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: VACUUM fails to parse 0 and 1 as boolean value (Andres Freund <andres@anarazel.de>) |
Список | pgsql-hackers |
> On Mon, May 20, 2019 at 9:20 PM Andres Freund <andres@anarazel.de> wrote: > > Hi, > > On May 20, 2019 12:14:30 PM PDT, Dmitry Dolgov <9erthalion6@gmail.com> wrote: > >> 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; > > That has since been fixed, right? Yep, right, after I've checkout 47a14c99e471. Sorry for the noise.
В списке pgsql-hackers по дате отправления: