David G. Johnston wrote:
> On Thu, Sep 24, 2015 at 12:15 PM, Ladislav Lenart wrote:
>> Suppose I have two (or more) concurrent DB transactions:
>> * Each runs in SERIALIZABLE.
>> * Each updates (insert / update / delete) different rows in the
>> same table.
>>
>> Can I get serializable failure
On Thu, Sep 24, 2015 at 12:15 PM, Ladislav Lenart
wrote:
> Hello.
>
> I would like to know how SERIALIZABLE behaves.
>
> Suppose I have two (or more) concurrent DB transactions:
> * Each runs in SERIALIZABLE.
> * Each updates (insert / update / delete) different rows in the same table.
>
> Can I
Hello.
I would like to know how SERIALIZABLE behaves.
Suppose I have two (or more) concurrent DB transactions:
* Each runs in SERIALIZABLE.
* Each updates (insert / update / delete) different rows in the same table.
Can I get serializable failures (i.e. ERROR: could not serialize access due to
r
