auxiliary processes in pg_stat_ssl
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: pgsql-hackers@lists.postgresql.org
Date: 2019-09-04T15:15:35Z
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
I just noticed that we list auxiliary processes in pg_stat_ssl: 55432 13devel 28627=# select * from pg_stat_ssl ; pid │ ssl │ version │ cipher │ bits │ compression │ client_dn │ client_serial │ issuer_dn ───────┼─────┼─────────┼────────────────────────┼──────┼─────────────┼───────────┼───────────────┼─────────── 28618 │ f │ │ │ │ │ │ │ 28620 │ f │ │ │ │ │ │ │ 28627 │ t │ TLSv1.3 │ TLS_AES_256_GCM_SHA384 │ 256 │ f │ │ │ 28616 │ f │ │ │ │ │ │ │ 28615 │ f │ │ │ │ │ │ │ 28617 │ f │ │ │ │ │ │ │ (6 filas) 55432 13devel 28627=# select pid, backend_type from pg_stat_activity ; pid │ backend_type ───────┼────────────────────────────── 28618 │ autovacuum launcher 28620 │ logical replication launcher 28627 │ client backend 28616 │ background writer 28615 │ checkpointer 28617 │ walwriter (6 filas) 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.) -- Álvaro Herrera http://www.twitter.com/alvherre