Re: Fwd: Vacuum Full + Cluster + Vacuum full = non removable dead rows

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Fwd: Vacuum Full + Cluster + Vacuum full = non removable dead rows
Дата
Msg-id 14512.1282137722@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Fwd: Vacuum Full + Cluster + Vacuum full = non removable dead rows  (Alexandre de Arruda Paes <adaldeia@gmail.com>)
Ответы Re: Fwd: Vacuum Full + Cluster + Vacuum full = non removable dead rows  (Alexandre de Arruda Paes <adaldeia@gmail.com>)
Список pgsql-performance
Alexandre de Arruda Paes <adaldeia@gmail.com> writes:
> I know the problem with VACUUM FULL and bloated Indexes, but I don't
> understand why the table that is not in use by nobody, cant be vacuumed or
> clustered to avoid dead tuples.

There's an open transaction somewhere that VACUUM is preserving the
tuples for.  This transaction need not ever have touched the table,
or ever intend to touch the table --- but VACUUM cannot know that,
so it saves any tuples that the transaction might be entitled to see
if it looked.

> carmen=# select * from vlocks where relname='tp93t'; select * from
> pg_stat_activity where usename='webpa';

You keep on showing us only subsets of pg_stat_activity :-(

Also, if you don't see anything in pg_stat_activity, try pg_prepared_xacts.

            regards, tom lane

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

Предыдущее
От: Alexandre de Arruda Paes
Дата:
Сообщение: Fwd: Vacuum Full + Cluster + Vacuum full = non removable dead rows
Следующее
От: Clemens Eisserer
Дата:
Сообщение: Are Indices automatically generated for primary keys?