On Thu, Sep 24, 2015 at 12:15 PM, Ladislav Lenart <lenartlad@volny.cz> 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 get serializable failures (i.e. ERROR: could not serialize access due to read/write dependencies among transactions)?
This is on 9.4.
Thank you in advance,
Probably not but there seems to be insufficient information provided to prove this. You seem to probably have the "write dependency" covered but you mention nothing about "read dependencies".
Why not just assume it can and put code in place to handle that possibility - especially since you should probably be frameworking database access to enforce that all parts of the system use SERIALIZABLE?