Re: Transaction Isolation level for ERP software - Mailing list pgsql-general

From Justin
Subject Re: Transaction Isolation level for ERP software
Date
Msg-id CALL-XeNJ0d+j+S=+14f5JBcwChQmKpMWGyLOPW8DqfmO48RN8g@mail.gmail.com
Whole thread
In response to Re: Transaction Isolation level for ERP software  (shammat@gmx.net)
List pgsql-general


On Thu, Jul 16, 2026 at 4:36 AM <shammat@gmx.net> wrote:
Laurenz Albe schrieb am 15.07.2026 um 23:20:
>>    4. Most business apps use REPEATABLE READ as an industry standard.
>
> I am surprised by that statement.
>
> My experience is that most developers of "business apps" aren't even aware that there
> are different transaction isolation levels.

I think, this viewpoint might be based on the fact that it's the default isolation level in MySQL/MariaDB
and due to their "marked share", it might be considered a an "industry standard" by a lot of people.


MariaDB  Repeatable Read implementation is NOT compliant to the SQL standard only recently has it gotten closer  hence the  serialization errors the original poster is  getting with the later versions of MariaDB

https://jepsen.io/analyses/mysql-8.0.34   very good article 

Many people believe they are operating in repeatable read when in reality the database is acting in really odd ways that no one would expect.

Why MySQL/
MariaDB chose repeatable read isolation as the default when every other database uses Read Committed by default.  I do not know  MySQL is the odd ball because all the other major databases  going back 20+ years use Read Committed.   


pgsql-general by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Windows installer not working
Next
From: Bilal Abdulkadir Muhammed
Date:
Subject: Question about monitoring PostgreSQL 10 streaming replication health