4 ms·
Actually the article you posted makes the case that postgres is not a good json database, because it can not modify json documents in place.
by ma2rten 11y ago
Actually the article you posted makes the case that postgres is not a good json database, because it can not modify json documents in place.
- neilc 11y agoPG 9.5 will improve this situation somewhat, e.g., builtin functions like jsonb_set(), and overloading the '-' operator for jsonb values: http://www.postgresql.org/docs/devel/static/functions-json.html http://www.postgresql.org/docs/devel/static/functions-json.h... That said, if you're doing a lot of mutation of large JSON documents stored in a single Postgres row value, the storage/concurrency control behavior still won't be ideal.
- valgog 11y agoActually if you really need to update large JSON documents efficiently, probably the only really efficient technology would be ToroDB http://www.8kdata.com/torodb/ http://www.8kdata.com/torodb/
- themartorana 11y agoI would love to hear more - this is the first I'm hearing of Toro - it never comes up in NoSQL talks or conversations. Any decent success stories?
- valgog 11y agoActually without providing some benchmark results, the statement, that PostgreSQL has performance problems because of on-copy updating of JSONB, is groundless.