Re: auxiliary processes in pg_stat_ssl
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: pgsql-hackers@lists.postgresql.org
Cc: Robert Haas <robertmhaas@gmail.com>, Kuntal Ghosh <kuntalghosh.2007@gmail.com>
Date: 2019-11-04T13:25:59Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
pg_stat_activity: document client_port being null
- c5e8ea978d88 13.0 landed
-
pg_stat_{ssl,gssapi}: Show only processes with connections
- 5c46e7d82e88 13.0 landed
On 2019-Sep-04, Alvaro Herrera wrote: > I just noticed that we list auxiliary processes in pg_stat_ssl: [...] > But this seems pointless. Should we not hide those? Seems this only > happened as an unintended side-effect of fc70a4b0df38. It appears to me > that we should redefine that view to restrict backend_type that's > 'client backend' (maybe include 'wal receiver'/'wal sender' also, not > sure.) [crickets] Robert, Kuntal, any opinion on this? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services