On Tue, 9 Nov 2004, PostgreSQL Bugs List wrote:
>
> Bug reference: 1308
> Logged by: Simon Lesage-Tremblay
> Email address: [EMAIL PROTECTED]
>
> Description: Bug with JDBC driver on duplicate
>
> Details:
>
> My problem is when I insert a record that have a problem of duplicate key,
> my request fall in a frozing mode.
>
> I test my commands with pgadmin and I got a message of duplicate key. So I
> supposed that is a problem with the driver.
>
This is not a problem with the JDBC driver, but likely a problem of two
concurrent sessions issuing the same insert inside two separate
transactions. Consider:
Session 1:
CREATE TABLE t(a int primary key);
BEGIN;
INSERT INTO t(a) VALUES(1);
Session 2:
BEGIN;
INSERT INTO t(a) VALUES(1);
Since Session 1 has not committed or rolled back Session 2 cannot tell if
the insert is a duplicate key error or is valid, so it must wait for
Session 1 to do something first. This is likely the "frozing mode" you
are seeing as the insert waits.
Kris Jurka
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
