From: Ronan Dunklau <ronan.dunklau@aiven.io>
To: Thomas Munro <thomas.munro@gmail.com>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Failures in constraints regression test, "read only 0 of 8192 bytes"
Date: Fri, 08 Mar 2024 14:40:00 +0100
Message-ID: <2746777.mvXUDI8C0e@aivenlaptop> (raw)
In-Reply-To: <61ef0b89-1ec6-4d88-afbd-2ffc2c977511@enterprisedb.com>
References: <CA+hUKGK+5DOmLaBp3Z7C4S-Yv6yoROvr1UncjH2S1ZbPT8D+Zg@mail.gmail.com>
<deefcee6-c8bb-40ed-a4e5-6c20648cf043@enterprisedb.com>
<61ef0b89-1ec6-4d88-afbd-2ffc2c977511@enterprisedb.com>
Le vendredi 8 mars 2024, 14:36:48 CET Tomas Vondra a écrit :
> > My guess would be 8af25652489, as it's the only storage-related commit.
> >
> > I'm currently running tests to verify this.
>
> Yup, the breakage starts with this commit. I haven't looked into the
> root cause, or whether the commit maybe just made some pre-existing
> issue easier to hit. Also, I haven't followed the discussion on the
> pgsql-bugs thread [1], maybe there are some interesting findings.
>
If that happens only on HEAD and not on 16, and doesn't involve WAL replay,
then it's not the same bug.
--
Ronan Dunklau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: ronan.dunklau@aiven.io, thomas.munro@gmail.com, tomas.vondra@enterprisedb.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Failures in constraints regression test, "read only 0 of 8192 bytes"
In-Reply-To: <2746777.mvXUDI8C0e@aivenlaptop>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox