Re: Use proc_exit() in WalRcvWaitForStartPosition - Mailing list pgsql-hackers

From Chao Li
Subject Re: Use proc_exit() in WalRcvWaitForStartPosition
Date
Msg-id A87FC1BD-A0BD-4B0E-A8D8-1ABF32287817@gmail.com
Whole thread
In response to Re: Use proc_exit() in WalRcvWaitForStartPosition  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers

> On Apr 16, 2026, at 11:34, Fujii Masao <masao.fujii@gmail.com> wrote:
>
> On Mon, Apr 13, 2026 at 8:33 AM Chao Li <li.evan.chao@gmail.com> wrote:
>> Okay, yes, that was a bit redundant. I changed it to “to ereport(FATAL)” in v3.
>>
>> After that change, the line went over 80 columns, so I also adjusted a few nearby lines to keep everything within
the80-column limit. There is no content change. 
>
> Thanks for updating the patch! I've pushed it.
>
> Regards,
>
> --
> Fujii Masao

Hi Fujii san, thank you very much for pushing.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/







pgsql-hackers by date:

Previous
From: shveta malik
Date:
Subject: Re: Fix tab completion after EXCEPT (...) in IMPORT FOREIGN SCHEMA
Next
From: Fujii Masao
Date:
Subject: Re: Use XLogRecPtrIsValid() instead of negated XLogRecPtrIsInvalid