[jordanlewis]

Thanks for the great feedback latch! I'm a Director of Engineering supporting the SQL implementation at Cockroach Labs and couldn't resist responding to your comment as we're aware of some of these limitations and are working on lifting them.

- CockroachDB 22.2 will support `LANGUAGE SQL` user-defined functions when it is released in the next few weeks. Have a look at the documentation: https://www.cockroachlabs.com/docs/dev/user-defined-function... - Triggers and PL/pgSQL support are both on the roadmap. - Postgres-compatible full-text search (tsvector/tsquery) is in development and we hope to land a preview in CockroachDB 23.1 (expected in the Spring of 2023).

Extensions-wise, we typically add support for them as users ask. Which Extensions do you typically need for a specific project that CockroachDB doesn't support?

[latch]

There's none that I need, but I think it's worth pointing out to anyone who asks about CRDB. There are many available extensions for PostgreSQL, so if you happen to rely on one of them, you might need to think about how you'll do that with CockroachDB. Obviously the new-ish support for spatial data was one of the most obvious, but even in this case, if you rely heavily on Postgis, you'll need to make sure CockroachDB supports everything you need.

[Joel_Mckay]

We are interested in a db system that can run adjacent to a CephFS external BLOB store, and are analyzing CRDB for comparable features (specifically data snapshots to offline mirrors, and time-shifting state for forensic auditing).

Transparent tuple salted-hash (like ephemeral seed) signing would also be nice for detecting bit-rot on backups. ;)