Home > mailing lists

Possible causes for "tuple concurrently updated" error - Mailing list pgsql-general

From	Jacob Scott
Subject	Possible causes for "tuple concurrently updated" error
Date	May 5, 2016 17:45:37
Msg-id	CA+yM-qb=dNwCS147n7wbh8Uq8Y-uqoNewfeJ+4TOgWwdZVAJFg@mail.gmail.com Whole thread Raw
Responses	Re: Possible causes for "tuple concurrently updated" error (Alvaro Herrera <alvherre@2ndquadrant.com>)
List	pgsql-general

Hi,

I'm seeing a "tuple concurrently updated" error thrown while executing UPDATE statements. I've attempted to diligently review previous threads on this error (e.g., https://www.google.com/webhp?ie=UTF-8#q=tuple+concurrently+updated+update+site:postgresql.org) but am confused about what classes of queries can conflict to cause this error.

It seems clear from previous threads that
- two concurrent ANALYZE queries on the same table can cause this this error.
- some access control/DDL statements (e.g. GRANT) run concurrently can cause this error.
Can a "VACUUM ANALYZE $TABLE" (e.g., from autovacuum) concurrent with a "UPDATE $TABLE" cause this error?
Can two concurrent "UPDATE $TABLE" queries which touch completely disjoint sets of rows (e.g. where clause on primary key with disjoint filters) cause this error?

Thanks,

Jacob

From: "David G. Johnston"
Date: 05 May 2016, 17:30:00
Subject: Re: Function PostgreSQL 9.2

From: Alvaro Herrera
Date: 05 May 2016, 17:46:29
Subject: Re: Possible causes for "tuple concurrently updated" error