| From: | Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: VACUUM FULL results in deadlock |
| Date: | 2019-07-05 22:25:26 |
| Message-ID: | CA+u7OA69k20bBYjKX-avZQsnLZaaP06+Fgki5Xyk4-VeKSBRAA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Jul 5, 2019 at 3:17 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> 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.
>
To clarify (since it came up a couple of times in this thread): The
deadlocks can also be observed with significantly less threads and
(many) statements in between. My initial bug report used 32 threads
and only VACUUM to make it easy to quickly reproduce the deadlocks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manuel Rigger | 2019-07-05 22:27:57 | Re: VACUUM FULL results in deadlock |
| Previous Message | Tom Lane | 2019-07-05 22:22:26 | Re: DISCARD TEMP results in "ERROR: cache lookup failed for type 0" |