Thread: what could be blocking an insertion?

Hi,

A few days ago an insertion operation issued by a JDBC client that was
blocked by
postgreSQL. I could verify that by issuing the operation using psql. My
question is,
what could be causing this? There were other JDBC clients but they never
lock any
tables. They all used transactions with the serializable isolation level. A
day or so
later the problem was gone.

Any idea? I need to prevent it from happening again. Thanks!


-----
--
Kent Tong
Wicket tutorials freely available at http://www.agileskills2.org/EWDW
--
View this message in context: http://www.nabble.com/what-could-be-blocking-an-insertion--tf4749607.html#a13581279
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

> There were other JDBC clients but they never
> lock any tables. They all used transactions with the serializable isolation level.

If you have concurrent access and some isolation you have locking.
If two inserts/updates try to change the same data (even via
triggers/rules) you get a failed commit.

maybe tis helps