David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> We could also do something like the attached just in case we're
> barking up the wrong tree.
Yeah, checking indisvalid isn't a bad idea. I'd put another
one further down, just before the DROP of table ab, so we
can see the state both before and after the unstable tests.
regards, tom lane