Skip site navigation (1) Skip section navigation (2)

Re: ERROR: tuple concurrently updated

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: ERROR: tuple concurrently updated
Date: 2006-12-21 06:33:40
Message-ID: 14457.1166682820@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Stephen Frost <sfrost(at)snowman(dot)net> writes:
>   Subject pretty much says it all.  I've put up with this error in the
>   past when it has caused me trouble but it's now starting to hit our
>   clients on occation which is just unacceptable.

Have you tracked down the exact scenario making it happen?

>   If this is correct then the solution seems to be either add versioning
>   to the SysCache data,

You have provided no evidence that that would fix anything at all.
To my mind a "concurrently updated" failure is more likely to mean
insufficient locking around update operations.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Stephen FrostDate: 2006-12-21 07:37:04
Subject: Re: ERROR: tuple concurrently updated
Previous:From: Tom LaneDate: 2006-12-21 06:12:09
Subject: Re: Question about debugging bootstrapping and catalog entries

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group