From: | Serge Fonville <serge(dot)fonville(at)gmail(dot)com> |
---|---|
To: | Yaroslav <ladayaroslav(at)yandex(dot)ru> |
Cc: | postgresql novice <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: How do concurrent inserts work? |
Date: | 2014-12-27 12:15:46 |
Message-ID: | CAOAS_+KydYDVV=TAgw_jCF6+fonf3=2e4oC1D-M88EpH087=bQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
My Bad,
You don't have a BEGIN statement, so it's in autocommit.
Kind regards/met vriendelijke groet,
Serge Fonville
2014-12-27 13:05 GMT+01:00 Serge Fonville <serge(dot)fonville(at)gmail(dot)com>:
> When I tested the same queries I get the same behaviour.
> When both are SERIALIZABLE, the second insert just waits
>
> When one is default (unspecified) and the other is SERIALIZABLE, the
> behaviour is the same as you describe.
>
> Kind regards/met vriendelijke groet,
>
> Serge Fonville
>
> http://www.sergefonville.nl
>
> 2014-12-27 12:54 GMT+01:00 Yaroslav <ladayaroslav(at)yandex(dot)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.html
>> Sent from the PostgreSQL - novice mailing list archive at Nabble.com.
>>
>>
>> --
>> Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-novice
>>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Yaroslav | 2014-12-27 12:19:18 | Re: How do concurrent inserts work? |
Previous Message | Serge Fonville | 2014-12-27 12:05:26 | Re: How do concurrent inserts work? |