Re: ERROR: Too many updates/deletes within transaction (cmin - Mailing list pgsql-novice

From Greg Stark
Subject Re: ERROR: Too many updates/deletes within transaction (cmin
Date
Msg-id 407d949e0908131211t1e815e76h20a4b1c1e272a7c@mail.gmail.com
Whole thread Raw
In response to Re: ERROR: Too many updates/deletes within transaction (cmin  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-novice
On Thu, Aug 13, 2009 at 3:56 PM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
> =?ISO-8859-1?Q?Petri_R=F6yti=F6?= <petri.roytio1@luukku.com> writes:
>> Every now and then I get following error message. It seems that it happens more or less randomly...I guess the
reasonis that some transaction log is filled. 
>
>> [Err] ERROR:  Too many updates/deletes within transaction (cmin). Reader gang not able to provide correct visibility
1/1(combocid.c:275)  (seg6 slice1 xback2-3:50003 pid=28899) 
>
> [ blink... ]  There is no such error message anywhere in the Postgres
> sources.  I suppose you are running somebody's heavily-modified version.
> You had better take this up with that somebody.

Google tells me this was in Greenplum's 3.2 release notes:

Resolved Issues in 3.2 -

3164 Too many updates/deletes within transaction error in serializable
transactions

In 3.1.1.4 and later, certain serializable transactions containing
function calls or TRUNCATE commands would fail with the error: ERROR:
Too many updates/deletes within transaction..

--
greg
http://mit.edu/~gsstark/resume.pdf

pgsql-novice by date:

Previous
From: Tom Lane
Date:
Subject: Re: Calling stored function that returns a cursor from a libpq program
Next
From: "P. Staring"
Date:
Subject: Having trouble installing on Vista