Is there an alternative for MySQL? We want to upgrade from 5.7 to 8 pretty soon, so it would be nice to have the appropriate toolkit.
MySQL is easy. You just open the database with the new version and the upgrade happens automatically.
Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
41–50 of 63 posts
Re: Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
#42 Requirements
...
Ruby 2.7 and later
Re: Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
#43There is also a new (OpenSource) Postgres extension that claims to provide multi-master replication based on logical replication, BDR and pglogical https://pgedge.github.io/spock/ which can also be used for online upgrades. It however only supports Postgres 15 and (not yet released) 16
Cool, that's good info. Hadn't come across it before. :)
The GitHub repo page for it is here, for anyone else interested in taking a look: https://github.com/pgEdge/spock
Re: Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
#44Is there an alternative for MySQL? We want to upgrade from 5.7 to 8 pretty soon, so it would be nice to have the appropriate toolkit.
MySQL is easy. You just open the database with the new version and the upgrade happens automatically.
When you do this, does it need to process the whole database before the server can start processing transactions, or is it more of a "upgrade in the background on the fly" kind of thing?
Re: Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
#45Have done minimal downtime major version upgrades using standard replication, switching between two "master" servers. In the five minute range.
Have you done this postgresql/RDS?
Because when I last tried it, the replica has to be the same major version (WAL streaming requires it) and then upgrading it to the latest version can take 10+ hours.
Definitely nowhere near 5 minutes downtime.
Re: Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
#46Have done minimal downtime major version upgrades using standard replication, switching between two "master" servers. In the five minute range.
Have you done this postgresql/RDS? Because when I last tried it, the replica has to be the same major version (WAL streaming requires it) and then upgrading it to the latest version can take 10+ hours. Definitely nowhere near 5 minutes downtime.
Self hosted postgres, not RDS.
Re: Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
#47Requirements ... Ruby 2.7 and later Damn. This looked interesting right up until the Ruby requirement. :(
I would prefer if it were written in Rust or Python. But this tool is very useful BTW.
Re: Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
#48Requirements ... Ruby 2.7 and later Damn. This looked interesting right up until the Ruby requirement. :(
How is this valid criticism? This is an excellent use of a scripting language.
Re: Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
#49Requirements ... Ruby 2.7 and later Damn. This looked interesting right up until the Ruby requirement. :(
What do you want them to use? Node.js?
Re: Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
#50Requirements ... Ruby 2.7 and later Damn. This looked interesting right up until the Ruby requirement. :(
What do you want them to use? Node.js?
Almost anything other than Ruby. Bad previous experiences with it have completely turned me off the entire ecosystem.
If it was "Ruby or Node.js" though, I'd just pick neither. ;)