Otto@programming.dev to Selfhosted@lemmy.worldEnglish · 1 month agoStop using MySQL in 2026, it is not true open sourceoptimizedbyotto.comexternal-linkmessage-square103linkfedilinkarrow-up1354arrow-down19cross-posted to: opensource@programming.devlobsters@lemmy.bestiver.setechnology@lemmy.world
arrow-up1345arrow-down1external-linkStop using MySQL in 2026, it is not true open sourceoptimizedbyotto.comOtto@programming.dev to Selfhosted@lemmy.worldEnglish · 1 month agomessage-square103linkfedilinkcross-posted to: opensource@programming.devlobsters@lemmy.bestiver.setechnology@lemmy.world
minus-squareTakioslinkfedilinkEnglisharrow-up8·1 month agoIf only the upgrade process wasn’t so annoying with postgres…
minus-squaremsage@programming.devlinkfedilinkEnglisharrow-up6·1 month agoWhat do you mean? Stop DB, run pg_upgrade, start it, win? Or set up logical replication into newer version, wait for sync, test use-cases, switch write? Where do you get better experience?
If only the upgrade process wasn’t so annoying with postgres…
What do you mean?
Stop DB, run pg_upgrade, start it, win?
Or set up logical replication into newer version, wait for sync, test use-cases, switch write?
Where do you get better experience?