Are they going to stay up-to-date with the latest version of Postgres? One problem with Yugabyte, TimescaleDB, Aurora etc. is that they are stuck on older versions of Postgres, which makes it feel like an entirely different product after a few years.
TimescaleDB, because it is packaged as a PostgreSQL extension (and not a fork, unlike the others), stays compatible with mainline PostgreSQL, especially as PostgreSQL improves. This is one of the key advantages of our approach.
We are planning on supporting the latest stable version of PostgreSQL. Right now, we're a bit behind (we're at 14.1, latest PosgreSQL is 14.3) but that shouldn't be much of an issue.
We don't yet know how we're going to do major version migrations, as the product is still not even out of private beta.
Major versions don't come out suddenly. We have time to test and make sure they work well with our storage.
Customers don't always want to upgrade to new version when old versions just work. However this can lead to version creep. Ideally we want to always run the latest version of Postgres. We will hold this line as long as possible.
Sorry, I meant less "how long until they catch up to trunk" and more "what is the downtime / operational burden of performing major upgrades like".
With separate storage and compute it seems tantalizingly possible to have low-effort zero downtime upgrades for the user, which would be a huge selling point.
