mirror of
https://github.com/postgres/postgres.git
synced 2025-10-25 13:17:41 +03:00
Get rid of WALBufMappingLock
Allow multiple backends to initialize WAL buffers concurrently. This way `MemSet((char *) NewPage, 0, XLOG_BLCKSZ);` can run in parallel without taking a single LWLock in exclusive mode. The new algorithm works as follows: * reserve a page for initialization using XLogCtl->InitializeReserved, * ensure the page is written out, * once the page is initialized, try to advance XLogCtl->InitializedUpTo and signal to waiters using XLogCtl->InitializedUpToCondVar condition variable, * repeat previous steps until we reserve initialization up to the target WAL position, * wait until concurrent initialization finishes using a XLogCtl->InitializedUpToCondVar. Now, multiple backends can, in parallel, concurrently reserve pages, initialize them, and advance XLogCtl->InitializedUpTo to point to the latest initialized page. Author: Yura Sokolov <y.sokolov@postgrespro.ru> Co-authored-by: Alexander Korotkov <aekorotkov@gmail.com> Reviewed-by: Pavel Borisov <pashkin.elfe@gmail.com> Reviewed-by: Tomas Vondra <tomas@vondra.me> Tested-by: Michael Paquier <michael@paquier.xyz>
This commit is contained in:
@@ -37,7 +37,7 @@ PG_LWLOCK(3, XidGen)
|
||||
PG_LWLOCK(4, ProcArray)
|
||||
PG_LWLOCK(5, SInvalRead)
|
||||
PG_LWLOCK(6, SInvalWrite)
|
||||
PG_LWLOCK(7, WALBufMapping)
|
||||
/* 7 was WALBufMapping */
|
||||
PG_LWLOCK(8, WALWrite)
|
||||
PG_LWLOCK(9, ControlFile)
|
||||
/* 10 was CheckpointLock */
|
||||
|
||||
Reference in New Issue
Block a user