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 | 20210407215625.syzdpwew4j47hhgl@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?
Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? |
| Список | pgsql-hackers |
On Wed, Apr 07, 2021 at 04:22:55PM -0400, Bruce Momjian wrote: > aOn Wed, Apr 7, 2021 at 04:15:50PM -0400, Tom Lane wrote: > > Bruce Momjian <bruce@momjian.us> writes: > > > Patch applied. I am ready to adjust this with any improvements people > > > might have. Thank you for all the good feedback we got on this, and I > > > know many users have waited a long time for this feature. > > > > For starters, you could try to make the buildfarm green again. > > Wow, that's odd. The cfbot was green, so I never even looked at the > buildfarm. I will look at that now, and the CVS log issue. Sorry about that. The issue came from animals with jit_above_cost = 0 outputting more lines than expected. I fixed that by using the same query as before in explain.sql, as they don't generate any JIT output. I also added the queryid to the csvlog output and fixed the documentation that mention how to create a table to access the data.
Вложения
В списке pgsql-hackers по дате отправления: