Re: Disabling Heap-Only Tuples

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: James Locke <james(dot)locke(dot)uk(at)gmail(dot)com>
Cc: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Disabling Heap-Only Tuples
Date: 2026-05-08 14:35:50
Message-ID: af30RIAO_UZnzkOa@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2026-May-08, James Locke wrote:

> It's the same invariant a cross-page UPDATE relies on, and heap_relocate
> inherits it because the on-disk and WAL record are identical to a regular
> update.

Ah, that makes sense, and I understand why you say this would cause
index bloat.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"The Gord often wonders why people threaten never to come back after they've
been told never to return" (www.actsofgord.com)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ayush Tiwari 2026-05-08 14:40:10 Re: Disallow whole-row index references with virtual generated columns?
Previous Message Nathan Bossart 2026-05-08 14:31:17 Re: Fix typo 586/686 in atomics/arch-x86.h