| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com> |
| Subject: | Re: Generating code for query jumbling through gen_node_support.pl |
| Date: | 2023-02-09 23:12:50 |
| Message-ID: | 3972105.1675984370@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> Tom, did you get a chance to look at what is proposed here and expand
> the use of query_jumble_ignore in the definitions of the nodes rather
> than have an enforced per-file policy in gen_node_support.pl?
Sorry, didn't look at it before.
I'm okay with the pathnodes.h changes --- although surely you don't need
changes like this:
- pg_node_attr(abstract)
+ pg_node_attr(abstract, no_query_jumble)
"abstract" should already imply "no_query_jumble".
I wonder too if you could shorten the changes by making no_query_jumble
an inheritable attribute, and then just applying it to Path and Plan.
The changes in parsenodes.h seem wrong, except for RawStmt. Those node
types are used in parsed queries, aren't they?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-02-09 23:19:06 | Re: Importing pg_bsd_indent into our source tree |
| Previous Message | Andres Freund | 2023-02-09 23:10:13 | Re: Importing pg_bsd_indent into our source tree |