Re: query_id: jumble names of temp tables for better pg_stat_statement UX

Поиск
Список
Период
Сортировка
От Sami Imseih
Тема Re: query_id: jumble names of temp tables for better pg_stat_statement UX
Дата
Msg-id CAA5RZ0uNofEXfEfNw3uRN3D3oXkFPQ_s+huLLHMKR_+MCk8RPQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: query_id: jumble names of temp tables for better pg_stat_statement UX  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: query_id: jumble names of temp tables for better pg_stat_statement UX
Re: query_id: jumble names of temp tables for better pg_stat_statement UX
Список 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)



В списке pgsql-hackers по дате отправления: