pg_attribute_relid_attnam_index problem after log disk filled up - Mailing list pgsql-sql

From Palle Girgensohn
Subject pg_attribute_relid_attnam_index problem after log disk filled up
Date
Msg-id 39AA8BC3.3047D8CF@partitur.se
Whole thread Raw
Responses Re: pg_attribute_relid_attnam_index problem after log disk filled up  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-sql
Hi!

What's this? What to do? Shall I bother?

pp=> vacuum;
NOTICE:  Index pg_attribute_relid_attnam_index: NUMBER OF
INDEX' TUPLES (3094) IS NOT THE SAME AS HEAP' (3093)

The database is rather large, and the time to run vacuum is too
short, so it feels like something is stopping the vacuum too
early. The problem started when the log partition (where
postmaster logging output is written) was full, and some
backends crashed. This is fixed, but it seems that postgres is
not fully recovered.

PostgreSQL 6.5.2 on i386-unknown-freebsd3.3, compiled by cc 
Running on FreeBSD 3.5-RELEASE  (SMP kernel).

Cheers,
Palle

--         Partitur Informationsteknik AB    
Wenner-Gren Center             +46 8 566 280 02  
113 46 Stockholm           +46 70 785 86 02  
Sweden                   girgen@partitur.se


pgsql-sql by date:

Previous
From: "Sherwin Daganato"
Date:
Subject: better way
Next
From: Tom Lane
Date:
Subject: Re: pg_attribute_relid_attnam_index problem after log disk filled up