Re: ps command does not show walsender's connected db

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: Ian Lawrence Barwick <barwick(at)gmail(dot)com>, bt22nakamorit <bt22nakamorit(at)oss(dot)nttdata(dot)com>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: ps command does not show walsender's connected db
Date: 2022-11-24 07:20:55
Message-ID: Y38bV3KGFdirgfGq@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 22, 2022 at 08:46:22AM +0530, Bharath Rupireddy wrote:
> Are you looking at the latest v3 patch
> https://www.postgresql.org/message-id/4b5691462b994c18ff370aaa84cef0d0%40oss.nttdata.com?
> It has no printf() calls.

Yes, I was looking at v1. v3 can be simpler. All this information in
the Port comes from the startup packet, and the database name would
default to the user name so it can never be NULL. And applied.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message walther 2022-11-24 07:41:46 Re: fixing CREATEROLE
Previous Message Julien Rouhaud 2022-11-24 06:37:23 Re: Allow file inclusion in pg_hba and pg_ident files