From: Noah Misch <noah@leadboat.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Alexander Lakhin <exclusion@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Assert in heapgettup_pagemode() fails due to underlying buffer change
Date: Thu, 6 Jun 2024 12:07:02 -0700
Message-ID: <20240606190702.cd.nmisch@google.com> (raw)
In-Reply-To: <CA+TgmoYbxzL4Zexu6cAZSrjYNRKVn+7t6Pccn+TaVry3sefT+w@mail.gmail.com>
References: <7ed10231-ce47-03d5-d3f9-4aea0dc7d5a4@gmail.com>
<CA+TgmoYbxzL4Zexu6cAZSrjYNRKVn+7t6Pccn+TaVry3sefT+w@mail.gmail.com>
On Thu, Jun 06, 2024 at 12:36:32PM -0400, Robert Haas wrote:
> On Thu, Jun 6, 2024 at 6:00 AM Alexander Lakhin <exclusion@gmail.com> wrote:
> > Am I missing something or the the page buffer indeed lacks locking there?
>
> 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/20240512171658.7e.nmisch@google.com (Hot standby queries see
transient all-zeros pages).
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: noah@leadboat.com, robertmhaas@gmail.com, exclusion@gmail.com
Subject: Re: Assert in heapgettup_pagemode() fails due to underlying buffer change
In-Reply-To: <20240606190702.cd.nmisch@google.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