4 ms·
One thing this article doesn't address (as far as I can see) is the efficiency of updates to a document in a key-value store in Postgres. If I'm using hstore/PL
by miketuritzin 15y ago
One thing this article doesn't address (as far as I can see) is the efficiency of updates to a document in a key-value store in Postgres. If I'm using hstore/PLV8/XML, how efficient is it to add to or update the document incrementally? (Say I am dealing with large, multi-megabyte documents.)
- saurik 15y agoPostgreSQL has multiversion concurrency, which means it will not do update-in-place (a strategy that makes concurrency very difficult); the result is that any part of an individual row, such as the entire hstore/xml field (but also including any other fields with types such as integer), cannot be "incrementally updated", and must be replaced (by which I mean, having a new one written and the old one effectively garbage collected at a later time) "whole hog".