Re: VACUUM FULL results in deadlock

On Thu, Jul 4, 2019 at 9:12 AM Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com> wrote:
> Did anyone try to verify this? I found a number of other race
> conditions where VACUUM causes errors such as "ERROR: found unexpected
> null value in index "i0", "invalid input syntax for type boolean", or
> "missing chunk number 0 for toast value 13171 in pg_toast_2619".
> Fixing this would help me to narrow down these issues.

I don't know whether or not this is a bug, but my guess is that it
isn't. pg_database and several other system catalogs are shared
relations, which means that they are shared by all databases. So, it's
not too surprising that you could get some interaction between VACUUM
FULL command in different databases. Routine use of VACUUM FULL is
something that should be avoided, so it doesn't seem like a huge
problem to me that you can't run 32 of them at the same time.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company