| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Jeremy Schneider <schnjere(at)amazon(dot)com>, "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>, 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:50:12 |
| Message-ID: | 20220908065012.l3bd2np7wj52cxco@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 08, 2022 at 02:23:19PM +0900, 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
>
> What happens on HEAD? That would be the target branch for a new
> feature.
It would be the same AFAICS. From v3:
+ case T_VariableSetStmt:
+ {
+ VariableSetStmt *stmt = (VariableSetStmt *) node;
+
+ APP_JUMB_STRING(stmt->name);
+ JumbleExpr(jstate, (Node *) stmt->args);
+ }
For a RESET ALL command stmt->name is NULL.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2022-09-08 06:51:49 | Re: Perform streaming logical transactions by background workers and parallel apply |
| Previous Message | Drouvot, Bertrand | 2022-09-08 06:49:13 | Re: [PATCH] Query Jumbling for CALL and SET utility statements |