postgresql pageinspect what does t_infomask, t_infomask2 comparison with integers really mean?

All we need is an easy explanation of the problem, so here it is.

create or replace function heap_page(relname text, pageno integer)
    table ( ctid tid,state text,xmin text,xmax text,hhu text,hot text,t_ctid tid)
    as $$
    (pageno,lp)::text::tid as ctid,
    case lp_flags
        when 0 then 'unused'
        when 1 then 'normal'
        when 2 then 'redirect to '|| lp_off
        when 3 then 'dead'
    end as state,
    t_xmin || case
    when (t_infomask & 256) > 0 then 'c'
    when (t_infomask & 512) > 0 then 'a'
    else ''
    end as xmin,
    t_xmax || case
    when (t_infomask & 1024) >0 then 'c'
    when (t_infomask & 2048) >0 then 'a'
    else ''
    end as xmax,
    case when (t_infomask2 & 16384) >0 then 't' end as hhu,
    case when (t_infomask2 & 32768) >0 then 't' end as hot,
    from heap_page_items
    (get_raw_page(relname, pageno))
    order by lp
    $$ language sql;
I can understand the manual bitwise operator & example.

But here I don’t understand all the comparisons t_infomask and t_infomask2 with variant integer.

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

You can find that information in src/include/access/htup_details.h.

About t_infomask:

 * information stored in t_infomask:
#define HEAP_HASNULL            0x0001  /* has null attribute(s) */
#define HEAP_HASVARWIDTH        0x0002  /* has variable-width attribute(s) */
#define HEAP_HASEXTERNAL        0x0004  /* has external stored attribute(s) */
#define HEAP_HASOID_OLD         0x0008  /* has an object-id field */
#define HEAP_XMAX_KEYSHR_LOCK   0x0010  /* xmax is a key-shared locker */
#define HEAP_COMBOCID           0x0020  /* t_cid is a combo CID */
#define HEAP_XMAX_EXCL_LOCK     0x0040  /* xmax is exclusive locker */
#define HEAP_XMAX_LOCK_ONLY     0x0080  /* xmax, if valid, is only a locker */

 /* xmax is a shared locker */

#define HEAP_XMIN_COMMITTED     0x0100  /* t_xmin committed */
#define HEAP_XMIN_INVALID       0x0200  /* t_xmin invalid/aborted */
#define HEAP_XMAX_COMMITTED     0x0400  /* t_xmax committed */
#define HEAP_XMAX_INVALID       0x0800  /* t_xmax invalid/aborted */
#define HEAP_XMAX_IS_MULTI      0x1000  /* t_xmax is a MultiXactId */
#define HEAP_UPDATED            0x2000  /* this is UPDATEd version of row */
#define HEAP_MOVED_OFF          0x4000  /* moved to another place by pre-9.0
                                         * VACUUM FULL; kept for binary
                                         * upgrade support */
#define HEAP_MOVED_IN           0x8000  /* moved from another place by pre-9.0
                                         * VACUUM FULL; kept for binary
                                         * upgrade support */

About t_infomask2:

 * information stored in t_infomask2:
#define HEAP_NATTS_MASK         0x07FF  /* 11 bits for number of attributes */
/* bits 0x1800 are available */
#define HEAP_KEYS_UPDATED       0x2000  /* tuple was updated and key cols
                                         * modified, or tuple deleted */
#define HEAP_HOT_UPDATED        0x4000  /* tuple was HOT-updated */
#define HEAP_ONLY_TUPLE         0x8000  /* this is heap-only tuple */

#define HEAP2_XACT_MASK         0xE000  /* visibility-related bits */

So t_infomask & 256 means that the transaction stored in xmin is marked committed, and t_infomask & 512 means that that the transaction stored in xmin is rolled back or invalid. t_infomask & 1024 and t_infomask & 2048 are the same for xmax.

These are so called “hint bits” that provide a shortcut to commit log information about the visibility of the tuple.

t_infomask2 & 16384 means that the tuple was updated with a HOT update, and t_infomask2 & 32768 means that the tuple is a heap-only tuple.

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from or, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply