| 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 16:15:50 |
| Message-ID: | 20100210161549.GD4922@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Jerry Gamache wrote:
> I was also surprised that table_y seemed to be involved. This is not
> a typo. Might be caused by a FK constraint between table_y and
> table_x. From the logs, the autovacuum on table_x was canceled
> before the one on table_y, but the restore only resumed after the
> autovacuum on table_y was canceled. It is possible (but I cannot
> confirm) that the autovacuum thread on table_x was blocked for a
> while after the cancellation message was written to the log. I added
> timestamps to log_line_prefix to be able to give more details if
> this happens again.
Could you try to restore the whole dump again and see if it you can
reproduce it? Maybe decreasing autovacuum_naptime makes it more
probable.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-02-10 18:26:47 | Re: Postgr. 8.2 |
| Previous Message | Jerry Gamache | 2010-02-10 15:54:30 | Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze |