Postgres Pro
Downloads
Home   >   mailing lists

RE: Index tuple count != heap tuple count problem identified - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject RE: Index tuple count != heap tuple count problem identified
Date
Msg-id 000401bf9f65$ea1c4de0$2801007e@tpf.co.jp
Whole thread Raw
In response to Index tuple count != heap tuple count problem identified  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Index tuple count != heap tuple count problem identified]  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Tree view 
> -----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.   

Regards.  

Hiroshi Inoue
Inoue@tpf.co.jp

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Index tuple count != heap tuple count problem identified
Next
From: Bruce Momjian
Date:
Subject: Re: Index tuple count != heap tuple count problem identified]