Message-ID: <05fd672f-2eac-4758-91e9-fa7afafa147e@enterprisedb.com>
Date: Fri, 8 Mar 2024 21:48:45 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Failures in constraints regression test, "read only 0 of 8192
 bytes"
Content-Language: en-US
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Ronan Dunklau <ronan.dunklau@aiven.io>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
 Heikki Linnakangas <hlinnaka@iki.fi>
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>
 <61ef0b89-1ec6-4d88-afbd-2ffc2c977511@enterprisedb.com>
 <CA+hUKGKKQJRap2M5EE7XoQRn5-O0h1=p0wkpkGog=87me-g6+g@mail.gmail.com>
From: Tomas Vondra <tomas.vondra@enterprisedb.com>
In-Reply-To: 
 <CA+hUKGKKQJRap2M5EE7XoQRn5-O0h1=p0wkpkGog=87me-g6+g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/05fd672f-2eac-4758-91e9-fa7afafa147e%40enterprisedb.com>
Precedence: bulk


On 3/8/24 21:29, Thomas Munro wrote:
> On Sat, Mar 9, 2024 at 2:36 AM Tomas Vondra
> <tomas.vondra@enterprisedb.com> wrote:
>> On 3/8/24 13:21, Tomas Vondra wrote:
>>> 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.
> 
> Adding Heikki.

I spent a bit of time investigating this today, but haven't made much
progress due to (a) my unfamiliarity with the smgr code in general and
the patch in particular, and (b) CLOBBER_CACHE_ALWAYS making it quite
time consuming to iterate and experiment.

However, the smallest schedule that still reproduces the issue is:

-------------------
test: test_setup

test: create_aggregate create_function_sql create_cast constraints
triggers select inherit typed_table vacuum drop_if_exists
updatable_views roleattributes create_am hash_func errors infinite_recurse
-------------------

I tried to reduce the second step to just "constraints", but that does
not fail. Clearly there's some concurrency at play, and having just a
single backend makes that go away.

regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company