pekaba
11-12-2008, 12:11 PM
I've had the same problem again and did some digging into Postgres. The problem looks like it's the same as one previous poster described:
2008-11-12 19:00:01 ERROR: duplicate key violates unique constraint "playerhandsflop_pkey"
2008-11-12 18:59:59 STATEMENT: EXECUTE PHCashKeyEXECUTE(5564487,426255,to_timestamp('10/26/2008 02:08:55','MM/DD/YYYY HH24:MI:SS'),1,194527,6,5,0,0,0,0,0,0,False,False, 3,0,0,0,0,0,0,0,0,0,False,F
EXECUTE PHCashMiscEXECUTE(426255,10555.00,4895.00,1,0,-1,False,-1,0,0,0,0,0,-1,-1,False,False,False,False,False,False,False,0,2);
EXECUTE PHCashKeyEXECUTE(5564487,426256,to_timestamp('10/26/2008 02:08:55','MM/DD/YYYY HH24:MI:SS'),1,77605,6,0,0,0,0,0,-25,0,False,False,3,0,0,0,0,0,0,0,0,0,False,False,F alse,False,-1,False,Fals
EXECUTE PHCashMiscEXECUTE(426256,3335.00,3335.00,2,5,-1,False,-1,0,0,25,0,0,-1,-1,False,False,False,False,False,False,False,0,2);
EXECUTE PVPExecute(77605,235317,5564487,-25 );
EXECUTE PHCashKeyEXECUTE(5564487,426257,to_timestamp('10/26/2008 02:08:55','MM/DD/YYYY HH24:MI:SS'),1,173461,6,1,0,0,0,0,-50,0,False,False,3,0,0,0,0,0,0,0,0,0,False,False,F alse,False,-1,False,Fal
EXECUTE PHCashMiscEXECUTE(426257,4895.00,4775.00,4,4,-1,False,-1,0,0,50,0,0,-1,-1,False,False,False,False,False,False,False,0,2);
EXECUTE PVPExecute(173461,235317,5564487,-50 );
EXECUTE PHCashKeyEXECUTE(5564487,426258,to_timestamp('10/26/2008 02:08:55','MM/DD/YYYY HH24:MI:SS'),1,204177,6,2,0,0,0,0,0,0,False,False, 0,0,0,0,0,0,0,0,0,0,False,False,False,False,-1,False,False
EXECUTE PHCashMiscEXECUTE(426258,12700,10555.00,6,3,-1,False,-1,0,0,0,0,0,-1,-1,False,False,False,False,False,False,False,0,0);
I snipped the statement (cut off at the right, it continues like this for about 1700 lines - actually one single line in the log, but I inserted line breaks), but there might be an indication to what the problem is: Are the consecutive INSERT statements which are obviously called by the SQL functions really reentrant? I've experienced the problems since I switched on a quad core system, which might explain why a possible race condition manifested since then.
Also, could we maybe test if it helps to split up the many many EXECUTE statements (~1700) into multiple PostgreSQL queries? Postgres might choke on a 250kB query payload...
Kind Regards,
pekaba
Powered by vBulletin® Version 4.2.3 Copyright © 2024 vBulletin Solutions, Inc. All rights reserved.