Skip site navigation (1) Skip section navigation (2)

Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Jerry Gamache <jerry(dot)gamache(at)idilia(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze
Date: 2010-02-10 20:02:49
Message-ID: 20100210200249.GR4922@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-bugs
Jerry Gamache wrote:
> Here is the pg_locks output.
> 
> Alvaro Herrera wrote:
> >Jerry Gamache wrote:

> >>The logs show that the autovacuum of table_b was canceled 20 minutes
> >>ago, but the thread is still alive and blocked.

Well, it's clearly locked on table_b, and that autovac is still running
... maybe it was a previous run that was cancelled?  Do you have the PID
in log_line_prefix?


-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

pgsql-bugs by date

Next:From: Jerry GamacheDate: 2010-02-10 20:23:22
Subject: Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze
Previous:From: Jerry GamacheDate: 2010-02-10 19:49:34
Subject: Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group