public inbox for [email protected]
help / color / mirror / Atom feedFrom: David G. Johnston <[email protected]>
To: Subramanian,Ramachandran <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Trying to understand Tuple Header
Date: Sun, 3 May 2026 12:48:47 -0700
Message-ID: <CAKFQuwbRKbjk4JPefgT6s64hN-i47a1nZO6O4j-+h48er6uyvw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<CAKFQuwawOYYR=Dfa3tWsKOd-baJ-hV7SKMj9FHiMnd9f-=vNAg@mail.gmail.com>
<[email protected]>
On Sun, May 3, 2026 at 12:25 PM Subramanian,Ramachandran <
[email protected]> 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.
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Trying to understand Tuple Header
In-Reply-To: <CAKFQuwbRKbjk4JPefgT6s64hN-i47a1nZO6O4j-+h48er6uyvw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox