4 ms·
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'
by mattashii 4y ago
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.
- rattray 4y ago"how will this handle major version upgrades" was one of my first/biggest questions when reading through the homepage fwiw
- nikita 4y agoMajor 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.
- rattray 4y agoSorry, 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.