Re: Index tuple count != heap tuple count problem identified]

> > -----Original Message-----
> > From: pgsql-hackers-owner@hub.org [mailto:pgsql-hackers-owner@hub.org]On
> > Behalf Of Tom Lane
> > 
> > You'll probably recall reports of messages like this out of VACUUM:
> > NOTICE:  Index ind1: NUMBER OF INDEX' TUPLES (2002) IS NOT THE 
> > SAME AS HEAP' (3003).
> > I've figured out the cause (or at least a cause) of this condition.
> > 
> > The CREATE INDEX operation has only bothered to index the non-dead
> > tuples.  So, VACUUM's little sanity check fails.
>
> 
> Is it wrong to change the implementation of CREATE INDEX ?
> I have a fix.
> It needs the change of duplicate check(tuplesort->btbuild) and
> I've thougth that it would be better to change it after the release 
> of 7.0.   

Well, it seems we better do something about it before 7.0 is released. 
Now it seems we have to decide to change CREATE INDEX, or modify VACUUM.

--  Bruce Momjian                        |  http://www.op.net/~candle pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026