BUG #1193: Some query sequences do not finish - Mailing list pgsql-bugs

From PostgreSQL Bugs List
Subject BUG #1193: Some query sequences do not finish
Date
Msg-id 20040714133855.7B600CF4A10@www.postgresql.com
Whole thread Raw
List pgsql-bugs
The following bug has been logged online:

Bug reference:      1193
Logged by:          Stefan Sassenberg

Email address:      stefan.sassenberg@gmx.de

PostgreSQL version: 7.4

Operating system:   Linux

Description:        Some query sequences do not finish

Details:

Hello,

this happens on a database 7.4.3: I have a sequence of 5 commands that I
execute from my Java program. The last of them does never return, so the
program locks. I verified this behaviour with my pgAdmin III 1.0.2 (Linux)
with the same result, the execution time counter runs endlessly, or until I
stop the execution. I had this behaviour with different sequences of
commands, all of them like one "DELETE" command and several "INSERT"
commands. An example:

DELETE FROM EM_ROSTER_1 WHERE ID_COSTCENTER = 525313 AND ID_TOUR = 1049601
AND STARTING_DATE = '2004-8-9';
INSERT INTO EM_ROSTER_1 (COMMENT, ID_COSTCENTER, ID_EMPLOYEE,
ID_OPERATIONAL_0, ID_OPERATIONAL_1, ID_OPERATIONAL_2, ID_OPERATIONAL_3,
ID_OPERATIONAL_4, ID_OPERATIONAL_5, ID_OPERATIONAL_6, ID_TOUR,
PLANNED_FROM_0, PLANNED_FROM_1, PLANNED_FROM_2, PLANNED_FROM_3,
PLANNED_FROM_4, PLANNED_FROM_5, PLANNED_FROM_6, PLANNED_TILL_0,
PLANNED_TILL_1, PLANNED_TILL_2, PLANNED_TILL_3, PLANNED_TILL_4,
PLANNED_TILL_5, PLANNED_TILL_6, STARTING_DATE) VALUES (NULL, 525313,
260310029, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 1049601, '17:00:00',
'19:00:00', '21:00:00', '23:00:00', '01:00:00', '03:00:00', '02:00:00',
'18:00:00', '20:00:00', '22:00:00', '00:00:00', '02:00:00', '04:00:00',
'03:00:00', '2004-8-9');
INSERT INTO EM_ROSTER_1 (COMMENT, ID_COSTCENTER, ID_EMPLOYEE,
ID_OPERATIONAL_0, ID_OPERATIONAL_1, ID_OPERATIONAL_2, ID_OPERATIONAL_3,
ID_OPERATIONAL_4, ID_OPERATIONAL_5, ID_OPERATIONAL_6, ID_TOUR,
PLANNED_FROM_0, PLANNED_FROM_1, PLANNED_FROM_2, PLANNED_FROM_3,
PLANNED_FROM_4, PLANNED_FROM_5, PLANNED_FROM_6, PLANNED_TILL_0,
PLANNED_TILL_1, PLANNED_TILL_2, PLANNED_TILL_3, PLANNED_TILL_4,
PLANNED_TILL_5, PLANNED_TILL_6, STARTING_DATE) VALUES (NULL, 525313,
45876225, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 1049601, NULL, NULL,
NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL,
'2004-8-9');
INSERT INTO EM_ROSTER_1 (COMMENT, ID_COSTCENTER, ID_EMPLOYEE,
ID_OPERATIONAL_0, ID_OPERATIONAL_1, ID_OPERATIONAL_2, ID_OPERATIONAL_3,
ID_OPERATIONAL_4, ID_OPERATIONAL_5, ID_OPERATIONAL_6, ID_TOUR,
PLANNED_FROM_0, PLANNED_FROM_1, PLANNED_FROM_2, PLANNED_FROM_3,
PLANNED_FROM_4, PLANNED_FROM_5, PLANNED_FROM_6, PLANNED_TILL_0,
PLANNED_TILL_1, PLANNED_TILL_2, PLANNED_TILL_3, PLANNED_TILL_4,
PLANNED_TILL_5, PLANNED_TILL_6, STARTING_DATE) VALUES (NULL, 525313,
49808385, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 1049601, NULL, NULL,
NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL,
'2004-8-9');
INSERT INTO EM_ROSTER_1 (COMMENT, ID_COSTCENTER, ID_EMPLOYEE,
ID_OPERATIONAL_0, ID_OPERATIONAL_1, ID_OPERATIONAL_2, ID_OPERATIONAL_3,
ID_OPERATIONAL_4, ID_OPERATIONAL_5, ID_OPERATIONAL_6, ID_TOUR,
PLANNED_FROM_0, PLANNED_FROM_1, PLANNED_FROM_2, PLANNED_FROM_3,
PLANNED_FROM_4, PLANNED_FROM_5, PLANNED_FROM_6, PLANNED_TILL_0,
PLANNED_TILL_1, PLANNED_TILL_2, PLANNED_TILL_3, PLANNED_TILL_4,
PLANNED_TILL_5, PLANNED_TILL_6, STARTING_DATE) VALUES (NULL, 525313,
58983425, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 1049601, NULL, NULL,
NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL,
'2004-8-9');

Best regards,

Stefan

pgsql-bugs by date:

Previous
From: "PostgreSQL Bugs List"
Date:
Subject: BUG #1192: JDBC driver: org.postgresql.jdbc2.Array throws Bad BigDecimal Exception
Next
From: Bruce Momjian
Date:
Subject: SELECT DISTINCT on boxes