pg_attribute_relid_attnam_index problem after log disk filled up

From: Palle Girgensohn <girgen(at)partitur(dot)se>
To: pgsql-sql(at)postgresql(dot)org
Subject: pg_attribute_relid_attnam_index problem after log disk filled up
Date: 2000-08-28 15:56:51
Message-ID: 39AA8BC3.3047D8CF@partitur.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)partitur(dot)se

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2000-08-28 17:26:22 Re: shared memory leak in 7.0.2?
Previous Message Pierre Padovani 2000-08-28 15:02:02 Re: shared memory leak in 7.0.2?