Re: LogwrtResult contended spinlock

Alvaro Herrera <alvherre@alvh.no-ip.org>

From: Alvaro Herrera <alvherre@alvh.no-ip.org>

To: Andres Freund <andres@anarazel.de>

Cc: Alexander Lakhin <exclusion@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Jeff Davis <pgsql@j-davis.com>, pgsql-hackers@lists.postgresql.org, Jaime Casanova <jcasanov@systemguards.com.ec>

Date: 2024-07-04T11:36:40Z

Lists: pgsql-hackers

Okay, so I've pushed the last version after confirming with Alexander
that it works on the Windows x86 machine.  I hope nothing breaks now in
the buildfarm.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/

Commits

Remove bogus assertion in pg_atomic_monotonic_advance_u64
- 768f0c3e21b3 18.0 landed
- 3a9d0d774d90 17.0 landed
Add XLogCtl->logInsertResult
- f3ff7bf83bce 17.0 cited
Operate XLogCtl->log{Write,Flush}Result with atomics
- ee1cbe806dad 17.0 landed
Split XLogCtl->LogwrtResult into separate struct members
- c9920a9068ea 17.0 landed
Introduce atomic read/write functions with full barrier semantics.
- bd5132db558b 17.0 cited
Reduce the number of GetFlushRecPtr() calls done by walsenders.
- e369f3708636 13.0 cited
Remove most volatile qualifiers from xlog.c
- 6ba4ecbf477e 9.5.0 cited