Re: Write skew observed under serializable isolation - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: Write skew observed under serializable isolation
Date
Msg-id CAJ7c6TMCQmm-7akUPPE0GoAwYdeN5E==KU87=E8g9yjArVHXMQ@mail.gmail.com
Whole thread
In response to Re: Write skew observed under serializable isolation  (Zsolt Parragi <zsolt.parragi@percona.com>)
List pgsql-hackers
Hi Zsolt,

> That's a way to fix it, but I am not sure that it is the proper way to
> do it because it locks way more than needed.
>
> [...]

This looks like the same concern Matthias expressed above.

Let's be mindful of the fact that SIREAD locks despite the name are
not actually locks. Also our SERIALIZABLE implementation allows
false-positives by design [1].

Perhaps there is a smart way of minimizing false positives but
personally I don't instantly see them. Firstly we should fix the
broken feature and optimizations can be discussed as a separate patch.
Users concerned with rollbacks can always choose other isolation
levels.

[1]: https://arxiv.org/abs/1208.4179

-- 
Best regards,
Aleksander Alekseev



pgsql-hackers by date:

Previous
From: "Alberto Piai"
Date:
Subject: Re: Adding a stored generated column without long-lived locks
Next
From: Sehrope Sarkuni
Date:
Subject: Re: Speed up lpad() and rpad() for one-byte padding strings