Re: Get rid of WALBufMappingLock - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Get rid of WALBufMappingLock
Date
Msg-id CAPpHfduHe3cHkEgRAGjG6qLrsFuS2M0vD5fniEgQBF9kBipBFA@mail.gmail.com
Whole thread Raw
In response to Re: Get rid of WALBufMappingLock  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-hackers
On Fri, Feb 7, 2025 at 1:39 PM Alexander Korotkov <aekorotkov@gmail.com> wrote:
> Good, thank you.  I think 0001 patch is generally good, but needs some
> further polishing, e.g. more comments explaining how does it work.

Two things comes to my mind worth rechecking about 0001.
1) Are XLogCtl->InitializeReserved, XLogCtl->InitializedUpTo and
XLogCtl->xlblocks always page-aligned?  Because algorithm seems to be
sensitive to that.  If so, I would propose to explicitly comment that
and add corresponding asserts.
2) Check if there are concurrency issues between
AdvanceXLInsertBuffer() and switching to the new WAL file.

------
Regards,
Alexander Korotkov
Supabase



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: proposal - plpgsql - support standard syntax for named arguments for cursors
Next
From: Japin Li
Date:
Subject: Re: proposal - plpgsql - support standard syntax for named arguments for cursors