Request a Demo
Home   >   mailing lists

Re: Propagate XLogFindNextRecord error to callers - Mailing list pgsql-hackers

From Anthonin Bonnefoy
Subject Re: Propagate XLogFindNextRecord error to callers
Date
Msg-id CAO6_XqptRqW5b3=BXZ3=OP2YL+7X_CRayCiRwpOySwuHJ2WYtw@mail.gmail.com
Whole thread
In response to Re: Propagate XLogFindNextRecord error to callers  (Mircea Cadariu <cadariu.mircea@gmail.com>)
Responses Re: Propagate XLogFindNextRecord error to callers
Re: Propagate XLogFindNextRecord error to callers
List pgsql-hackers
Tree view 
On Wed, Feb 11, 2026 at 1:16 PM Mircea Cadariu <cadariu.mircea@gmail.com> wrote:
> Indeed. Should we place this initialisation at the top of
> XLogFindNextRecord, before any processing? At that point, there's
> nothing to erase.

That makes sense, I've added the '*errormsg = NULL' at the top of the function.

> You can consider capitalising.

Done
Attachment

pgsql-hackers by date:

Previous
From: "Aya Iwata (Fujitsu)"
Date:
Subject: RE: [WIP]Vertical Clustered Index (columnar store extension) - take2
Next
From: Chao Li
Date:
Subject: Re: Odd usage of errmsg_internal in bufmgr.c