Received: from bastuba.partitur.se ([212.209.169.194]) by hub.org (8.10.1/8.10.1) with ESMTP id e7SFuxC25794 for ; Mon, 28 Aug 2000 11:56:59 -0400 (EDT) Received: from elbas.partitur.se (elbas.partitur.se [212.209.169.222]) by bastuba.partitur.se (8.9.3/8.9.3) with ESMTP id RAA67098; Mon, 28 Aug 2000 17:56:51 +0200 (CEST) (envelope-from girgen@partitur.se) Received: from partitur.se (localhost.partitur.se [127.0.0.1]) by elbas.partitur.se (8.9.3/8.9.3) with ESMTP id RAA79513; Mon, 28 Aug 2000 17:56:51 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <39AA8BC3.3047D8CF@partitur.se> Date: Mon, 28 Aug 2000 17:56:51 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: pg_attribute_relid_attnam_index problem after log disk filled up Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200008/312 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