Re: Inval reliability, especially for inplace updates

From: Noah Misch <noah(at)leadboat(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Inval reliability, especially for inplace updates
Date: 2024-06-29 03:11:09
Message-ID: 20240629031109.cb.nmisch@google.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 17, 2024 at 04:58:54PM -0700, Noah Misch wrote:
> attached v2 patch stack.

Rebased. This applies on top of three patches from
https://postgr.es/m/20240629024251.03.nmisch@google.com. I'm attaching those
to placate cfbot, but this thread is for review of the last patch only.

Attachment Content-Type Size
inplace090-LOCKTAG_TUPLE-eoxact-v5.patch text/plain 1.2 KB
inplace110-successors-v5.patch text/plain 44.5 KB
inplace120-locktag-v5.patch text/plain 42.8 KB
inplace160-inval-durability-inplace-v3.patch text/plain 39.9 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2024-06-29 04:38:19 Re: Backporting BackgroundPsql
Previous Message Noah Misch 2024-06-29 02:42:51 Re: race condition in pg_class