Hi,
I wonder why the query for monitoring how far away we are from transaction wraparound is returning double value comparing to actual max transaction id which is supported. Recently I had this problem, and Postgres max is ~2bln id instead of 4bln which is returned by this query. Same database which has stopped to prevent wraparound as is seen in the attachment query result.
Could anyone explain or confirm if it is correct?
Thanks,
Michal
I wonder why the query for monitoring how far away we are from transaction wraparound is returning double value comparing to actual max transaction id which is supported. Recently I had this problem, and Postgres max is ~2bln id instead of 4bln which is returned by this query. Same database which has stopped to prevent wraparound as is seen in the attachment query result.
Could anyone explain or confirm if it is correct?
Thanks,
Michal
Attached Files