Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending

From: Xuneng Zhou <xunengzhou(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending
Date: 2026-06-08 08:43:31
Message-ID: CABPTF7Vg1CTf49c4gvYu-6-0h7LNSqgWe5_+63FcmTgeqseK1w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Jun 8, 2026 at 1:49 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Sat, Jun 06, 2026 at 08:45:26PM +0800, Xuneng Zhou wrote:
> > Sorry for being late. One nit for the patch -- would it be better to
> > use AmWalSenderProcess() for identification to save the include?
> > +#include "replication/walsender.h"
>
> In the startup sequence, MyBackendType is updated to B_WAL_SENDER a
> couple of lines after am_walsender. One or the other don't really
> matter; they're both right.

Yeah, both of them work well. To use AmWalSenderProcess(), we would
need to include src/include/miscadmin.h, whereas using am_walsender
requires including “replication/walsender.h”. I’m just wondering
whether using AmWalSenderProcess() would result in less coupling
between pgstat and replication.

--
Regards,
Xuneng Zhou
HighGo Software Co., Ltd.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2026-06-08 11:59:56 BUG #19514: pg_hba error when configuring SSL Replication
Previous Message Michael Paquier 2026-06-08 05:48:55 Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending