Hi everyone,
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]?
Best,
Manuel
[1] https://www.postgresql.org/message-id/CA%2Bu7OA6pL%2B7Xm_NXHLenxffe3tCr3gTamVdr7zPjcWqW0RFM-A%40mail.gmail.com