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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Ian Lawrence Barwick <barwick(at)gmail(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(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-22 00:44:43
Message-ID: Y3wbe2dnxh9B4fLF@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 17, 2022 at 01:32:11PM +0900, Ian Lawrence Barwick wrote:
> Fujii-san is marked as committer on the commifest entry for this patch [1];
> are you able to go ahead and get it committed?

That's the state of the patch since the 11th of October. Seeing the
lack of activity, I propose to take care of that myself if there are
no objections, only on HEAD. That could be qualified as a bug, but
that does not seem worth bothering the back-branches, either. Except
if somebody has a different opinion?

The patch looks to do the job correctly, still I would leave the extra
printf() calls in BackendStartup() out.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii.Yuki@df.MitsubishiElectric.co.jp 2022-11-22 01:01:55 RE: Partial aggregates pushdown
Previous Message Nathan Bossart 2022-11-22 00:41:19 wake up logical workers after ALTER SUBSCRIPTION