Re: pg_stat_activity.client_addr sometimes null for host connections

From: Erik Wienhold <ewie(at)ewie(dot)name>
To: Rui DeSousa <rui(at)crazybean(dot)net>
Cc: "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_stat_activity.client_addr sometimes null for host connections
Date: 2023-05-05 00:47:24
Message-ID: 106621723.1703032.1683247644104@office.mailbox.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> On 05/05/2023 01:54 CEST Rui DeSousa <rui(at)crazybean(dot)net> wrote:
>
> Could it be that the process you are seeing is a parallel worker? That would
> not have client_addr populated as only the leader process has client_addr
> populated.

That's it. They're indeed all parallel workers. I didn't know that. I always
found datname is not null and usename is not null to be sufficient for only
considering client connections. Safes me a few keystrokes from now.

Thanks a lot!

--
Erik

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message ?????????? RMUTT CPE IX 2023-05-05 11:03:07 How to bring Pgpool-II virtual IP up?
Previous Message Rui DeSousa 2023-05-04 23:54:45 Re: pg_stat_activity.client_addr sometimes null for host connections