Re: Replace known_assigned_xids_lck by memory barrier - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Replace known_assigned_xids_lck by memory barrier
Date
Msg-id 20230816200715.GB2908487@nathanxps13
Whole thread Raw
In response to Re: Replace known_assigned_xids_lck by memory barrier  (Michail Nikolaev <michail.nikolaev@gmail.com>)
Responses Re: Replace known_assigned_xids_lck by memory barrier
List pgsql-hackers
On Wed, Aug 16, 2023 at 09:29:10PM +0200, Michail Nikolaev wrote:
> As answer: probably we need to change
> "If we know that we're holding ProcArrayLock exclusively, we don't
> need the read barrier."
> to
> "If we're removing xid, we don't need the read barrier because only
> the startup process can remove and add xids to KnownAssignedXids"

Ah, that explains it.  v5 of the patch is attached.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

Attachment

pgsql-hackers by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: PostgreSQL 16 RC1 + GA release dates
Next
From: Peter Geoghegan
Date:
Subject: Re: run pgindent on a regular basis / scripted manner