DROP STATISTICS results in "ERROR: tuple concurrently updated"

From: Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com>
To: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: DROP STATISTICS results in "ERROR: tuple concurrently updated"
Date: 2019-07-23 12:01:56
Message-ID: CA+u7OA6rxM-Wz6WaLGZ+mZvMBBd7DbcUUP_B4NJt1AJ65JjXtQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-07-23 16:48:16 BUG #15922: Simple select with multiple exists filters returns duplicates from a primary key field
Previous Message 高 云龙 2019-07-23 08:07:04 A function privilege problem