Re: Storage: upsert vs. delete + insert

2014-09-10 Thread Michal Budzyn
his was true in version prior to 2.0, but it should still work this > way. But maybe someone will correct me, if i'm wrong. > Cheers, > Olek > > 2014-09-10 18:30 GMT+02:00 Michal Budzyn : > > One insert would be much better e.g. for performance and network latency. >

Re: Storage: upsert vs. delete + insert

2014-09-10 Thread Michal Budzyn
One insert would be much better e.g. for performance and network latency. I wanted to know if there is a significant difference (apart from additional commit log entry) in the used storage between these 2 use cases.

Storage: upsert vs. delete + insert

2014-09-10 Thread Michal Budzyn
Is there any serious difference in the used disk and memory storage between upsert and delete + insert ? e.g. 2 vs 2A + 2B. PK ((key), version, c1) 1. INSERT INTO A (key , version , c1, val) values (1, 1, 4711, “X1”) ... 2. INSERT INTO A (key , version , c1, val) values (1, 1, 4711, “X2”) Vs. 2A