Re: Regardign RecentFlushPtr in WalSndWaitForWal() - Mailing list pgsql-hackers

From Matthias van de Meent
Subject Re: Regardign RecentFlushPtr in WalSndWaitForWal()
Date
Msg-id CAEze2Wgm=TvEeDmmyR3pF70k1vhbQFC25fUrV3cRk2HdEECxvg@mail.gmail.com
Whole thread Raw
In response to Regardign RecentFlushPtr in WalSndWaitForWal()  (shveta malik <shveta.malik@gmail.com>)
Responses Re: Regardign RecentFlushPtr in WalSndWaitForWal()
List pgsql-hackers
On Mon, 26 Feb 2024 at 12:46, shveta malik <shveta.malik@gmail.com> wrote:
>
> Hi hackers,
>
> I would like to understand why we have code [1] that retrieves
> RecentFlushPtr in WalSndWaitForWal() outside of the loop. We utilize
> RecentFlushPtr later within the loop, but prior to that, we already
> have [2]. Wouldn't [2] alone be sufficient?
>
> Just to check the impact, I ran 'make check-world' after removing [1],
> and did not see any issue exposed by the test at-least.

Yeah, that seems accurate.

> Any thoughts?
[...]
> [2]:
>                 /* Update our idea of the currently flushed position. */
>                 else if (!RecoveryInProgress())

I can't find where this "else" of this "else if" clause came from, as
this piece of code hasn't changed in years. But apart from that, your
observation seems accurate, yes.

Kind regards,

Matthias van de Meent
Neon (https://neon.tech)



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Volatile write caches on macOS and Windows, redux
Next
From: jian he
Date:
Subject: src/include/miscadmin.h outdated comments