Re: auxiliary processes in pg_stat_ssl - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: auxiliary processes in pg_stat_ssl
Date
Msg-id 20191112215008.GA607@alvherre.pgsql
Whole thread Raw
In response to Re: auxiliary processes in pg_stat_ssl  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On 2019-Nov-04, Stephen Frost wrote:

> Based on what we claim in our docs, it does look like 'client_port IS
> NOT NULL' should work.  I do think we might want to update the docs to
> make it a bit more explicit, what we say now is:
> 
> TCP port number that the client is using for communication with this
> backend, or -1 if a Unix socket is used
> 
> We don't explain there that NULL means the backend doesn't have an
> external connection even though plenty of those entries show up in every
> instance of PG.  Perhaps we should add this:
> 
> If this field is null, it indicates that this is an internal process
> such as autovacuum.
> 
> Which is what we say for 'client_addr'.

Seems sensible.  Done.  Thanks

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: auxiliary processes in pg_stat_ssl
Next
From: Alvaro Herrera
Date:
Subject: Re: [PATCH] Do not use StdRdOptions in Access Methods