Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 64FEC1337B48 for ; Sun, 10 Oct 2010 12:52:43 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 94775-03 for ; Sun, 10 Oct 2010 15:52:35 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 5432E1337B4C for ; Sun, 10 Oct 2010 12:52:35 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o9AFqYLv012330; Sun, 10 Oct 2010 11:52:34 -0400 (EDT) To: Robert Burgholzer cc: pgsql-admin@postgresql.org Subject: Re: Re: Vaccuuming every db in cluster fails to eliminate "execute a full-database VACUUM in..." In-reply-to: References: Comments: In-reply-to Robert Burgholzer message dated "Sun, 10 Oct 2010 11:35:34 -0400" Date: Sun, 10 Oct 2010 11:52:34 -0400 Message-ID: <12329.1286725954@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201010/87 X-Sequence-Number: 35828 Robert Burgholzer writes: > So, as I mentioned, I have tried to get this straightened out by > vacuuming all in --single mode, but to no avail. I executed the > following command, to see which tables were in trouble: > SELECT relname, age(relfrozenxid) FROM pg_class WHERE relkind = 'r'; > And found a table listed, that DOES NOT exist any longer. Yeah? What happens if you try to select from that table? If there is a row in pg_class that for some reason didn't get deleted when the table was dropped, you could just manually remove that row (ie, DELETE FROM pg_class WHERE ... as superuser). You'd still need another VACUUM to get the database's datfrozenxid updated, but after that things should be OK. regards, tom lane