Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> I had the idea we were doing that already --- at least I'm pretty sure I
> >> remember it being discussed.  But I see it's not being done in HEAD.
> 
> > Patch to do it attached.  I am thinking we can do something similar in
> > CLUSTER as well.
> 
> Umm ... you'd have to be a lot more conservative in CLUSTER now that
> it's MVCC-safe.  I don't say that CLUSTER can't push up relfrozenxid,
> but there's something wrong if CLUSTER and TRUNCATE are trying to
> push it up the same amount.

No, TRUNCATE will use RecentXmin while the CLUSTER patch I posted uses
OldestXmin, which is what the HeapTupleSatisfiesUpdate test was using.
However, given that Heikki just confirmed that CLUSTER does not freeze
tuples, it's not really possible to do this, so I'll drop the CLUSTER
patch for now.

This means that people using CLUSTER to compact tables won't have the
benefit of advancing relfrozenxid, so they will have to run VACUUM on
those tables at some point anyway, even though there will be no dead
tuples :-(

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

Reply via email to