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

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

2010-02-10 13:10:26 EST::@:[18301]:ERROR:  canceling autovacuum task
2010-02-10 13:10:26 EST::@:[18301]:CONTEXT:  automatic analyze of table "database1.public.table_d"
2010-02-10 13:10:42 EST::@:[18350]:ERROR:  canceling autovacuum task
2010-02-10 13:10:42 EST::@:[18350]:CONTEXT:  automatic analyze of table "database1.public.table_e"
2010-02-10 13:10:58 EST::@:[18320]:ERROR:  canceling autovacuum task
2010-02-10 13:10:58 EST::@:[18320]:CONTEXT:  automatic analyze of table "database1.public.table_f"
2010-02-10 13:11:00 EST::@:[18350]:ERROR:  canceling autovacuum task
2010-02-10 13:11:00 EST::@:[18350]:CONTEXT:  automatic analyze of table "database1.public.table_g"
2010-02-10 13:11:08 EST::@:[18320]:ERROR:  canceling autovacuum task
2010-02-10 13:11:08 EST::@:[18320]:CONTEXT:  automatic analyze of table "database1.public.table_h"
2010-02-10 13:11:17 EST::@:[18350]:ERROR:  canceling autovacuum task
2010-02-10 13:11:17 EST::@:[18350]:CONTEXT:  automatic analyze of table "database1.public.table_i"
2010-02-10 13:11:22 EST::@:[18320]:ERROR:  canceling autovacuum task
2010-02-10 13:11:22 EST::@:[18320]:CONTEXT:  automatic analyze of table "database1.public.table_j"
2010-02-10 13:11:42 EST::@:[18350]:ERROR:  canceling autovacuum task
2010-02-10 13:11:42 EST::@:[18350]:CONTEXT:  automatic analyze of table "database1.public.table_b"
2010-02-10 13:13:39 EST::@:[18406]:ERROR:  canceling autovacuum task
2010-02-10 13:13:39 EST::@:[18406]:CONTEXT:  automatic analyze of table "database1.public.table_e"
2010-02-10 13:13:39 EST::@:[18395]:ERROR:  canceling autovacuum task
2010-02-10 13:13:39 EST::@:[18395]:CONTEXT:  automatic analyze of table "database1.public.table_g"
2010-02-10 13:14:07 EST::@:[18406]:ERROR:  canceling autovacuum task
2010-02-10 13:14:07 EST::@:[18406]:CONTEXT:  automatic analyze of table "database1.public.table_c"
2010-02-10 13:14:49 EST::@:[18395]:ERROR:  canceling autovacuum task
2010-02-10 13:14:49 EST::@:[18395]:CONTEXT:  automatic analyze of table "database1.public.table_h"
2010-02-10 13:14:49 EST::@:[18406]:ERROR:  canceling autovacuum task
2010-02-10 13:14:49 EST::@:[18406]:CONTEXT:  automatic analyze of table "database1.public.table_k"
2010-02-10 13:14:49 EST::@:[18350]:ERROR:  canceling autovacuum task
2010-02-10 13:14:49 EST::@:[18350]:CONTEXT:  automatic analyze of table "database1.public.table_l"
2010-02-10 13:16:25 EST::@:[18350]:ERROR:  canceling autovacuum task
2010-02-10 13:16:25 EST::@:[18350]:CONTEXT:  automatic analyze of table "database1.public.table_m"
2010-02-10 13:17:13 EST::@:[18395]:ERROR:  canceling autovacuum task
2010-02-10 13:17:13 EST::@:[18395]:CONTEXT:  automatic analyze of table "database1.public.table_i"
2010-02-10 13:18:20 EST::@:[18567]:ERROR:  canceling autovacuum task
2010-02-10 13:18:20 EST::@:[18567]:CONTEXT:  automatic analyze of table "database1.public.table_e"
2010-02-10 13:18:31 EST::@:[18395]:ERROR:  canceling autovacuum task
2010-02-10 13:18:31 EST::@:[18395]:CONTEXT:  automatic analyze of table "database1.public.table_l"