Compatible with MySQL or PostgreSQL is becoming a big deal. This is great for users but there will be confusion about the meaning of "compatible".
smalldatum.blogspot.com/2021/10/compat
Conversation
Replying to
I classify systems with pg compatibility based on code reuse. The extreme case is a pure extension - these "reuse" everything. Then you have Aurora, which can reuse existing geospatial + FTS index AM code. Cockroach/Yugabyte change storage at a higher level, making this hard.
Cockroach/Yugabyte do still reuse a lot of pg code that doesn't touch storage. Don't know where to place new Google spanner stuff just yet -- maybe it's kind of a clean room reimplementation of the parser. If so, that seems like another gradation in compatibility to me.
1
1
CockroachDB is reusing pg code? I thought it's pretty much written in Go?
1
1
Show replies
TimescaleDB would be considered a pure extension by this categorization I think? Interested if that's your perception too?
1
2
Replying to
Judging by reuse is easier in BSD-land. Team PG can choose reuse (because BSD) while Team MySQL usually must choose reimplement (because GPL).
1