Otto@programming.dev to Selfhosted@lemmy.worldEnglish · 2 months agoStop using MySQL in 2026, it is not true open sourceoptimizedbyotto.comexternal-linkmessage-square102fedilinkarrow-up1352arrow-down19cross-posted to: technology@lemmy.world
arrow-up1343arrow-down1external-linkStop using MySQL in 2026, it is not true open sourceoptimizedbyotto.comOtto@programming.dev to Selfhosted@lemmy.worldEnglish · 2 months agomessage-square102fedilinkcross-posted to: technology@lemmy.world
minus-squareherseycokguzelolacak@lemmy.mllinkfedilinkEnglisharrow-up53·2 months agoDidn’t Postgresql effectively win the database wars? Why use anything else?
minus-squaredogs0n@sh.itjust.workslinkfedilinkEnglisharrow-up28arrow-down1·2 months agoPostgres or sqlite are the only ones I ever consider nowadays.
minus-squareTakios@discuss.tchncs.delinkfedilinkEnglisharrow-up8·2 months agoIf only the upgrade process wasn’t so annoying with postgres…
minus-squaremsage@programming.devlinkfedilinkEnglisharrow-up6·2 months 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?
Didn’t Postgresql effectively win the database wars? Why use anything else?
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?