From: | Jacob Scott <jacob(dot)scott(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Possible causes for "tuple concurrently updated" error |
Date: | 2016-05-05 06:52:47 |
Message-ID: | CA+yM-qb=dNwCS147n7wbh8Uq8Y-uqoNewfeJ+4TOgWwdZVAJFg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 | Date | Subject | |
---|---|---|---|
Next Message | Berend Tober | 2016-05-05 07:40:57 | Re: Function PostgreSQL 9.2 |
Previous Message | drum.lucas@gmail.com | 2016-05-05 06:42:21 | Re: Function PostgreSQL 9.2 |