Re: Notice in logg file
Tom, we fixed this, right?
grzegorz.przezdziecki@crn.pl writes:
PostgreSQL 6.5.1 on i686-pc-linux-gnu, compiled by gcc 2.7.2.3
Apr 28 03:06:05 ziutek logger: NOTICE: Index
tb_klienci_id_klienci_key: NUMBER OF INDEX' TUPLES (10652)
IS NOT THE SAME AS HEAP' (10634)This can happen if there are other transactions open while the VACUUM
runs. It's not real critical --- the cross-check between index and
table tuple count is just not bright enough to consider the possibility
of "zombie" tuples (killed, but not dead yet because there are other
transactions that can still see them). I'd like to improve the cross-
check so it doesn't emit bogus notices, but haven't figured out how yet.If you see it even when the VACUUM is the only transaction running,
then you might be well advised to drop and re-create the index.regards, tom lane
--
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, Pennsylvania 19026Import Notes
Reply to msg id not found: 3970.956936340@sss.pgh.pa.us
Bruce Momjian <pgman@candle.pha.pa.us> writes:
Tom, we fixed this, right?
It's still on the TODO list, AFAIK...
regards, tom lane
-----Original Message-----
From: pgsql-hackers-owner@hub.org [mailto:pgsql-hackers-owner@hub.org]On
Behalf Of Tom LaneBruce Momjian <pgman@candle.pha.pa.us> writes:
Tom, we fixed this, right?
It's still on the TODO list, AFAIK...
As for the cases such that NUMBER OF INDEX TUPLES < HEAP,
we know at least one of the cause. I have had a fix for it and would
commit it in a week or so(Currently my local branch is broken due
to configure tree change). But as for the cases such that NUMBER
OF INDEX TUPLES > HEAP,the cause seems to be not clear yet.
Regards.
Hiroshi Inoue
Inoue@tpf.co.jp