From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Sami Imseih <samimseih(at)gmail(dot)com> |
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:27:40 |
Message-ID: | 1189112.1742869660@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Sami Imseih <samimseih(at)gmail(dot)com> writes:
> For example, I have seen users add comments to SQLs to differentiate
> similar SQLs coming from different tenants. This patch makes this no longer a
> somewhat decent workaround to overcome the fact that pg_stat_statements
> does not track schemas or search path.
Well, the workaround is different, but that doesn't mean there is no
workaround. You just need to alter a table alias in the query:
select * from foo s1;
select * from foo s2;
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.
So yeah, it's a nontrivial behavioral change. But I think on the
whole it's likely to be more useful. We could always revert the
change during beta if we get too much pushback.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sami Imseih | 2025-03-25 02:38:35 | Re: query_id: jumble names of temp tables for better pg_stat_statement UX |
Previous Message | Sami Imseih | 2025-03-25 01:51:14 | Re: query_id: jumble names of temp tables for better pg_stat_statement UX |
From | Date | Subject | |
---|---|---|---|
Next Message | vignesh C | 2025-03-25 02:29:11 | Re: [18] CREATE SUBSCRIPTION ... SERVER |
Previous Message | James Hunter | 2025-03-25 02:23:26 | Re: a pool for parallel worker |