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

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: Fwd: Vacuum Full + Cluster + Vacuum full = non removable dead rows
Дата
Msg-id 4C6CEE4202000025000348D6@gw.wicourts.gov
обсуждение исходный текст
Ответ на Re: 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
Список pgsql-performance
Alexandre de Arruda Paes <adaldeia@gmail.com> wrote:
> 2010/8/18 Tom Lane <tgl@sss.pgh.pa.us>

>> 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 :-(

> select * from pg_stat_activity where usename='webpa';

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

*ANY* open transaction, including "idle in transaction" including
transactions by other users in other databases will prevent vacuum
from cleaning up rows, for the reasons Tom already gave you.

What do you get from?:

select * from pg_stat_activity where current_query <> '<IDLE>'
  order by xact_start limit 10;

-Kevin

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: in-memory sorting
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Fwd: Vacuum Full + Cluster + Vacuum full = non removable dead rows