Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activityview?
| От | Robert Haas |
|---|---|
| Тема | Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activityview? |
| Дата | |
| Msg-id | CA+TgmoYyFN3FuiC+E0Ug4ceXmfUYKpmqx6xZdLZq-F9ZJoZutg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activityview? (Julien Rouhaud <julien.rouhaud@free.fr>) |
| Ответы |
Re: Feature improvement: can we add queryId forpg_catalog.pg_stat_activity view?
|
| Список | pgsql-hackers |
On Thu, Aug 1, 2019 at 2:46 AM Julien Rouhaud <julien.rouhaud@free.fr> wrote: > This patch is actually storing the queryid in PGPROC, not in > PgBackendStatus, thus the need for an atomic. I used PGPROC because > the value needs to be available in log_line_prefix() and spi.c, so > pgstat.c / PgBackendStatus didn't seem like the best interface in that > case. Is widening PGPROC is too expensive for this purpose? I doubt it. However, I think that the fact that this patch adds 15 new calls to pg_atomic_write_u64(&MyProc->queryId, ...) is probably not a good sign. It seems like we ought to be able to centralize it better than that. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: