From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Split use of SerialSLRULock, creating SerialControlLock
Date: Tue, 30 Jan 2024 17:13:02 +0000
Message-ID: <E1rUrfS-003s2i-7y@gemulon.postgresql.org> (raw)
Split use of SerialSLRULock, creating SerialControlLock
predicate.c has been using SerialSLRULock (the control lock for its SLRU
structure) to coordinate access to SerialControlData, another of its
numerous shared memory structures; this is unnecessary and confuses
further SLRU scalability work. Create a separate LWLock to cover
SerialControlData.
Extracted from a larger patch from the same author, and some additional
changes by Álvaro.
Author: Dilip Kumar <dilip.kumar@enterprisedb.com>
Discussion: https://postgr.es/m/CAFiTN-vzDvNz=ExGXz6gdyjtzGixKSqs0mKHMmaQ8sOSEFZ33A@mail.gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/7b745d85b80d4492c4df8d9769592c7aad1f63d2
Modified Files
--------------
src/backend/storage/lmgr/lwlocknames.txt | 1 +
src/backend/storage/lmgr/predicate.c | 41 ++++++++++++++++++-------
src/backend/utils/activity/wait_event_names.txt | 1 +
3 files changed, 32 insertions(+), 11 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: alvherre@alvh.no-ip.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Split use of SerialSLRULock, creating SerialControlLock
In-Reply-To: <E1rUrfS-003s2i-7y@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox