2 ms·
I would keep an eye on the columnstore space. I know that Microsoft introduced read-only columnstore indices before introducing updateable ones, and their turna
by greggyb 12y ago
I would keep an eye on the columnstore space. I know that Microsoft introduced read-only columnstore indices before introducing updateable ones, and their turnaround on it was 2 years - SQL Server 2012 to 2014.
I'd use that as the outside end of an estimate for when the Postgres team will get updateable columnstore working.
- ddorian43 12y agoNote, updatetable columnstore sucks everywhere, so I don't think so. It's only for OLAP, not OLTP (parse is oltp). What may help @azinman is group-compression (ex: bigger pages of rows and compress the whole page, where each json-key can be repeated multiple times in a page since each page may have multiple rows). This is what happens on tokudb,hbse,hypertable,cassandra.