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+Tgmoavept8pK_8pPBptsJn=oTUtF9-caEOG0AqaUHYi7Ycqw@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 Wed, Feb 5, 2020 at 9:32 AM Julien Rouhaud <julien.rouhaud@free.fr> wrote: > There's also the possibility to reserve 1 bit of the hash to know if > this is a utility command or not, although I don't recall right now > all the possible issues with utility commands and some special > handling of them. I'll work on it before the next commitfest. FWIW, I don't really see why it would be bad to have 0 mean that "there's no query ID for some reason" without caring whether that's because the current statement is a utility statement or because there's no statement in progress at all or whatever else. The user probably doesn't need our help to distinguish between "no statement" and "utility statement", right? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: