From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Burgholzer <rburghol@vt.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: Re: Vaccuuming every db in cluster fails to eliminate "execute a full-database VACUUM in..."
Date: Sun, 10 Oct 2010 11:52:34 -0400
Message-ID: <12329.1286725954@sss.pgh.pa.us> (raw)
In-Reply-To: <AANLkTikZ35E9UR-49rrNKBDRpu=k3+5aAX6m33o3gJTo@mail.gmail.com>
References: <AANLkTi=YEdR98c-mAW4u2MPhuapXnohsy2tMbaQRS9H3@mail.gmail.com>
<AANLkTikZ35E9UR-49rrNKBDRpu=k3+5aAX6m33o3gJTo@mail.gmail.com>
Robert Burgholzer <rburghol@vt.edu> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, rburghol@vt.edu
Subject: Re: Re: Vaccuuming every db in cluster fails to eliminate "execute a full-database VACUUM in..."
In-Reply-To: <12329.1286725954@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox