Re: Addition of authenticated ID to pg_stat_activity - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Addition of authenticated ID to pg_stat_activity
Date
Msg-id 20210426191811.sp3o77doinphyjhu@alap3.anarazel.de
Whole thread Raw
In response to Addition of authenticated ID to pg_stat_activity  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Addition of authenticated ID to pg_stat_activity  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Hi,

On 2021-04-26 11:34:16 +0900, Michael Paquier wrote:
> 9afffcb has added the concept of authenticated identity to the
> information provided in log_connections for audit purposes, with this
> data stored in each backend's port.  One extra thing that can be
> really useful for monitoring is the capability to track this
> information directly in pg_stat_activity.

I'm getting a bit worried about the incremental increase in
pg_stat_activity width - it's probably by far the view that's most
viewed interactively. I think we need to be careful not to add too niche
things to it. This is especially true for columns that may be wider.

It'd be bad for discoverability, but perhaps something like this, that's
not that likely to be used interactively, would be better done as a
separate function that would need to be used explicitly?


A select * from pg_stat_activity on a plain installation, connecting
over unix socket, with nothing running, is 411 chars wide for me...

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Use simplehash.h instead of dynahash in SMgr
Next
From: Stephen Frost
Date:
Subject: Re: Addition of authenticated ID to pg_stat_activity