public inbox for [email protected]
help / color / mirror / Atom feedFrom: Alexander Lakhin <[email protected]>
To: Noah Misch <[email protected]>
To: Robert Haas <[email protected]>
Cc: pgsql-hackers <[email protected]>
Cc: Thomas Munro <[email protected]>
Subject: Re: Assert in heapgettup_pagemode() fails due to underlying buffer change
Date: Fri, 7 Jun 2024 06:00:00 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<CA+TgmoYbxzL4Zexu6cAZSrjYNRKVn+7t6Pccn+TaVry3sefT+w@mail.gmail.com>
<[email protected]>
Hello Noah,
06.06.2024 22:07, Noah Misch wrote:
>
>> I don't know, but if the locks are really missing now, I feel like the
>> first question is "which commit got rid of them?". It's a little hard
>> to believe that they've never been there and somehow nobody has
>> noticed.
>>
>> Then again, maybe we have; see Noah's thread about in-place updates
>> breaking stuff and some of the surprising discoveries there. But it
>> seems worth investigating.
> $SUBJECT looks more like a duplicate of
> postgr.es/m/flat/[email protected] (Hot standby queries see
> transient all-zeros pages).
Thank you for the reference! Yes, it looks very similar. Though I can't
say the sleep you proposed helps the failure reproduction (I've tried
026_overwrite_contrecord.pl and saw no more frequent failures or so).
My bisect run ended with:
210622c60e1a9db2e2730140b8106ab57d259d15 is the first bad commit
Author: Thomas Munro <[email protected]>
Date: Wed Apr 3 00:03:08 2024 +1300
Provide vectored variant of ReadBuffer().
Other buildfarm failures with this Assert I could find kind of confirm this:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=calliphoridae&dt=2024-04-03%2003%3A32%3A...
(presumably a first failure of this sort)
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tamandua&dt=2024-04-04%2015%3A38%3A16
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=margay&dt=2024-05-07%2004%3A00%3A08
Best regards,
Alexander
view thread (4+ messages)
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Assert in heapgettup_pagemode() fails due to underlying buffer change
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox