Tom Lane wrote:
> 2. In VAC FULL and CLUSTER, tell index rebuild not to wait around for
> INSERT_IN_PROGRESS or DELETE_IN_PROGRESS tuples. I believe that the
> price of this would be not re-verifying the integrity of unique indexes.
> Which is kind of annoying, but then again rechecking data cons
I discovered $subject while continuing to test my patch. The problem
occurs because many parts of the backend are in the habit of releasing
lock on system catalogs as soon as they've updated whatever they wanted
to update. This means that we can encounter INSERT_IN_PROGRESS or
DELETE_IN_PROGRESS
