Re: Non-reproducible AIO failure

From: Ken Marshall <ktm(at)rice(dot)edu>
To: Konstantin Knizhnik <knizhnik(at)garret(dot)ru>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Nico Williams <nico(at)cryptonector(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, rmt(at)lists(dot)postgresql(dot)org
Subject: Re: Non-reproducible AIO failure
Date: 2025-08-26 14:15:13
Message-ID: aK3BcS9OZ/K+2TZA@customer.dllstxx1.pop.starlinkisp.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 26, 2025 at 04:59:54PM +0300, Konstantin Knizhnik wrote:
>
> > But we have observed the generated code being pretty grotty and it's caused
> > more than enough confusion - so let's just replace them with plain uint8's and
> > cast in switches.
>
> +1
>
> May be I am wrong, but it seems to me that after add-moissing-memory-barrier
> patch was applied nobody reproduced assertion failure with replaced
> bitfields.
>

Hi,

I am just a lurker but that was what I saw happen too. No problem with
the replaced bitfields.

Regards,
Ken

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Damien Clochard 2025-08-26 14:17:03 Re: [PATCH] Generate random dates/times in a specified range
Previous Message Kirk Wolak 2025-08-26 14:11:43 Re: [WiP] B-tree page merge during vacuum to reduce index bloat