pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: pavan95 <pavan.postgresdba@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: tuple concurrently updated
Date: Tue, 28 Aug 2018 06:45:42 -0700 (MST)
Message-ID: <1535463942466-0.post@n3.nabble.com> (raw)
In-Reply-To: <2be8ebca-fecc-51f4-39d7-9869941c679a@posteo.de>
References: <986488f7-ff29-5dff-9425-5fcd6dcbb68a@posteo.de>
	<1378566276.366027624.1535454005687.JavaMail.root@zimbra82-e14.priv.proxad.net>
	<99342cd8-c2f6-31bd-f8e4-5c65658b1a2f@posteo.de>
	<1233975696.366149748.1535454938944.JavaMail.root@zimbra82-e14.priv.proxad.net>
	<cc5734b5-7706-1873-4640-67c51a42cb23@posteo.de>
	<f737db87-9ca8-a90c-c29d-fd9638a8a3cf@posteo.de>
	<114865725.367018989.1535461805284.JavaMail.root@zimbra82-e14.priv.proxad.net>
	<2be8ebca-fecc-51f4-39d7-9869941c679a@posteo.de>

Hi Walter,

Why can't you go with a postgres service restart in order to get rid of this
error?

>DELETE FROM planet_osm_line WHERE osm_id = -166570; 
>FEHLER:  tuple concurrently updated 

Concurrent transactions can update or delete one or more of those rows
before DELETE can lock the rows (at least with the default isolation level
READ COMMITTED). This would result in your error message.

To defend against this race condition, lock the rows in the SELECT with FOR
UPDATE (or other options)

Regards,
Pavan



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html




view thread (28+ messages)  latest in thread

Message-ID: <1535463942466-0.post@n3.nabble.com>
Permalink:  ../1535463942466-0.post@n3.nabble.com/
Also on:    postgresql.org/message-id/1535463942466-0.post@n3.nabble.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: pavan.postgresdba@gmail.com
  Subject: Re: tuple concurrently updated
  In-Reply-To: <1535463942466-0.post@n3.nabble.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox