| From: | Sami Imseih <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Christoph Berg <myon(at)debian(dot)org>, 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-25 02:38:35 |
| Message-ID: | CAA5RZ0uNofEXfEfNw3uRN3D3oXkFPQ_s+huLLHMKR_+MCk8RPQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> select * from foo s1;
> select * from foo s2;
ah, thanks for pointing this out. Not as good of a workaround as
a comment since one must change aliases, but at least there is
a workaround...
> As against this, there is probably also a set of people who would
> *like* identical queries on identically-rowtyped tables in different
> schemas to be merged. Right now they have no way to make that happen.
I agree that some may want stats to merge for the same tables,
and others may not. I will suggest this with some hesitation, but why not
make this behavior configurable via a GUC?
We recently introduced query_id_squash_values for controlling
the merge of an IN list, maybe this is another queryId behavior we should
provide a configuration for?
--
Sami Imseih
Amazon Web Services (AWS)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-03-25 02:56:30 | Re: query_id: jumble names of temp tables for better pg_stat_statement UX |
| Previous Message | Tom Lane | 2025-03-25 02:27:40 | Re: query_id: jumble names of temp tables for better pg_stat_statement UX |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2025-03-25 02:52:19 | Re: AIO v2.5 |
| Previous Message | Andres Freund | 2025-03-25 02:30:27 | Re: AIO v2.5 |