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

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

From: Jerry Gamache <jerry(dot)gamache(at)idilia(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(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:23:22
Message-ID: 4B7315BA.1070904@idilia.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Yes, I have PID in the logs now. Problem was observed around 13h30, and 
there was no log output between 13h18 and 13h30.
There are messages for table_b (pid 18350) and table_c (pid 18406), but 
none for table_a.

Alvaro Herrera 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?
>
>   


Attachment: pg_842_log_output.txt
Description: text/plain (3.0 KB)

In response to

Responses

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2010-02-10 20:26:24
Subject: Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze
Previous:From: Alvaro HerreraDate: 2010-02-10 20:02:49
Subject: Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze

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