On Thu, Aug 13, 2009 at 3:56 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> =?ISO-8859-1?Q?Petri_R=F6yti=F6?= <petri(dot)roytio1(at)luukku(dot)com> writes:
>> Every now and then I get following error message. It seems that it happens more or less randomly...I guess the reason is 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
In 126.96.36.199 and later, certain serializable transactions containing
function calls or TRUNCATE commands would fail with the error: ERROR:
Too many updates/deletes within transaction..
In response to
pgsql-novice by date
|Next:||From: P. Staring||Date: 2009-08-14 12:09:08|
|Subject: Having trouble installing on Vista|
|Previous:||From: Tom Lane||Date: 2009-08-13 16:43:49|
|Subject: Re: Calling stored function that returns a cursor from a libpq program |