Re: Trying to understand Tuple Header - Mailing list pgsql-novice

From David G. Johnston
Subject Re: Trying to understand Tuple Header
Date
Msg-id CAKFQuwbRKbjk4JPefgT6s64hN-i47a1nZO6O4j-+h48er6uyvw@mail.gmail.com
Whole thread
In response to AW: Trying to understand Tuple Header  ("Subramanian,Ramachandran" <ramachandran.subramanian@alte-leipziger.de>)
Responses Re: Trying to understand Tuple Header
AW: Trying to understand Tuple Header
List pgsql-novice
On Sun, May 3, 2026 at 12:25 PM Subramanian,Ramachandran <ramachandran.subramanian@alte-leipziger.de> wrote:

The binary value of t_infomask for both the tuples are identical, but they produce different column values for xmin_commited, xmin_aborted ….  in the SQL  !!!.

 

Am I not seeing something that is obvious?


You didn't re-check the infomask data after running the select query, instead assuming the bits didn't change.  They did.  SELECT is not a read-only operation, it participates in optimizations.  Called "writing hint bits".  Manually evaluating the various tests against the data you did show would have proven that the pre-select-data had zeros where the second query claims there are ones.

David J.

pgsql-novice by date:

Previous
From: "Subramanian,Ramachandran"
Date:
Subject: AW: Trying to understand Tuple Header
Next
From: Tom Lane
Date:
Subject: Re: Trying to understand Tuple Header