Horton
Menu

Re: Use proc_exit() in WalRcvWaitForStartPosition

Chao Li <li.evan.chao@gmail.com>

View thread
From: Chao Li <li.evan.chao@gmail.com>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: Xuneng Zhou <xunengzhou@gmail.com>, Andreas Karlsson <andreas@proxel.se>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2026-04-16T04:02:48Z
Lists: 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 the 80-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/

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Use proc_exit() for walreceiver exit in WalRcvWaitForStartPosition()