From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com>,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>,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:20:35 |
Message-ID: | 719E13C7-D98E-435B-8813-E1A135444AF2@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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?
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Dolgov | 2019-05-20 19:22:34 | Re: VACUUM fails to parse 0 and 1 as boolean value |
Previous Message | Mark Wong | 2019-05-20 19:15:49 | Re: Why is infinite_recurse test suddenly failing? |