From: | Sami Imseih <samimseih(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christoph Berg <myon(at)debian(dot)org>, Lukas Fittl <lukas(at)fittl(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, ma lz <ma100(at)hotmail(dot)com> |
Subject: | Re: query_id: jumble names of temp tables for better pg_stat_statement UX |
Date: | 2025-03-26 00:56:29 |
Message-ID: | 70BA294B-5A33-4F47-A637-8011C1F279CB@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
> If I get the difference right, semantically would apply to concepts
> related to linguistics, but that's not what we have here, so you are
> using a more general term.
FWIW, the pg_stat_statements docs in a few places refer to
queries that may look different but have the same meaning
as “semantically equivalent”, this is why I used the same
terminology here. But, I have no issue with the simplified
rewrite either.
The patch LGTM as well.
Regards,
Sami Imseih
Amazon Web Services (AWS)
From | Date | Subject | |
---|---|---|---|
Next Message | Phillip Diffley | 2025-03-26 03:56:38 | Re: Replication slot WAL reservation |
Previous Message | Michael Paquier | 2025-03-26 00:34:02 | Re: query_id: jumble names of temp tables for better pg_stat_statement UX |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2025-03-26 01:04:13 | Re: Query ID Calculation Fix for DISTINCT / ORDER BY and LIMIT / OFFSET |
Previous Message | Rafael Thofehrn Castro | 2025-03-26 00:52:03 | Re: Proposal: Progressive explain |