Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
| От | Julien Rouhaud |
|---|---|
| Тема | Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? |
| Дата | |
| Msg-id | 20210408163829.o37wgnsrwdbrew4u@nol обсуждение исходный текст |
| Ответ на | Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? (Bruce Momjian <bruce@momjian.us>) |
| Ответы |
Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
|
| Список | pgsql-hackers |
On Thu, Apr 08, 2021 at 11:34:25AM -0400, Bruce Momjian wrote: > > OK, let's get some details. First, pg_stat_statements.queryid already > exists (no underscore), and I don't think anyone wants to change that. > > pg_stat_activity.queryid is new, but I can imagine cases where you would > join pg_stat_activity to pg_stat_statements to get an estimate of how > long the query will take --- having one using an underscore and another > one not seems odd. Indeed, and also being able to join with a USING clause rather than an ON could also save some keystrokes. But unfortunately, we already have (userid, dbid) on pg_stat_statements side vs (usesysid, datid) on pg_stat_activity side, so this unfortunately won't fix all the oddities.
В списке pgsql-hackers по дате отправления: