On 2019-Mar-29, Andrey Borodin wrote: > Here's updated patch with AccessShareLock. > I've tried to stress this with combination of random inserts, vaccuums and > checks. This process neither failed, nor deadlocked. > The patch intentionally contains one superflous line to make gist logically > broken. This triggers regression test of amcheck.
How close are we to this being a committable patch? CF bot complains that it doesn't apply anymore (please rebase), but from past discussion it seems pretty close to ready. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
