Simple Question: In heap tuple header, is *t_xvac* set only FrozenTransactionId or InvalidTransactionId by the heap_execute_freeze_tuple()? I checked that only the HeapTupleHeaderSetXvac macro sets a value to t_xvac, and this macro is only used in the heap_execute_freeze_tuple().
-
-
Replying to @suzuki_hironobu
IIRC t_xvac is historial, used for the vacuum full implementation prior to 9.0. You won't see it in current postgres unless you pg_upgrade from before 9.0.
2 replies 0 retweets 2 likes -
-
Replying to @MengTangmu @suzuki_hironobu
IIRC the idea we've discussed is adding a version marker to pg_class. A new version would be known to have been rewritten by a Postgres release that does not use the old vacuum flags
1 reply 0 retweets 2 likes
Yea. And then at some point we should / need to refuse to upgrade if there's not been a vacuum since point X.
9:45 AM - 15 May 2020
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.