Re: Add WALRCV_CONNECTING state to walreceiver

From: Xuneng Zhou <xunengzhou(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Rahila Syed <rahilasyed90(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add WALRCV_CONNECTING state to walreceiver
Date: 2026-01-22 10:06:21
Message-ID: CABPTF7W+fMCK4JfdthtXF4gNSVrvoG_DaZ-1CBnDEvEVe4vKkQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Thu, Jan 22, 2026 at 4:08 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Thu, Jan 22, 2026 at 12:37:42PM +0800, Xuneng Zhou wrote:
> > So the view returns no row rather than a row with status = 'stopped'.
> > But for completeness, maybe we should add it.
>
> Yeah, you are making me doubt here, "stopped" is the only state that
> would never show up. After pondering a bit on this one, I have
> removed this part, and applied the rest of 0001 on HEAD after some
> reordering of the items and fixing a <para> markup which was at an
> incorrect location. That's one.
> --
> Michael

Thanks for updating and pushing it.

--
Best,
Xuneng

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2026-01-22 10:15:46 Re: Import Statistics in postgres_fdw before resorting to sampling.
Previous Message Xuneng Zhou 2026-01-22 10:02:54 Re: Add WALRCV_CONNECTING state to walreceiver