From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of JotaComm
Sent: Wednesday, September 04, 2013 10:57 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Problems with vacuum
Hello, everbody
I have the following problem: My vacuum is running since 2013-08-27 18:58:41.527238-03.
billing=# SELECT localtimestamp(0);
-[ RECORD 1 ]------------------
timestamp | 2013-09-04 11:23:06
billing=# SELECT pg_stat_activity.procpid,pg_
stat_activity.current_query,pg_stat_activity.query_start FROM pg_stat_activity WHERE pg_stat_activity.current_query ~
'public.mensagem'AND pg_stat_activity.procpid!=pg_backend_pid();
-[ RECORD 1 ]-+-----------------------------------------------------------
procpid | 2738
current_query | autovacuum: VACUUM public.mensagem (to prevent wraparound)
query_start | 2013-08-27 18:58:41.527238-03
I tried to cancel it but unsuccessful.
billing=# SELECT pg_cancel_backend(2738);
-[ RECORD 1 ]-----+--
pg_cancel_backend | t
billing=# SELECT localtimestamp(0);
-[ RECORD 1 ]------------------
timestamp | 2013-09-04 11:23:18
billing=# SELECT pg_stat_activity.procpid,pg_stat_activity.current_query,pg_stat_activity.query_start FROM
pg_stat_activityWHERE pg_stat_activity.current_query ~ 'public.mensagem' AND
pg_stat_activity.procpid!=pg_backend_pid();
-[ RECORD 1 ]-+-----------------------------------------------------------
procpid | 2738
current_query | autovacuum: VACUUM public.mensagem (to prevent wraparound)
query_start | 2013-08-27 18:58:41.527238-03
Any idea? Any tips?
Best regards
--
JotaComm
http://jotacomm.wordpress.com
Why do you consider this a problem? Autovacuum is just doing the job it's supposed to do.
How big mensagem table is?
How many autovacuum workers you have? Does this long-running autovacuum prevent other tables from being vacuumed
in-time?
Is there some other long running transaction involving this table and preventing autovacuum from doing its job?
Regards,
Igor Neyman
Regards,