PG JSON write operations are document level whereas with Mongodb it's field level.
Would you use a DB that only let you write an entire row instead of setting a single field? Race conditions galore. Be very careful choosing PG for JSON in production systems...
Nope. If two writes happen concurrently on different fields you'll lose one write, unless you lock. The storage layer just stores the data as a blob that gets overwritten every time, it doesn't support partial updates.
PG JSON write operations are document level whereas with Mongodb it's field level.
Would you use a DB that only let you write an entire row instead of setting a single field? Race conditions galore. Be very careful choosing PG for JSON in production systems...
on postgres I can update a field easily and atomically with transactions (or there is something I don't know about?), like (postgresql 14)[0]:
[0] https://stackoverflow.com/a/38045827
Nope. If two writes happen concurrently on different fields you'll lose one write, unless you lock. The storage layer just stores the data as a blob that gets overwritten every time, it doesn't support partial updates.