Re: walsender.c comment with no context is hard to understand - Mailing list pgsql-hackers

From Peter Smith
Subject Re: walsender.c comment with no context is hard to understand
Date
Msg-id CAHut+PukgSkO=mA8-dcSVXyTGGFaus0eZjOL0gacwQzMQ1UpHw@mail.gmail.com
Whole thread Raw
In response to Re: walsender.c comment with no context is hard to understand  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: walsender.c comment with no context is hard to understand
List pgsql-hackers
On Fri, Jun 28, 2024 at 4:18 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
...
> Shouldn't the check for flushptr (if (flushptr < targetPagePtr +
> reqLen)) be moved immediately after the call to WalSndWaitForWal().
> The comment seems to suggests the same: "Make sure we have enough WAL
> available before retrieving the current timeline. .."

OK, I have changed the code as suggested. Please see the attached v2 patch.

make check-world was successful.

======
Kind Regards,
Peter Smith.
Fujitsu Australia

Attachment

pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: collect_corrupt_items_vacuum.patch
Next
From: Michael Paquier
Date:
Subject: Creation of REL_17_STABLE and upcoming Commit Fest 2024-07