| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Staroverov Ilja <i(dot)staroverov(at)ftdata(dot)ru> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz> |
| Subject: | Re: Query jumbling ignores XML names, ROLLUP/CUBE, VARIADIC and more |
| Date: | 2026-10-26 18:26:34 |
| Message-ID: | 737423.1793039194@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Staroverov Ilja <i(dot)staroverov(at)ftdata(dot)ru> writes:
> While working on the SQL/JSON patterns in pg_stat_statements [1], I
> looked at the other fields marked query_jumble_ignore, and some of them
> change the results of the queries.
I don't believe that query jumbles have ever been intended to
distinguish every semantic detail of a query tree. To the contrary,
merging together "sufficiently similar" queries has always been
precisely the intention. So there is not one of these things that
deserves the label of bug. We can have a discussion about whether
the original (and clearly intentional) choice to mark a field as
query_jumble_ignore was being too aggressive about what is "similar",
but in each case that's going to be a judgment call.
So rather than submitting a patch and expecting it to get pushed,
you need to try to create some consensus on the -hackers list about
whether these things should be changed. To my mind the benefit of
the doubt should probably go to the existing behaviors.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Sami Imseih | 2026-10-26 18:23:22 | Re: pg_stat_statements replaces SQL/JSON ON EMPTY / ON ERROR keywords with parameters |