[QGIS-Developer] Potential data loss issue with PostgreSQL JSONB and buffered transactions

Lauri Kajan lauri.kajan at gmail.com
Wed Jun 17 00:47:43 PDT 2026


Hi everyone,

First of all, thank you for all the time and effort you put into QGIS.

I opened an issue about a month ago and I know there is a lot on everyone's
plate, but I wanted to highlight it here since it involves silent data loss.

Basically, when saving two or more new features to a geometryless
PostgreSQL layer at the same time using buffered transactions, JSONB fields
are not saved at all. They just end up as NULL in the database. If you save
one feature at a time, it works perfectly.

Could someone take a quick look and let me know if you can reproduce this?
I want to make sure this is actually a bug in QGIS and not just some
specific issue on my end.

I included a short Python snippet in the bug report that makes it easy to
test. You can find the full details here:
https://github.com/qgis/QGIS/issues/65323


Thanks for your time!

Best,
Lauri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20260617/9bc52818/attachment.htm>


More information about the QGIS-Developer mailing list