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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Index tuple count != heap tuple count problem identified]
Date: 2000-04-06 05:00:22
Message-ID: 25824.954997222@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
>>>> 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.

> It's difficult for me to provide a fix for CREATE INDEX before 7.0 is
> released.
> It's not sufficiently checked and I don't remember details now.

Also, we'd need to change the other index access methods too.  That
doesn't seem to me like a good thing to tackle a week before release...

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Hiroshi InoueDate: 2000-04-06 05:03:56
Subject: RE: Index tuple count != heap tuple count problem identified]
Previous:From: Thomas LockhartDate: 2000-04-06 04:03:19
Subject: Re: [HACKERS] Doc updates

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