Maybe that risk could be lowered if instead of a flag, we stored the minimal global xmin needed to prune at least one tuple.
I like the idea. The question is whether the chances of a Prunable page being looked up again and again in presence of a long running transaction are high enough to justify adding 4 bytes to page header.
