[thepumpkin1979]

I've been using CRDB 2.0 for a toy project for a few weeks now, today I notice 2.1 was available so I started playing with some of their new features, I ran a SQL query with correlated sub-queries and then the server crashed. It's the first time I see a crash, so I rushed to the GitHub report to report the bug and to my surprise a GitHub issue was already created for the crash[0], it included the stack trace and an anonymized version of my SQL query that caused the crash.

This really demonstrates they really care about the stability of their product, one more reason to keep recommending CockroachDB.

[0] https://github.com/cockroachdb/cockroach/issues/32048

[beefsack]

This is equal parts impressive and scary. It's awesome from a stability perspective, but I'm not completely comfortable with "dial home" functionality apparently being enabled by default in a database system.

[knz42]

It's printed "in bold letters on the label";

and like any sane db deployment you should firewall it off anyway.

[rishav_sharan]

If i remember it right, you can switch off the telemetry during installation

[tyingq]

Here's the details: https://www.cockroachlabs.com/docs/stable/diagnostics-report...

[StreamBright]

That is great but I would rather have software which does not crash than a team of very enthusiastic developers who are eager to fix bugs. One example of this would be FoundationDB or Riak. I never managed to crash Riak in a production environment, I haven't used FoundationDB in production to say the same but based on the method they use to build the software is just mind blowing and afaik verrry efficient.

[kierenj]

Well obviously, which is what they're striving to achieve by putting measures like this in place