Re: VACUUM FULL results in deadlock

From: Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(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 22:27:57
Message-ID: CA+u7OA61ia8BSjFmyoOyEjTdEKMLq5OeFOL9ayeCcp5vaq0k1w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I assume that you are talking about the corruptions. I'm still trying
to make them reproducible. So far, I could not reproduce them by
trying to repeatedly replay the recorded statements.

Best,
Manuel

On Fri, Jul 5, 2019 at 7:08 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> 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

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2019-07-05 22:32:32 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
Previous Message Manuel Rigger 2019-07-05 22:25:26 Re: VACUUM FULL results in deadlock