Re: vacuumdb parallel has a deadlock detected in 9.5.4 - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: vacuumdb parallel has a deadlock detected in 9.5.4
Date
Msg-id 20160929171057.GA426369@alvherre.pgsql
Whole thread Raw
In response to Re: vacuumdb parallel has a deadlock detected in 9.5.4  (Francisco Olarte <folarte@peoplecall.com>)
Responses Re: vacuumdb parallel has a deadlock detected in 9.5.4  (Francisco Olarte <folarte@peoplecall.com>)
List pgsql-bugs
Francisco Olarte wrote:

> I would propose another behaviour, which I think can solve the problem
> without introducing more complex code. Put a couple of flags to vacuum
> only catalog tables / non catalog tables ( I believe this can be
> served by include/exclude schemas too, which will be even more useful
> for other things ). This way one can do a full paralell vacuum of
> non-catalog objects followed by a serial one on catalog objects (
> which should not be too slow on 'normal' databases )

OK, that sounds easier to implement.  Are you going to submit a patch?

--
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: BUG #14344: string_agg(DISTINCT ..) crash
Next
From: 德哥
Date:
Subject: Re: BUG #14345: run multi-PG9.6 on One Host, hang when checkpoint