(Again) Column Store on PostGreSQL - Mailing list pgsql-general

From Simon AUBERT
Subject (Again) Column Store on PostGreSQL
Date
Msg-id CANOsmnDz-hm-45f5XUeprXpU4nNEvdBGwBUU0TtuBOJkxH448w@mail.gmail.com
Whole thread Raw
Responses Re: (Again) Column Store on PostGreSQL
Re: (Again) Column Store on PostGreSQL
List pgsql-general
Hello,

We can find this very informative blog post :
https://blog.2ndquadrant.com/column-store-plans/

I must say the approach with the "orientation" option is a genius idea.

I won't discuss much the advantages of COS, I had three years using Vertica -I loved it-, some tests of Monetdb, and recently Column Store Index on MSQL Server etc. And I'm pretty sure everybody is convinced this works great for Instant Analytics with products such as Tableau or Spotfire.. and much better than, saying, Hive. MonetDb is not so much enterprise ready (not even paid support available), CH is young while PGSQL has proven its high value in Transactionnal DB, the only thing missing for even a bigger deployment is this feature.

From what I understand, there is a team at 2ndquadrant.com that works on it (but I'm not sure it's still in the dev pipe).

My questions :
-do you develop from scratch or do you plan to use some code of MonetDb/Clickhouse/C_Store_fdw for that?  I don't know if even a collaboration between teams is feasible (I may be very naive but that would kick ass ^^)
.
-is it still in the pipe? do you have an idea of the workload or even ETA?

-I'm not a developer myself but I would be interested in testing, benchmarking, etc.. how to get involved?

Best regards,

--
Simon AUBERT
aubert.simon@gmail.com
+33 (0)6 66 28 52 04

pgsql-general by date:

Previous
From: Mark Jeffcoat
Date:
Subject: Showing table comments with psql
Next
From: Tom Lane
Date:
Subject: Re: Potentially undocumented behaviour change in Postgres 11 concerning OLD record in an after insert trigger