Horton
Menu

Re: Use proc_exit() in WalRcvWaitForStartPosition

Fujii Masao <masao.fujii@gmail.com>

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

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()