Re: vacuumdb parallel has a deadlock detected in 9.5.4

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Francisco Olarte <folarte(at)peoplecall(dot)com>
Cc: hubert depesz lubaczewski <depesz(at)depesz(dot)com>, huang <foggyglass(at)163(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: vacuumdb parallel has a deadlock detected in 9.5.4
Date: 2016-09-29 17:10:57
Message-ID: 20160929171057.GA426369@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message 德哥 2016-09-30 02:27:17 Re: BUG #14345: run multi-PG9.6 on One Host, hang when checkpoint
Previous Message Heikki Linnakangas 2016-09-29 17:08:19 Re: BUG #14344: string_agg(DISTINCT ..) crash