Re: Tuple concurrency issue in large objects

From: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
To: "Shalini" <shalini(at)saralweb(dot)com>
Cc: "Rene Romero Benavides" <rene(dot)romero(dot)b(at)gmail(dot)com>,"Postgres General" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Tuple concurrency issue in large objects
Date: 2019-12-13 11:55:34
Message-ID: 6afceeda-e645-4892-8cd6-a5bd1fea54bd@manitou-mail.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Shalini wrote:

> > Is there a workaround to this concurrency issue without creating a
> > new large object?

The transaction failing with the "Tuple concurrently updated"
error could be resubmitted by the client, as if it was a
serialization failure.
Or the failure could be prevented by using advisory locks:
https://www.postgresql.org/docs/current/explicit-locking.html

Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message İlyas Derse 2019-12-13 12:31:50 Is there an equivalent to sp_getapplock, sp_releaseapplock in PostgreSql?
Previous Message Pavel Stehule 2019-12-13 09:23:30 Re: How to Change collate & ctype for an existing database?