6 ms·

What are the pros and cons of this compared to CockroachDB?

snthpy 11mo ago
Not the OP nor knowledgeable in this area but I would suspect / hope postgres compatibility as a start. The last time I looked into whether I could use cockroachdb as a backend for my Airflow cluster, it wasn't possible due to compatibility issues.
- pgedge_postgres 11mo ago
  You're actually 100% correct! CockroachDB is only 57.25% compatible with standard PostgreSQL (according to https://pgscorecard.com https://pgscorecard.com, which details the way it comes up with these numbers) whereas we are 100% compatible (and 100% open-source, whereas they are source-available).
znpy 11mo ago
License. CockroachDB moved to a license that I can’t even remember if it’s source-available anymore.
- pgedge_postgres 11mo ago
  It technically is source-available, as of Nov 2024, anyway: https://news.itsfoss.com/cockcroachdb-no-open-source/ https://news.itsfoss.com/cockcroachdb-no-open-source/ So yes, license (and compatibility - see https://pgscorecard.com https://pgscorecard.com) are two major differences between pgEdge and CockroachDB. pgEdge version updates also come in very close alignment with upstream PostgreSQL intentionally to make sure security patches/bugfixes and the latest features get to users ASAP.
traceroute66 11mo ago
> compared to CockroachDB CockroachDB != PostgreSQL. I take great issue with the way CockroachDB marketing seeks to imply compatability, when infact what they are promising is wire protocol compatability (i.e. you can fire up your copy of psql on the CLI and it will connect). Last time I looked, a great number of primitive, obvious, fundamental, low-hanging fruit were completely absent from CockroachDB, e.g. (IIRC) stored procedures are nowhere to be seen in CockroachDB.
- bonesmoses 11mo ago
  You can't even run pgbench unaltered on CockroachDB, as simple table structures and indexes are fundamentally different there. It is in no way a compatible product, and never has been.

snthpy 11mo ago

Not the OP nor knowledgeable in this area but I would suspect / hope postgres compatibility as a start. The last time I looked into whether I could use cockroachdb as a backend for my Airflow cluster, it wasn't possible due to compatibility issues.

pgedge_postgres 11mo ago
You're actually 100% correct! CockroachDB is only 57.25% compatible with standard PostgreSQL (according to https://pgscorecard.com https://pgscorecard.com, which details the way it comes up with these numbers) whereas we are 100% compatible (and 100% open-source, whereas they are source-available).

znpy 11mo ago

License. CockroachDB moved to a license that I can’t even remember if it’s source-available anymore.

pgedge_postgres 11mo ago
It technically is source-available, as of Nov 2024, anyway: https://news.itsfoss.com/cockcroachdb-no-open-source/ https://news.itsfoss.com/cockcroachdb-no-open-source/ So yes, license (and compatibility - see https://pgscorecard.com https://pgscorecard.com) are two major differences between pgEdge and CockroachDB. pgEdge version updates also come in very close alignment with upstream PostgreSQL intentionally to make sure security patches/bugfixes and the latest features get to users ASAP.

traceroute66 11mo ago

> compared to CockroachDB CockroachDB != PostgreSQL. I take great issue with the way CockroachDB marketing seeks to imply compatability, when infact what they are promising is wire protocol compatability (i.e. you can fire up your copy of psql on the CLI and it will connect). Last time I looked, a great number of primitive, obvious, fundamental, low-hanging fruit were completely absent from CockroachDB, e.g. (IIRC) stored procedures are nowhere to be seen in CockroachDB.

bonesmoses 11mo ago
You can't even run pgbench unaltered on CockroachDB, as simple table structures and indexes are fundamentally different there. It is in no way a compatible product, and never has been.