Otto@programming.dev to Selfhosted@lemmy.worldEnglish · 15 days agoStop using MySQL in 2026, it is not true open sourceoptimizedbyotto.comexternal-linkmessage-square102linkfedilinkarrow-up1351arrow-down19cross-posted to: opensource@programming.devtechnology@lemmy.world
arrow-up1342arrow-down1external-linkStop using MySQL in 2026, it is not true open sourceoptimizedbyotto.comOtto@programming.dev to Selfhosted@lemmy.worldEnglish · 15 days agomessage-square102linkfedilinkcross-posted to: opensource@programming.devtechnology@lemmy.world
minus-squaredogs0n@sh.itjust.workslinkfedilinkEnglisharrow-up28·14 days agoPostgres or sqlite are the only ones I ever consider nowadays.
minus-squareTakios@discuss.tchncs.delinkfedilinkEnglisharrow-up8·14 days agoIf only the upgrade process wasn’t so annoying with postgres…
minus-squaremsage@programming.devlinkfedilinkEnglisharrow-up6·14 days 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?
Postgres or sqlite are the only ones I ever consider nowadays.
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?