4 ms·
And will not be supported for the foreseeable future due to the fact that PostgreSQL does row level multi version concurrency control.
by ants_a 13y ago
And will not be supported for the foreseeable future due to the fact that PostgreSQL does row level multi version concurrency control.
- rpedela 13y agoI proposed supporting JSON Patch which may or may not be implemented, but it does provide a way forward. http://www.postgresql.org/message-id/CACu89FSYikxdUj+J01BoAvoyieaGsXr1wSo1oQgGBMXsBNoMhg@mail.gmail.com http://www.postgresql.org/message-id/CACu89FSYikxdUj+J01BoAv...
- ants_a 13y agoI should have been more clear. What I meant was that in-place partial updates are not going to happen any time soon. This is mostly a performance issue, updating a value inside a JSON document will never be lightning fast because you need to copy the whole row and clean up the old version after the transaction has committed. JSON patch would avoid transfering the JSON document back and forth over the network, but the local copy will still need to happen.
- rpedela 13y agoTrue. I think reducing network overhead, removing one SQL call (currently need SELECT + UPDATE), and simplifying application code is a good start and probably fast enough for most use cases.