Re: Insert behavior in transaction - Mailing list pgsql-general

From Tom Lane
Subject Re: Insert behavior in transaction
Date
Msg-id 17391.1119229734@sss.pgh.pa.us
Whole thread Raw
In response to Insert behavior in transaction  ("Andres" <andres1981@gawab.com>)
Responses Re: Insert behavior in transaction
List pgsql-general
"Andres" <andres1981@gawab.com> writes:
> I did this simple test and it fails too.

> BEGIN (first transaction)
> INSERT INTO mytable VALUES(1);

> On other client
> BEGIN (second transaction)
> INSERT INTO mytable VALUES(0);
> INSERT INTO mytable VALUES(1);

> and it freezes waiting for the first o commit or rollback

Not too surprising if the second insert would imply a unique-key
violation.  It has to wait to see if the first insertion of "1"
is going to commit or not.

            regards, tom lane

pgsql-general by date:

Previous
From: "Grant Morgan"
Date:
Subject: unicode and =
Next
From: Tom Lane
Date:
Subject: Re: unicode and =