RE: Index tuple count != heap tuple count problem identified

> -----Original Message-----
> From: pgsql-hackers-owner(at)hub(dot)org [mailto:pgsql-hackers-owner(at)hub(dot)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.

Regards.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp