| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> |
| 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>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| Subject: | Re: Generating code for query jumbling through gen_node_support.pl |
| Date: | 2023-07-11 05:35:55 |
| Message-ID: | ZKzqO9wXJRe0FW5P@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 11, 2023 at 12:29:29PM +0700, Andrey Lepikhov wrote:
> I vote for only one method based on a query tree structure.
Noted
> BTW, did you think about different algorithms of queryId generation?
Not really, except if you are referring to the possibility of being
able to handle differently different portions of the nodes depending
on a context given by the callers willing to do a query jumbling
computation. (For example, choose to *not* silence the Const nodes,
etc.)
> Auto-generated queryId code can open a way for extensions to have
> easy-supporting custom queryIds.
Extensions can control that at some extent, already.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2023-07-11 05:47:45 | Re: doc: improve the restriction description of using indexes on REPLICA IDENTITY FULL table. |
| Previous Message | Jeevan Chalke | 2023-07-11 05:31:51 | unrecognized node type while displaying a Path due to dangling pointer |