Otto@programming.dev to Selfhosted@lemmy.worldEnglish · 1 day agoStop using MySQL in 2026, it is not true open sourceoptimizedbyotto.comexternal-linkmessage-square100linkfedilinkarrow-up1316
arrow-up1316external-linkStop using MySQL in 2026, it is not true open sourceoptimizedbyotto.comOtto@programming.dev to Selfhosted@lemmy.worldEnglish · 1 day agomessage-square100linkfedilink
minus-squaredogs0n@sh.itjust.workslinkfedilinkEnglisharrow-up21·12 hours agoPostgres or sqlite are the only ones I ever consider nowadays.
minus-squareTakios@discuss.tchncs.delinkfedilinkEnglisharrow-up4·9 hours agoIf only the upgrade process wasn’t so annoying with postgres…
minus-squaremsage@programming.devlinkfedilinkEnglisharrow-up4·8 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·10 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.