Re: Use proc_exit() in WalRcvWaitForStartPosition

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Xuneng Zhou <xunengzhou(at)gmail(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Use proc_exit() in WalRcvWaitForStartPosition
Date: 2026-04-16 04:02:48
Message-ID: A87FC1BD-A0BD-4B0E-A8D8-1ABF32287817@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Apr 16, 2026, at 11:34, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>
> On Mon, Apr 13, 2026 at 8:33 AM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)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/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-04-16 04:11:52 Re: Use XLogRecPtrIsValid() instead of negated XLogRecPtrIsInvalid
Previous Message shveta malik 2026-04-16 03:59:41 Re: Fix tab completion after EXCEPT (...) in IMPORT FOREIGN SCHEMA