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

From Adrian Klaver
Subject Re: Transaction Isolation level for ERP software
Date
Msg-id cea64644-0291-45dc-8980-d79ac52ea575@aklaver.com
Whole thread
In response to Transaction Isolation level for ERP software  (Mihir Kandoi <kandoimihir@gmail.com>)
List pgsql-general
On 7/15/26 10:34 AM, Mihir Kandoi wrote:
> I work on an ERP software called ERPNext <https://github.com/frappe/ 
> erpnext>. Currently, we use MariaDB with |REPEATABLE READ| . We have 
> been working on adding Postgres support to it but we have reached a 
> roadblock.
> 
> Recently, we updated MariaDB on our cloud platform from 10.6 to 11.8. 
> After that, we received a barrage of support tickets from people 
> complaining of snapshot violation errors. Given the number of tickets 
> and the severity of an ERP software not functioning ideally, along with 
> constant nagging from enterprise customers, we temporarily disabled 
> snapshot isolation.

This article:

https://www.percona.com/blog/mariadbs-snapshot-isolation-a-fix-that-breaks-more-than-it-fixes/

seems to be a good explanation of what is actually happening, namely it 
is not actually a fix.

> 
> Now with Postgres and |REPEATABLE READ| , there is no option like 
> MariaDB to just turn off snapshot violation errors. We believe that once 
> Postgres support hits production, we will again face another set of 
> similar serialization errors.

Set up a Postgres test database and run your problematic queries against 
it and then you can go from 'believe' to know.




-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Christophe Pettus
Date:
Subject: Re: Transaction Isolation level for ERP software
Next
From: Justin
Date:
Subject: Re: Transaction Isolation level for ERP software