Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
От | Bruce Momjian |
---|---|
Тема | Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? |
Дата | |
Msg-id | 20210408024229.GJ24239@momjian.us обсуждение исходный текст |
Ответ на | Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? (Julien Rouhaud <rjuju123@gmail.com>) |
Ответы |
Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
|
Список | pgsql-hackers |
On Thu, Apr 8, 2021 at 10:38:08AM +0800, Julien Rouhaud wrote: > On Wed, Apr 07, 2021 at 10:31:01PM -0400, Bruce Momjian wrote: > > On Wed, Apr 7, 2021 at 08:54:02PM -0400, Bruce Momjian wrote: > > > > Unless I'm missing something this will output the query id in the next log > > > > line? The new code should be added before the newline is output, and the comma > > > > should also be output before the queryid. > > > > > > Yes, correct, updated patch attached. > > > > Patch applied. > > Thanks! And I agree with using query_id in the new field names while keeping > queryid for pg_stat_statements to avoid unnecessary query breakage. I think we need more feedback from the group. Do people agree with the idea above? The question is what to call: GUC compute_queryid pg_stat_activity.queryid pg_stat_statements.queryid using "queryid" or "query_id", and do they have to match? -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.
В списке pgsql-hackers по дате отправления: