Re: Concurrency bug with vacuum full (cluster) and toast - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Concurrency bug with vacuum full (cluster) and toast
Date
Msg-id CA+TgmoZdjBWMqRThuziwJ+bwL0OMMVpQYeS=DbytbgDFtnZYVw@mail.gmail.com
Whole thread Raw
In response to Re: Concurrency bug with vacuum full (cluster) and toast  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
Responses Re: Concurrency bug with vacuum full (cluster) and toast
List pgsql-hackers
On Tue, Mar 19, 2019 at 1:37 PM Alexander Korotkov
<a.korotkov@postgrespro.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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: New vacuum option to do only freezing
Next
From: Sergey Cherkashin
Date:
Subject: Re: Psql patch to show access methods info