PostgreSQL: Jsonb has committed

Re:PostgreSQL: Jsonb has committed by rpedela on Monday March 24, 2014 @11:52AM (#7458898)

Partial updates of a single JSON document are not supported yet.

[ Parent | on HN ]

Re:PostgreSQL: Jsonb has committed by ants_a on Monday March 24, 2014 @08:44PM (#7462919)

And will not be supported for the foreseeable future due to the fact that PostgreSQL does row level multi version concurrency control.

[ Parent | on HN ]

Re:PostgreSQL: Jsonb has committed by rpedela on Monday March 24, 2014 @11:37PM (#7463673)

I 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+J01BoAv...

[ Parent | on HN ]

Re:PostgreSQL: Jsonb has committed by ants_a on Tuesday March 25, 2014 @08:17AM (#7465341)

I 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.

[ Parent | on HN ]

Re:PostgreSQL: Jsonb has committed by rpedela on Tuesday March 25, 2014 @11:28AM (#7466418)

True. 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.

[ Parent | on HN ]