Re: MultiXact\SLRU buffers configuration - Mailing list pgsql-hackers

From Gilles Darold
Subject Re: MultiXact\SLRU buffers configuration
Date
Msg-id 636f694a-4d69-d6d9-78d1-c88714f3e2e0@darold.net
Whole thread Raw
In response to Re: MultiXact\SLRU buffers configuration  (Andrey Borodin <x4mmm@yandex-team.ru>)
Responses Re: MultiXact\SLRU buffers configuration
List pgsql-hackers
Le 08/12/2020 à 18:52, Andrey Borodin a écrit :
Hi Gilles!

Many thanks for your message!

8 дек. 2020 г., в 21:05, Gilles Darold <gilles@darold.net> написал(а):

I know that this report is not really helpful 
Quite contrary - this benchmarks prove that controllable reproduction exists. I've rebased patches for PG11. Can you please benchmark them (without extending SLRU)?

Best regards, Andrey Borodin.

Hi,


Running tests yesterday with the patches has reported log of failures with error on INSERT and UPDATE statements:


ERROR:  lock MultiXactOffsetControlLock is not held


After a patch review this morning I think I have found what's going wrong. In patch v6-0001-Use-shared-lock-in-GetMultiXactIdMembers-for-offs.patch I think there is a missing reinitialisation of the lockmode variable to LW_NONE inside the retry loop after the call to LWLockRelease() in src/backend/access/transam/multixact.c:1392:GetMultiXactIdMembers(). I've attached a new version of the patch for master that include the fix I'm using now with PG11 and with which everything works very well now.


I'm running more tests to see the impact on the performances to play with multixact_offsets_slru_buffers, multixact_members_slru_buffers and multixact_local_cache_entries. I will reports the results later today.

-- 
Gilles Darold
http://www.darold.net/
Attachment

pgsql-hackers by date:

Previous
From: Amit Khandekar
Date:
Subject: Speeding up GIST index creation for tsvectors
Next
From: Pavel Stehule
Date:
Subject: Re: On login trigger: take three