Re: Concurrency bug with vacuum full (cluster) and toast

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Concurrency bug with vacuum full (cluster) and toast
Date: 2019-03-22 18:27:07
Message-ID: CA+TgmoZdjBWMqRThuziwJ+bwL0OMMVpQYeS=DbytbgDFtnZYVw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 19, 2019 at 1:37 PM Alexander Korotkov
<a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> Thank you for pointing, but none of the threads you pointed describe
> this exact problem. Now I see this bug have a set of cute siblings :)

Yeah. I really thought this precise issue -- the interlocking between
the VACUUM of the main table and the VACUUM of the TOAST table -- had
been discussed somewhere before. But I couldn't find that discussion.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sergey Cherkashin 2019-03-22 18:29:09 Re: Psql patch to show access methods info
Previous Message Robert Haas 2019-03-22 18:25:40 Re: New vacuum option to do only freezing