From: | Jameison Martin <jameisonb(at)yahoo(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | "canceling autovacuum time" |
Date: | 2012-02-28 00:53:01 |
Message-ID: | 1330390381.50699.YahooMailNeo@web39402.mail.mud.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm seeing "GMTERROR: canceling autovacuum task" lines in my logs.
2012-02-27 23:53:28 GMTLOG: checkpoint starting: time
>2012-02-27 23:53:31 GMTERROR: canceling autovacuum task
>2012-02-27 23:53:31 GMTCONTEXT: automatic vacuum of table "<somedb>.pg_toast.pg_toast_33254"
>2012-02-27 23:53:32 GMTERROR: canceling autovacuum task
>2012-02-27 23:53:32 GMTCONTEXT: automatic vacuum of table "<somedb>.pg_toast.pg_toast_33485"
>2012-02-27 23:54:29 GMTLOG: automatic vacuum of table "<somedb>.pg_toast.pg_toast_33254": index scans: 1
It was suggested to me that perhaps I had an exclusive lock on the table that was being vacuumed (e.g. that I was running some DDL that was conflicting with the autovacuum). I'm quite certain that I'm not running any DDL at the time this happens, all i'm running are:
* SELECT ... FOR UPDATE
* UPDATE
* INSERT
* DELETE
Does anyone have a suggestions as to what the cause of this error might be?
I'm using Postgres 9.0.
Thanks.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Vitek | 2012-02-28 00:55:39 | strategies for dealing with frequently updated tables |
Previous Message | Jameison Martin | 2012-02-28 00:36:26 | synchronous replication: blocking commit on the master |