Skip site navigation (1) Skip section navigation (2)

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

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: RE: Index tuple count != heap tuple count problem identified
Date: 2000-04-06 01:17:45
Message-ID: 000401bf9f65$ea1c4de0$2801007e@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
> -----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

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2000-04-06 01:24:26
Subject: Re: Index tuple count != heap tuple count problem identified]
Previous:From: Bruce MomjianDate: 2000-04-06 00:51:04
Subject: Re: Index tuple count != heap tuple count problem identified

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group