I don't know if it's related, but we often have index problems as well. When performing full vacuum, many indexes contain one more row versions than the tables:
WARNING: index "iwiw_start_top_napi_fast_idx" contains 10932 row versions, but table contains 10931 row versions WARNING: index "iwiw_start_top_napi_fast_idx" contains 10932 row versions, but table contains 10931 row versions WARNING: index "iwiw_jatekok_ertek_idx" contains 17 row versions, but table contains 16 row versions WARNING: index "ujtema_nehezseg_idx" contains 696 row versions, but table contains 695 row versions etc... Daniel Tom Lane wrote: > Nagy Daniel <nagy.dan...@telekom.hu> writes: >> I have pg segfaults on two boxes, a DL160G6 and a DL380g5. >> I've just checked their memory with memtest86+ v2.11 >> No errors were detected. >> We also monitor the boxes via IPMI, and there are no signs >> of HW failures. > > Hm. Well, now that 8.4.2 is out, the first thing you ought to do is > update and see if this happens to be resolved by any of the recent > fixes. (I'm not too optimistic about that, because it doesn't look > exactly like any of the known symptoms, but an update is certainly > worth your time in any case.) > > If you still see it after that, please try to extract a reproducible > test case. > > regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
