> You're right, lazy VACUUM doesn't create this issue. My mistake.
> But VACUUM FULL does.
>
> > I can only see a problem with a partway through vacuum
> full, that aborted.
>
> Exactly.
Can you try give me a hint, why an aborted VACUUM FULL will not allways be
a problem (also for other operations) until you run another VACUUM FULL
that succeeds ?
How do we know, that a (newly) FrozenXid tuple does not still have
a (visible) duplicate ?
Andreas
