| From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, 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:14:30 |
| Message-ID: | CA+q6zcVzS7GxoCHJD6Qr80PK4JJaKuHv97Gp26LZKonF8OMw3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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;
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Wong | 2019-05-20 19:15:49 | Re: Why is infinite_recurse test suddenly failing? |
| Previous Message | Melanie Plageman | 2019-05-20 19:05:56 | Re: Avoiding hash join batch explosions with extreme skew and weird stats |