Re: Remove unneeded check for XLH_INSERT_ALL_FROZEN in heap_xlog_insert

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: Melanie Plageman <melanieplageman(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: Tomáš Vondra <tv(at)fuzzy(dot)cz>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Subject: Re: Remove unneeded check for XLH_INSERT_ALL_FROZEN in heap_xlog_insert
Date: 2025-06-24 17:53:39
Message-ID: 2a6a9303-4979-4e20-a8b9-e138902e1cb7@vondra.me
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6/24/25 19:41, Melanie Plageman wrote:
> Hi,
>
> I noticed that 8e03eb92e9a forgot one line when reverting 39b66a91bd.
> There is an extraneous check for XLH_INSERT_ALL_FROZEN_SET in
> heap_xlog_insert() -- even though heap_insert() never freezes tuples.
> It doesn't hurt anything, but I found it confusing, so I think it is
> worth removing. I don't think it's worth backpatching, so I don't know
> if that means that this commit shouldn't go in master until after we
> branch.

Thanks for noticing this. I'd probably be +0.5 to backpatch this, even
if it's ultimately harmless, just to keep the code not confusing.

regards

--
Tomas Vondra

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-06-24 18:21:56 Re: problems with toast.* reloptions
Previous Message Álvaro Herrera 2025-06-24 17:45:15 Re: queryId constant squashing does not support prepared statements