| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| 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 00:51:04 |
| Message-ID: | 200004060051.UAA21899@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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.
>
> I am inclined to change the check to complain if there are more index
> tuples than table tuples (that's surely wrong), or if there are fewer
> index tuples than committed-live table tuples (ditto), but not to
> complain if it's in between those limits. Comments?
Sounds good to me. I know I never considered such an interaction.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2000-04-06 01:17:45 | RE: Index tuple count != heap tuple count problem identified |
| Previous Message | Tom Lane | 2000-04-06 00:33:51 | Index tuple count != heap tuple count problem identified |