Re: LogwrtResult contended spinlock

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Subject: Re: LogwrtResult contended spinlock
Date: 2022-03-22 13:49:13
Message-ID: 202203221349.pn6ekl4xivkx@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2022-Mar-21, Andres Freund wrote:

> This patch currently doesn't apply:


> Are you aiming this for v15? Otherwise I'd like to move the entry to the next
> CF. Marked as waiting-on-author.

I'd like to get 0001 pushed to pg15, yes. I'll let 0002 sit here for
discussion, but I haven't seen any evidence that we need it. If others
vouch for it, I can push that one too, but I'd rather have it be a
separate thing.

Álvaro Herrera 48°01'N 7°57'E —
"El miedo atento y previsor es la madre de la seguridad" (E. Burke)

Attachment Content-Type Size
v6-0001-Change-XLogCtl-LogwrtResult-to-use-atomic-ops.patch text/x-diff 22.0 KB
v6-0002-Change-asyncXactLSN-and-WalWriterSleeping-to-atom.patch text/x-diff 4.2 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Michail Nikolaev 2022-03-22 13:52:09 Re: [PATCH] Full support for index LP_DEAD hint bits on standby
Previous Message Julien Rouhaud 2022-03-22 13:38:00 Re: Allow file inclusion in pg_hba and pg_ident files