MultiXactMemberControlLock contention on a replica

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: MultiXactMemberControlLock contention on a replica
Date: 2021-02-12 19:11:30
Message-ID: 76AD9A74-E518-4D2F-A4B7-EBB6203530C3@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On a whole fleet of load-balanced replicas, we saw an incident where one particular query started backing up on MultiXactMemberControlLock and multixact_member. There was no sign of this backup on the primary. Under what conditions would there be enough multixact members on a replica (where you can't do UPDATE / SELECT FOR UPDATE / FOR SHARE) to start spilling to disk?
--
-- Christophe Pettus
xof(at)thebuild(dot)com

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Noah Bergbauer 2021-02-12 20:44:56 Re: Preventing free space from being reused
Previous Message Karthik Kumar Kondamudi 2021-02-12 18:46:05 Insert into on conflict, data size upto 3 billion records