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

From: bt22nakamorit <bt22nakamorit(at)oss(dot)nttdata(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: ps command does not show walsender's connected db
Date: 2022-10-07 09:43:51
Message-ID: 6b632b1b3d29a8823e09d73fd931f416@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2022-10-07 16:59 Fujii Masao wrote:

> s/subscriber/publisher ?

I did not understand what this means.

> Thanks for the patch!
>
> -
> + printf("fork child process\n");
> + printf(" am_walsender: %d\n", am_walsender);
> + printf(" am_db_walsender: %d\n", am_db_walsender);
>
> The patch seems to include the debug code accidentally.
> Except this, the patch looks good to me.

I apologize for the silly mistake.
I edited the patch and attached it to this mail.

Best,
Tatsuhiro Nakamori

Attachment Content-Type Size
pslogirep2.patch text/x-diff 616 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2022-10-07 09:56:37 Re: Eliminating SPI from RI triggers - take 2
Previous Message Amit Langote 2022-10-07 09:26:56 Re: Eliminating SPI from RI triggers - take 2