From: Noah Misch <noah@leadboat.com>
To: pgsql-hackers@postgresql.org
Subject: Re: Inval reliability, especially for inplace updates
Date: Sun, 16 Jun 2024 15:12:05 -0700
Message-ID: <20240616221205.24.nmisch@google.com> (raw)
In-Reply-To: <20240615223718.42.nmisch@google.com>
References: <20240523000548.58.nmisch@google.com>
<20240615223718.42.nmisch@google.com>
On Sat, Jun 15, 2024 at 03:37:18PM -0700, Noah Misch wrote:
> I'm attaching the implementation.
I'm withdrawing inplace150-inval-durability-atcommit-v1.patch, having found
two major problems so far:
1. It sends transactional invalidation messages before
ProcArrayEndTransaction(), so other backends can read stale data.
2. It didn't make the equivalent changes for COMMIT PREPARED.
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
Subject: Re: Inval reliability, especially for inplace updates
In-Reply-To: <20240616221205.24.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