DROP STATISTICS results in "ERROR: tuple concurrently updated" - Mailing list pgsql-bugs

From Manuel Rigger
Subject DROP STATISTICS results in "ERROR: tuple concurrently updated"
Date
Msg-id CA+u7OA6rxM-Wz6WaLGZ+mZvMBBd7DbcUUP_B4NJt1AJ65JjXtQ@mail.gmail.com
Whole thread Raw
Responses Re: DROP STATISTICS results in "ERROR: tuple concurrently updated"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: 高 云龙
Date:
Subject: A function privilege problem
Next
From: PG Bug reporting form
Date:
Subject: BUG #15922: Simple select with multiple exists filters returns duplicates from a primary key field