Re: tuptoaster.c must *not* use SnapshotAny

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Jan Wieck" <JanWieck(at)Yahoo(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tuptoaster.c must *not* use SnapshotAny
Date: 2002-01-16 17:40:25
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA41EB4B6@m0114.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Command Prompt, Inc. 2002-01-16 17:46:32 Re: tuptoaster.c must *not* use SnapshotAny
Previous Message Peter Eisentraut 2002-01-16 17:40:10 Re: backend/po, make update-po works strange