Re: VACUUM FULL results in deadlock - Mailing list pgsql-bugs

From Tom Lane
Subject Re: VACUUM FULL results in deadlock
Date
Msg-id 27094.1562360279@sss.pgh.pa.us
Whole thread Raw
In response to Re: VACUUM FULL results in deadlock  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> I agree that you should not be running 32 full vacuums at once, much
> less in a loop, but if you do, they shouldn't result in weird corruption
> such as the ones reported.

BTW, looking at the OIDs in the original problem report, they are for
pg_authid and pg_shdepend, both of which are shared catalogs.  It does not
seem terribly surprising to me that sets of operations that take out
exclusive locks on such catalogs are subject to deadlocks, especially not
when you consider that yet other sessions also have need to read those
catalogs.  So I'm more or less in agreement with Robert that the deadlock
errors aren't very interesting.  But I still concur with Alvaro that
those other error messages probably shouldn't be happening.

            regards, tom lane



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15898: pg_dump error not able to restore complete dump
Next
From: Peter Geoghegan
Date:
Subject: Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«