Re: VACUUM FULL results in deadlock

Alvaro Herrera <alvherre(at)2ndquadrant(dot)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