Otto@programming.dev to Selfhosted@lemmy.worldEnglish · 1 day agoStop using MySQL in 2026, it is not true open sourceoptimizedbyotto.comexternal-linkmessage-square100fedilinkarrow-up1323arrow-down110
arrow-up1313arrow-down1external-linkStop using MySQL in 2026, it is not true open sourceoptimizedbyotto.comOtto@programming.dev to Selfhosted@lemmy.worldEnglish · 1 day agomessage-square100fedilink
minus-squaredogs0n@sh.itjust.workslinkfedilinkEnglisharrow-up22·17 hours agoPostgres or sqlite are the only ones I ever consider nowadays.
minus-squareTakios@discuss.tchncs.delinkfedilinkEnglisharrow-up5·15 hours agoIf only the upgrade process wasn’t so annoying with postgres…
minus-squaremsage@programming.devlinkfedilinkEnglisharrow-up4·14 hours 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?
minus-squareHawk@lemmynsfw.comlinkfedilinkEnglisharrow-up4·15 hours agoSee also duckdb and clickhouse for OLAP of course.
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?
See also duckdb and clickhouse for OLAP of course.