Re: Non-reproducible AIO failure

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Nico Williams <nico(at)cryptonector(dot)com>, Konstantin Knizhnik <knizhnik(at)garret(dot)ru>, 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 03:45:25
Message-ID: CA+hUKGLSNaMAgSBtjJiCnbyHBoH05Xb60jOOaXwsAQQqrYS=MA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 26, 2025 at 12:37 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> I'm a bit confused by this focus on bitfields - both Alexander and Konstantin
> stated they could reproduce the issue without the bitfields.

Konstantin's message all seem to say it *did* fix it?

But I do apologise for working through the same theory and analysis as
Konstantin had already done earlier. I somehow had the impression
this topic was considered closed, and was reacting to Alexander's
latest email as if it was a new variant of the problem when I wrote
that. ETHREADTOOLONG.

> 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexandra Wang 2025-08-26 03:52:28 Re: SQL:2023 JSON simplified accessor support
Previous Message jian he 2025-08-26 03:26:16 Re: [PATCH] no table rewrite when set column type to constrained domain