Re: VACUUM FULL results in deadlock

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: VACUUM FULL results in deadlock
Date: 2019-07-05 17:08:22
Message-ID: 29204.1562346502@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

I agree that we probably should look closer rather than just writing this
off. However, without a more concrete report there's no way to look
closer.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-07-05 19:11:24 BUG #15898: pg_dump error not able to restore complete dump
Previous Message Alvaro Herrera 2019-07-05 16:14:33 Re: VACUUM FULL results in deadlock