Jeff Janes wrote: > c3d09b3bd23f5f6 fixed it so concurrent CIC would not deadlock (or at least > not as reliably as before) by dropping its own snapshot before waiting for > all the other ones to go away. > > With commit 8aa3e47510b969354ea02a, concurrent CREATE INDEX CONCURRENTLY on > different tables in the same database started deadlocking against each > other again quite reliably. > > I think the solution is simply to drop the catalog snapshot as well, as in > the attached.
Pushed to all affected branches, along with a somewhat lame isolationtester test for the condition (since we've already broken this twice and not noticed for long). Thanks for the diagnosis and patch, -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
