Re: FrozenTransactionId - Mailing list pgsql-docs

From Tom Lane
Subject Re: FrozenTransactionId
Date
Msg-id 18782.1473194499@sss.pgh.pa.us
Whole thread Raw
In response to Re: FrozenTransactionId  (Egor Rogov <e.rogov@postgrespro.ru>)
Responses Re: FrozenTransactionId  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: FrozenTransactionId  (Egor Rogov <e.rogov@postgrespro.ru>)
List pgsql-docs
Egor Rogov <e.rogov@postgrespro.ru> writes:
> Right, it does not say that FrozenTransactionId is what appears on disk,
> but what is? There is no such information anywhere in the doc. Since 9.4
> frozen transactions have their normal XIDs preserved, so how a user can
> tell normal transaction from frozen one? This is what needs to be
> explained, I believe.

I'm afraid the answer is "you can't tell".  The infomask bits in tuple
headers aren't exposed via SQL.  If you're really desperate,
contrib/pageinspect would help, but I don't propose mentioning that here.

In general, I'm not really sure why users would care very much at
a tuple-by-tuple level.  Aggregate statistics would be interesting,
which raises the question why contrib/pgstattuple doesn't provide
frozen-tuples counts.

            regards, tom lane


pgsql-docs by date:

Previous
From: Egor Rogov
Date:
Subject: Re: FrozenTransactionId
Next
From: Tom Lane
Date:
Subject: Re: FrozenTransactionId