Re: Re: Vaccuuming every db in cluster fails to eliminate "execute a full-database VACUUM in..."

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Re: Vaccuuming every db in cluster fails to eliminate "execute a full-database VACUUM in..."
Дата
Msg-id 12329.1286725954@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Vaccuuming every db in cluster fails to eliminate "execute a full-database VACUUM in..."  (Robert Burgholzer <rburghol@vt.edu>)
Ответы Re: Re: Vaccuuming every db in cluster fails to eliminate "execute a full-database VACUUM in..."  (Robert Burgholzer <rburghol@vt.edu>)
Список pgsql-admin
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

В списке pgsql-admin по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: build from Source: 9.0.1 / 9.1-alpha1 cannot build modules
Следующее
От: Robert Burgholzer
Дата:
Сообщение: Re: Re: Vaccuuming every db in cluster fails to eliminate "execute a full-database VACUUM in..."