Jean-Christophe Praud wrote:
> Hi all,
>
> I've a problem on a heavy loaded database: vacuums don't work since
> about a week. All I got is:
>
> mybase=# vacuum verbose analyze public.mytable;
> INFO: vacuuming "public.mytable"
> (I stop it after hours)
>
> Looking with top and iotop, I see the process takes some cpu and
> disk io time during several minutes, then it seems to fall asleep.
> The process isn't locked according to pg_stat_activity.
What are your vacuum_cost_% parameters?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support