Re: LogwrtResult contended spinlock

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Subject: Re: LogwrtResult contended spinlock
Date: 2024-04-05 11:54:45
Message-ID: 202404051154.am63tvpedo5p@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Couldn't push: I tested with --disable-atomics --disable-spinlocks and
the tests fail because the semaphore for the atomic variables is not
always initialized. This is weird -- it's like a client process is
running at a time when StartupXLOG has not initialized the variable ...
so the initialization in the other place was not completely wrong.
I'll investigate after lunch. Here's v16.

Álvaro Herrera PostgreSQL Developer —
"XML!" Exclaimed C++. "What are you doing here? You're not a programming
"Tell that to the people who use me," said XML.

Attachment Content-Type Size
v16-0001-Make-XLogCtl-log-Write-Flush-Result-accessible-w.patch text/x-diff 9.5 KB
v16-0002-Add-logCopyResult.patch text/x-diff 4.8 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2024-04-05 12:20:44 Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs
Previous Message Amit Kapila 2024-04-05 11:47:17 Re: Synchronizing slots from primary to standby