From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Ronan Dunklau <ronan.dunklau@aiven.io>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Failures in constraints regression test, "read only 0 of 8192 bytes"
Date: Fri, 8 Mar 2024 14:36:48 +0100
Message-ID: <61ef0b89-1ec6-4d88-afbd-2ffc2c977511@enterprisedb.com> (raw)
In-Reply-To: <deefcee6-c8bb-40ed-a4e5-6c20648cf043@enterprisedb.com>
References: <CA+hUKGK+5DOmLaBp3Z7C4S-Yv6yoROvr1UncjH2S1ZbPT8D+Zg@mail.gmail.com>
<tWkwfE42CgNg0bJeYH8uTmY9eI3nWIZNqoqACLaw43eRPLnzdNKHXe_WhKHUNaw3bwe9eOs3qumXddY_DpuAkw==@protonmail.internalid>
<e4f94648-4236-4358-b64c-6a935e33658d@enterprisedb.com>
<2185821.Icojqenx9y@aivenlaptop>
<5c5a0015-723a-4fa7-85d5-2f0f47b92094@enterprisedb.com>
<CA+hUKGJvFgkEgbKyPZj4CwjN9=A+ggio3_2xdwnK0Gd8RzAYuw@mail.gmail.com>
<deefcee6-c8bb-40ed-a4e5-6c20648cf043@enterprisedb.com>
On 3/8/24 13:21, Tomas Vondra wrote:
> On 3/8/24 09:33, Thomas Munro wrote:
>> Happened again. I see this is OpenSUSE. Does that mean the file
>> system is Btrfs?
>
>
> It is, but I don't think that matters - I've been able to reproduce this
> locally on my laptop using ext4 filesystem. I'd bet the important piece
> here is -DCLOBBER_CACHE_ALWAYS (and it seems avocet/trilobite are the
> only animals running with this).
>
> Also, if this really is a filesystem (or environment) issue, it seems
> very strange it'd only affect HEAD and not the other branches. So it
> seems quite likely this is actually triggered by a commit.
>
> Looking at the commits from the good/bad runs, I see this:
>
> avocet: good=4c2369a bad=f5a465f
> trilobite: good=d13ff82 bad=def0ce3
>
> That means the commit would have to be somewhere here:
>
> f5a465f1a07 Promote assertion about !ReindexIsProcessingIndex to ...
> 57b28c08305 Doc: fix minor typos in two ECPG function descriptions.
> 28e858c0f95 Improve documentation and GUC description for ...
> a661bf7b0f5 Remove flaky isolation tests for timeouts
> 874d817baa1 Multiple revisions to the GROUP BY reordering tests
> 466979ef031 Replace lateral references to removed rels in subqueries
> a6b2a51e16d Avoid dangling-pointer problem with partitionwise ...
> d360e3cc60e Fix compiler warning on typedef redeclaration
> 8af25652489 Introduce a new smgr bulk loading facility.
> e612384fc78 Fix mistake in SQL features list
> d13ff82319c Fix BF failure in commit 93db6cbda0.
>
> 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.
[1]
https://www.postgresql.org/message-id/flat/1878547.tdWV9SEqCh%40aivenlaptop
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
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: tomas.vondra@enterprisedb.com, thomas.munro@gmail.com, ronan.dunklau@aiven.io, pgsql-hackers@lists.postgresql.org
Subject: Re: Failures in constraints regression test, "read only 0 of 8192 bytes"
In-Reply-To: <61ef0b89-1ec6-4d88-afbd-2ffc2c977511@enterprisedb.com>
* 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