Hello,

yesterday I took our database down and started in single user mode.
After reindexing of three tables I thought a vacuum would be a good idea.

backend> VACUUM FULL VERBOSE ANALYZE
WARNING: Index pg_statistic_relid_att_index: NUMBER OF INDEX' TUPLES
(163) IS NOT THE SAME AS HEAP' (345).
Recreate the index.
WARNING: Index pg_statistic_relid_att_index: NUMBER OF INDEX' TUPLES
(5) IS NOT THE SAME AS HEAP' (345).
Recreate the index.
WARNING: Index pg_toast_16408_index: NUMBER OF INDEX' TUPLES (2) IS NOT
THE SAME AS HEAP' (7).
Recreate the index.

Should these errors worry me? What do they mean? IS there anything I
need to do / should have done?

TIA

/Ulrich


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Ulrich Wisser <ulrich.wisser@relevanttraffic.se> writes:[color=blue]
> WARNING: Index pg_statistic_relid_att_index: NUMBER OF INDEX' TUPLES
> (163) IS NOT THE SAME AS HEAP' (345).
> Recreate the index.[/color]
[color=blue]
> Should these errors worry me?[/color]

Yeah, they should. A REINDEX will probably get you out of the immediate
problem, but the more interesting question is how you got to be missing
index entries in the first place. Have you had any crashes or hardware
problems lately? What PG version is this?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Hi Tom,
[color=blue][color=green]
>>WARNING: Index pg_statistic_relid_att_index: NUMBER OF INDEX' TUPLES
>>(163) IS NOT THE SAME AS HEAP' (345).
>> Recreate the index.[/color]
>[color=green]
>>Should these errors worry me?[/color]
>
> Yeah, they should. A REINDEX will probably get you out of the immediate
> problem, but the more interesting question is how you got to be missing
> index entries in the first place. Have you had any crashes or hardware
> problems lately? What PG version is this?[/color]

PG version 7.3.4
No hardware problems or crashes I know of. I do a "vacuum full analyze"
once every night and never did see these problems. Only yesterday after
I used reindex on three tables did I see these problems.

I will try to reindex the database tonight.

Thanks

Ulrich


---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)