Re: sync_standbys_defined read/write race on startup - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: sync_standbys_defined read/write race on startup
Date
Msg-id Z_eMOVsxebE6X4--@paquier.xyz
Whole thread Raw
In response to Re: sync_standbys_defined read/write race on startup  ("Maksim.Melnikov" <m.melnikov@postgrespro.ru>)
Responses Re: sync_standbys_defined read/write race on startup
List pgsql-hackers
On Thu, Apr 10, 2025 at 10:12:34AM +0300, Maksim.Melnikov wrote:
> but I am afraid we are loosing this.
>
>    if (WalSndCtl->sync_standbys_status & SYNC_STANDBY_INIT)
>    {
>       if ((WalSndCtl->sync_standbys_status & SYNC_STANDBY_DEFINED) == 0 ||
>          lsn <= WalSndCtl->lsn[mode])
>       {
>          LWLockRelease(SyncRepLock);
>          return;
>       }
>    }
> [...]
> +  else if (lsn <= WalSndCtl->lsn[mode])
> +  {
> +     LWLockRelease(SyncRepLock);
> +     return;
> +   }
>
> What do you think?

Hmm, yeah.  Instead of last, it would be better to put it in second
place perhaps, for clarity?  That would be the same at the end, but we
would be slightly more consistent with the past logic regarding the
ordering.  Does that look OK to you?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: wrong comments in rewriteTargetListIU
Next
From: Amit Kapila
Date:
Subject: Re: Enhance 'pg_createsubscriber' to retrieve databases automatically when no database is provided.