On Fri, 2007-03-02 at 18:37 -0300, Alvaro Herrera wrote:
> Bruce Momjian escribió:
> > Simon Riggs wrote:
> > > CLUSTER does not need changes for HOT, as things stand currently, mainly
> > > because its MVCC behaviour is broken.
> >               ------------------------
> > 
> > That's oddly discouraging.  :-)
> Apparently no one has been bothered enough to fix CLUSTER.

We learned from Csaba just the other day that this is a backdoor used on
production systems. I've not seen anyone admit it before, even though
I've seen it discussed.

People know that CLUSTER works better than VACUUM FULL and they use
that. The reason it hasn't been fixed is because its useful, I observe.

The oddly discouraging bit is that VACUUM FULL is only second best at
the thing its designed to achieve (compaction). Thats why I'm not
enthralled by the prospect of adding code to make VACUUM FULL work with
HOT - ISTM a good opportunity to make it work better.

  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com

---------------------------(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

Reply via email to