Re: Fwd: Vacuum Full + Cluster + Vacuum full = non removable dead rows - Mailing list pgsql-performance

From Tom Lane
Subject Re: Fwd: Vacuum Full + Cluster + Vacuum full = non removable dead rows
Date
Msg-id 14512.1282137722@sss.pgh.pa.us
Whole thread Raw
In response to Fwd: Vacuum Full + Cluster + Vacuum full = non removable dead rows  (Alexandre de Arruda Paes <adaldeia@gmail.com>)
Responses Re: Fwd: Vacuum Full + Cluster + Vacuum full = non removable dead rows  (Alexandre de Arruda Paes <adaldeia@gmail.com>)
List 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 by date:

Previous
From: Alexandre de Arruda Paes
Date:
Subject: Fwd: Vacuum Full + Cluster + Vacuum full = non removable dead rows
Next
From: Clemens Eisserer
Date:
Subject: Are Indices automatically generated for primary keys?