Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
Evgeniy Efimkin <efimkin@yandex-team.ru>
From: Evgeny Efimkin <efimkin@yandex-team.ru>
To: pgsql-hackers@lists.postgresql.org
Cc: Julien Rouhaud <julien.rouhaud@free.fr>
Date: 2019-07-31T08:54:18Z
Lists: pgsql-hackers
What reason to use pg_atomic_uint64? In docs: occured - > occurred
Commits
-
Clarify description of pg_stat_statements columns
- b4deefc39b93 15.0 landed
- 3b57d5af7435 14.0 landed
-
Fix wording in description of pg_stat_statements.toplevel
- f9e6d00df029 14.0 landed
-
Mention that toplevel is part of pg_stat_statements key.
- 7531fcb1fcf5 14.0 landed
-
adjust query id feature to use pg_stat_activity.query_id
- 9660834dd8bf 14.0 landed
-
Update copyright for 2021
- ca3b37487be3 14.0 cited
-
Take the statistics collector out of the loop for monitoring backends'
- b13c9686d084 8.2.0 cited