From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
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-22 03:16:22 |
Message-ID: | CALj2ACWnRDbazJPDa_O33Bec6f04bVzOzpNiXKJBj0oNCY7BxA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Nov 22, 2022 at 6:14 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> 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?
-1 for back-patching as it's not something critical to any of the
server's operations.
> The patch looks to do the job correctly, still I would leave the extra
> printf() calls in BackendStartup() out.
Are you looking at the latest v3 patch
https://www.postgresql.org/message-id/4b5691462b994c18ff370aaa84cef0d0%40oss.nttdata.com?
It has no printf() calls.
--
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2022-11-22 03:51:25 | Re: perform_spin_delay() vs wait events |
Previous Message | Julien Rouhaud | 2022-11-22 03:06:52 | Re: Proposal: Allow user with pg_monitor role to call pg_stat_reset* functions |