| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Mihir Kandoi <kandoimihir(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Transaction Isolation level for ERP software |
| Date: | 2026-07-15 17:56:31 |
| Message-ID: | cea64644-0291-45dc-8980-d79ac52ea575@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shammat | 2026-07-15 18:04:59 | Re: Transaction Isolation level for ERP software |
| Previous Message | Christophe Pettus | 2026-07-15 17:52:57 | Re: Transaction Isolation level for ERP software |