Laurette Cisneros <laurette@nextbus.com> writes:
> Yeah I think that could have happened since I was running it several times and had
> cancelled it (ctrl-c) it a couple of those times. Could be the backend of one
> cancelled run hadn't finished what it was doing and if that was renabling
> triggers it could have walked on it.
Sounds like we've got the explanation, then.
I've just committed fixes into 7.3 to prevent this scenario in future.
The patch is probably too large to risk back-patching into 7.2.* though.
regards, tom lane
