rafiss

3 ms·

1. 1.▲
   by rafiss 4y ago

   > The Licensor may make an Additional Use Grant, above, permitting limited production use. See the text of the Additional Use Grant for CockroachDB [1]: > Additional Use Grant: You may make use of the Licensed Work, provided that you
2. 2.▲
   by rafiss 6y ago

   We do have compatibility gaps -- some big, some small. But I would still call it compatible because it's definitely close enough to use a PostgreSQL driver with it in production. I would be curious to hear your opinion on which incompa
3. 3.▲
   by rafiss 6y ago

   There certainly are pain points. I don't work on this myself, but one of our other engineers wrote this blog post [0] that discusses the experience of running CockroachDB in k8s and why we chose to use it for our hosted cloud product.
4. 4.▲
   by rafiss 7y ago

   Our goal is to make switching over from PostgreSQL easy. For Ecto in particular, we have a tracking issue that shows the items in our backlog that would improve compatibility: https://github.com/cockroachdb/cockroach&#x
5. 5.▲
   by rafiss 7y ago

   Thanks! I do think that a columnar on-disk representation would likely help with large analytical queries. But I would imagine they would negatively affect performance of point transactions in an OLTP workload. Note that this vectorized eng
6. 6.▲
   How We Built a Vectorized SQL Engine(cockroachlabs.com)

   209 points by rafiss 7y ago|55 comments
7. 7.▲
   by rafiss 14y ago

   github: rafiss Thanks! This might help a lot for an idea that my friends and I are working on.