public inbox for [email protected]  

help / color / mirror / Atom feed

From: Michail Nikolaev <[email protected]>
To: Nathan Bossart <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: Tom Lane <[email protected]>
Subject: Re: Replace known_assigned_xids_lck by memory barrier
Date: Wed, 16 Aug 2023 21:29:10 +0200
Message-ID: <CANtu0ohXFhY2gq=D9cHFLfJjLrNMOGcUGR5thJCSpqweNnqbpQ@mail.gmail.com> (raw)
In-Reply-To: <20230816183236.GA2812457@nathanxps13>
References: <CANtu0oh0si=jG5z_fLeFtmYcETssQ08kLEa8b6TQqDm_cinroA@mail.gmail.com>
	<20230814153634.GB1395427@nathanxps13>
	<CANtu0ohnGXW6wfM7eXts=m23A1g9D7s1X0ms7bV3-x5oQugX5g@mail.gmail.com>
	<20230815152224.GA2296544@nathanxps13>
	<CANtu0ogdo86z-+oQVT7LENPPe_W4N5Q4HsisM_Xpf-H=v5vaow@mail.gmail.com>
	<20230816183236.GA2812457@nathanxps13>

Hello, good question!

Thanks for your edits.

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"

Best regards,
Mikhail.

view thread (3+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Replace known_assigned_xids_lck by memory barrier
  In-Reply-To: <CANtu0ohXFhY2gq=D9cHFLfJjLrNMOGcUGR5thJCSpqweNnqbpQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox