| Lists: | pgsql-novice |
|---|
| From: | Petri Röytiö <petri(dot)roytio1(at)luukku(dot)com> |
|---|---|
| To: | pgsql-novice(at)postgresql(dot)org |
| Subject: | ERROR: Too many updates/deletes within transaction (cmin |
| Date: | 2009-08-12 09:22:33 |
| Message-ID: | 1250068953179.petri.roytio1.28048.t-ztPLIr-Bt8n0MOn0xU6w@luukku.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-novice |
Hi.
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.
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_filled WHERE 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
| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Petri Röytiö <petri(dot)roytio1(at)luukku(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: ERROR: Too many updates/deletes within transaction (cmin |
| Date: | 2009-08-13 14:56:02 |
| Message-ID: | 7169.1250175362@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-novice |
=?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.
regards, tom lane
| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Petri Röytiö <petri(dot)roytio1(at)luukku(dot)com>, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: ERROR: Too many updates/deletes within transaction (cmin |
| Date: | 2009-08-13 19:11:12 |
| Message-ID: | 407d949e0908131211t1e815e76h20a4b1c1e272a7c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-novice |
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
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..