Re: vacuumdb parallel has a deadlock detected in 9.5.4

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: huang <foggyglass(at)163(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: vacuumdb parallel has a deadlock detected in 9.5.4
Date: 2016-09-28 17:25:51
Message-ID: 20160928172551.bxetdmwm7xwy74ue@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Sep 28, 2016 at 09:46:22PM +0800, huang wrote:
> Hi friends,
>
> There is a error deadlock detected in vacuumdb parallel .
> but if I do not use parallel , it has not deadlock detected .

man vacuumdb says about -j option:

>> Note that using this mode together with the -f (FULL) option might cause
>> deadlock failures if certain system catalogs are processed in parallel.

so, while I understand it's not pretty, it's well documented.

Best regards,

depesz

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message hubert depesz lubaczewski 2016-09-28 17:29:37 Re: vacuumdb has a fatal after database rename
Previous Message huang 2016-09-28 13:54:41 vacuumdb has a fatal after database rename