From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Kuntal Ghosh <kuntalghosh.2007@gmail.com>
Subject: Re: auxiliary processes in pg_stat_ssl
Date: Tue, 12 Nov 2019 18:50:08 -0300
Message-ID: <20191112215008.GA607@alvherre.pgsql> (raw)
In-Reply-To: <20191104160605.GC6962@tamriel.snowman.net>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, sfrost@snowman.net, robertmhaas@gmail.com, pgsql-hackers@lists.postgresql.org, kuntalghosh.2007@gmail.com
Subject: Re: auxiliary processes in pg_stat_ssl
In-Reply-To: <20191112215008.GA607@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox