Re: IO in wrong state on riscv64

On Sat, Nov 8, 2025 at 1:03 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> You're a brave man to be pushing this into the last-ever release
> of v13 with all of 12 hours remaining till code freeze.  I don't
> mind so much for the newer branches, but I'm feeling nervous
> about the risk/reward ratio for v13.

I figured "adding a no-op compiler barrier where we already believed
there to be a compiler barrier and rely on it crucially" was pretty
safe as these things go, but that's a good point about v13 and I can
revert it in that one branch in a couple of hours if that's the
consensus.