Its _always_ that same index. No others have had this problem. Unfortunately, i have no clue how to replicate this. It was happening fairly consistantly before i upgraded from 7.3.3 to 7.3.4 (like nearly every vacuumdb run). Then nothing for a month after going to 7.3.4, and now its happening every vacuumdb run again. On Wed, 05 May 2004 11:30:33 -0400, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Lonni Friedman <netllama@gmail.com> writes: > > All of a sudden last month (after about 3 years) I started getting > > this warning when vacuumdb was run: > > > INFO: Index pg_largeobject_loid_pn_index: Pages 903; Tuples 323847: > > Deleted 0. CPU 0.04s/0.07u sec elapsed 0.10 sec. > > WARNING: Index pg_largeobject_loid_pn_index: NUMBER OF INDEX' TUPLES > > (323847) IS NOT THE SAME AS HEAP' (323802). > > Recreate the index. > > Hmm. Is it always that same index, or have you seen this on other indexes? > > I'm not aware of any known bug in 7.3.* that could lead to this sort of > error. Don't suppose you have any suggestions about how to reproduce > the problem? > > regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
