When I tested the same queries I get the same behaviour.When both are SERIALIZABLE, the second insert just waitsWhen one is default (unspecified) and the other is SERIALIZABLE, the behaviour is the same as you describe.Kind regards/met vriendelijke groet,Serge Fonvillehttp://www.sergefonville.nl2014-12-27 12:54 GMT+01:00 Yaroslav <ladayaroslav@yandex.ru>:Serge Fonville wrote> Perhaps because your second session doesn't specify an isolation level?No. ;) It's the same with any isolation level of the second session. ----- WBR, Yaroslav Schekin. --View this message in context: http://postgresql.nabble.com/How-do-concurrent-inserts-work-tp5832157p5832160.htmlSent from the PostgreSQL - novice mailing list archive at Nabble.com. -- Sent via pgsql-novice mailing list (pgsql-novice@postgresql.org) To make changes to your subscription:http://www.postgresql.org/mailpref/pgsql-novice
Serge Fonville wrote> Perhaps because your second session doesn't specify an isolation level?No. ;) It's the same with any isolation level of the second session. ----- WBR, Yaroslav Schekin. --View this message in context: http://postgresql.nabble.com/How-do-concurrent-inserts-work-tp5832157p5832160.htmlSent from the PostgreSQL - novice mailing list archive at Nabble.com. -- Sent via pgsql-novice mailing list (pgsql-novice@postgresql.org) To make changes to your subscription:http://www.postgresql.org/mailpref/pgsql-novice
pgsql-novice by date:
Соглашаюсь с условиями обработки персональных данных
