Seems to do the same thing as Citus. Is that accurate?
It seems pretty compelling.
There's at least 2 big caveats though:
1. Although they are very transparent about limitations / PG compatibility issues, you'll almost certainly run into things you weren't expecting (because some of the limitations are only documented as bugs in github issues, which you probably won't go through every single one of before you start). Examples:
a. No partial indexes (which can be a pain if you had a unique partial index, solution add a nullable column to the unique index) - but there's clearly work being done on this as we speak
b. Index isn't used with now() (solution, pass it as a parameter)
c. No way to tell if an upsert did an insert or update (like using xmax in postgres)
d. More obviously: no full text search or geo
2. Backup options for the community edition is limited (which I think is a generous way to describe it). If you're used to (free) Barman, even their enterprise backup capabilities are poor.
For any serious work, I'd recommend you not use the community edition until #2 improves.
1a) (as you noted) should be in the next release
1b) working on it, should be in the next release: https://github.com/cockroachdb/cockroach/pull/50320
1c) I filed https://github.com/cockroachdb/cockroach/issues/50418 to track. It seems plausible that we could fit in a story here with the work we're doing to expose MVCC timestamps to SQL.
1d) No plans on any sort of text search story but geo is underway (see https://github.com/cockroachdb/cockroach/issues?q=is%3Aissue...)
Curious to hear about your use of full text search in postgres.
Have you ever used pgtrgm? Would something like that or compatible with that be interesting to you? https://www.postgresql.org/docs/12/pgtrgm.html
For "even their enterprise backup capabilities are poor." are there specific things you have in mind?
Out of curiosity, what are your use cases? I'd expect before triggers are implemented, we'll make changefeeds more powerful and robustly supported.
Please!
