On Tue, Mar 19, 2019 at 1:37 PM Alexander Korotkov <a.korot...@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
