Re: Use proc_exit() in WalRcvWaitForStartPosition

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Chao Li <li(dot)evan(dot)chao(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 03:34:40
Message-ID: CAHGQGwGV0gAwhmoBi_AwqJP8CGUO8AQtjBS5szft-WCzzG04+g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2026-04-16 03:59:41 Re: Fix tab completion after EXCEPT (...) in IMPORT FOREIGN SCHEMA
Previous Message Chao Li 2026-04-16 03:32:40 repack: clarify final phase of concurrent mode in file header comment