Thread: ERROR: Too many updates/deletes within transaction (cmin
Hi. Every now and then I get following error message. It seems that it happens more or less randomly...I guess the reason isthat some transaction log is filled. How can I prevent this? [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) CONTEXT: SQL statement "CREATE TABLE profilointi.group_names AS SELECT group_id FROM profilointi.vtj_profilointi_results_filledWHERE group_id IS NOT NULL GROUP BY group_id" PL/pgSQL function "petri_profilointia_create_table" line 14 at SQL statement BR, Petri .................................................................... Luukku Plus -paketilla pääset eroon tila- ja turvallisuusongelmista. Hanki Luukku Plus ja helpotat elämääsi. http://www.mtv3.fi/luukku
=?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 reason
isthat 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.
regards, tom lane
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