Re: IO in wrong state on riscv64

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, greg(at)burd(dot)me
Subject: Re: IO in wrong state on riscv64
Date: 2025-10-23 07:52:29
Message-ID: CA+hUKGKt5o70MB0Yj8QYNOjR3xTH8fTJQ09WdkvA_Rdg-Qag8w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 23, 2025 at 8:00 PM Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
> Unfortunately, this change doesn't lead to change in disassembly of
> pgaio_io_wait(), produced with clang-19 -O1. That is, I'm getting the same
> disassembly as the one I sent you before (error/pgaio_io_wait.asm).

Oh, I think this should work better:

#define pg_read_barrier_impl() \
do { pg_compiler_barrier_impl();
__atomic_thread_fence(__ATOMIC_ACQUIRE); } while (0)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2025-10-23 08:12:43 Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
Previous Message Shlok Kyal 2025-10-23 07:49:24 Re: issue with synchronized_standby_slots