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.