From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
---|---|
To: | Евгений Горбанев <gorbanyoves(at)basealt(dot)ru> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
Subject: | Re: Assert failure in base_yyparse |
Date: | 2025-05-09 05:54:37 |
Message-ID: | CAMbWs4-DrQ0COUpFoje_NyxFDMxThCqGMc+D8uk=FfmFnbMCNw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 14, 2025 at 5:45 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> It seems what happens is that internally in gram.y (~line 14274), the
> DefElem for the not-null option is assigned the name "is_not_null".
> As a result, this allows users to explicitly use "is_not_null" as the
> option name. However, the value provided for the is_not_null option
> in this way might not be a Boolean as expected, which triggers the
> assertion.
>
> I kind of doubt we should allow the use of the "is_not_null" keyword
> in the xmltable function.
>
> Hi Álvaro, what do you think about this?
Just realized Álvaro has switched to a new email address — re-cc'ing.
Thanks
Richard
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2025-05-09 06:37:58 | Re: pgsql: Make cancel request keys longer |
Previous Message | Michael Paquier | 2025-05-09 05:35:33 | Re: queryId constant squashing does not support prepared statements |