MIME-Version: 1.0
References: 
 <TYRPR01MB1419579F217CC4332B615589594202@TYRPR01MB14195.jpnprd01.prod.outlook.com>
 <CAA4eK1JF-zny8pGP4Mafk8=mNBCV8A0a1-6HvVd1Q2ZVJW-NJw@mail.gmail.com>
In-Reply-To: 
 <CAA4eK1JF-zny8pGP4Mafk8=mNBCV8A0a1-6HvVd1Q2ZVJW-NJw@mail.gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
Date: Mon, 20 Apr 2026 13:53:47 +0530
Message-ID: 
 <CAA4eK1KbhbNQyhfWa8hMqbhD-6Q1Y91h+WyDVCL_Fct80Z=wxA@mail.gmail.com>
Subject: Re: Fix stats reporting delays in logical parallel apply worker
To: "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAA4eK1KbhbNQyhfWa8hMqbhD-6Q1Y91h%2BWyDVCL_Fct80Z%3DwxA%40mail.gmail.com>
Precedence: bulk

On Fri, Apr 17, 2026 at 12:49=E2=80=AFPM Amit Kapila <amit.kapila16@gmail.c=
om> wrote:
>
> On Fri, Apr 17, 2026 at 8:31=E2=80=AFAM Zhijie Hou (Fujitsu)
> <houzj.fnst@fujitsu.com> wrote:
> >
> > When implementing another feature, I noticed that parallel apply worker=
s
> > currently do not report statistics while idle in their main loop. This =
can cause
> > stats from the last processed transaction to be arbitrarily delayed, es=
pecially
> > when there are long gaps between streamed transactions.
> >
> > The issue is demonstrated in 0002, where a TAP test fails when attempti=
ng to
> > collect stats from a parallel apply worker that has no subsequent trans=
action to
> > trigger a stats report.
> >
> > 0001 fixes this issue by forcing a stats report when the worker is idle=
 in the
> > main loop, matching the behavior already present in LogicalRepApplyLoop=
() for
> > regular logical apply workers.
> >
>
> LGTM. We should backpatch this change.
>

Pushed now.

--=20
With Regards,
Amit Kapila.