Manuel Rigger <rigger.manuel@gmail.com> writes:
> When running multiple threads that operate on distinct databases, a
> "DROP STATISTICS" sometimes results in an error "ERROR: tuple
> concurrently updated". Would it be useful to make this error
> reproducible, or could this be expected, similar to the VACUUM
> deadlocks [1]?
I think it'd be worth running to ground, at least. One could imagine that
the error is coming from one session trying to delete a statistics row
that some other session has updated-and-not-yet-committed; but then the
question is why there's not sufficient interlocking to avoid that.
regards, tom lane