| From: | "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Jeremy Schneider <schnjere(at)amazon(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> |
| Subject: | Re: [PATCH] Query Jumbling for CALL and SET utility statements |
| Date: | 2022-09-08 06:49:13 |
| Message-ID: | 95c702fa-61a1-1bc1-7313-4f2b46fdaf94@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 9/8/22 7:23 AM, Michael Paquier wrote:
> On Wed, Sep 07, 2022 at 06:19:42PM -0700, Jeremy Schneider wrote:
>> I didn't fully debug yet, but here's the backtrace on my 14.4 build with
>> the patch
Thanks Jeremy for reporting the issue!
> What happens on HEAD? That would be the target branch for a new
> feature.
Just tested and i can see the same issue on HEAD.
Issue is on stmt->name being NULL here:
Breakpoint 2, JumbleExpr (jstate=0x55d60e769e30, node=0x55d60e769b60) at
queryjumble.c:364
364 if (node == NULL)
(gdb) n
368 check_stack_depth();
(gdb)
374 APP_JUMB(node->type);
(gdb)
376 switch (nodeTag(node))
(gdb)
398 VariableSetStmt *stmt =
(VariableSetStmt *) node;
(gdb) n
400 APP_JUMB_STRING(stmt->name);
(gdb) p stmt->name
$1 = 0x0
I'll have a closer look.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services:https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2022-09-08 06:50:12 | Re: [PATCH] Query Jumbling for CALL and SET utility statements |
| Previous Message | Pavel Stehule | 2022-09-08 05:50:45 | Re: broken table formatting in psql |