Re: transactions getting slon in councurrent environment

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tigran Mkrtchyan <tigran(dot)mkrtchyan(at)desy(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: transactions getting slon in councurrent environment
Date: 2006-12-29 03:42:55
Message-ID: 27724.1167363775@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tigran Mkrtchyan <tigran(dot)mkrtchyan(at)desy(dot)de> writes:
> I got a incorrect or unexpected behavior in concurrent environment.

This is not a bug, nor even surprising. Since you haven't committed
the second transaction, there are a growing number of
dead-but-not-recyclable versions of the updated row. The active client
has to check each of these versions during its primary key uniqueness
check during each update.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-12-29 04:04:41 Re: BUG #2866: cast varchar to decimal failure
Previous Message Theodore Petrosky 2006-12-28 13:26:24 Re: BUG #2867: FULL PATH name problem