Otto@programming.dev to Selfhosted@lemmy.worldEnglish · 3 days agoStop using MySQL in 2026, it is not true open sourceoptimizedbyotto.comexternal-linkmessage-square102fedilinkarrow-up1352arrow-down19
arrow-up1343arrow-down1external-linkStop using MySQL in 2026, it is not true open sourceoptimizedbyotto.comOtto@programming.dev to Selfhosted@lemmy.worldEnglish · 3 days agomessage-square102fedilink
minus-squaredogs0n@sh.itjust.workslinkfedilinkEnglisharrow-up27·3 days agoPostgres or sqlite are the only ones I ever consider nowadays.
minus-squareTakios@discuss.tchncs.delinkfedilinkEnglisharrow-up7·3 days agoIf only the upgrade process wasn’t so annoying with postgres…
minus-squaremsage@programming.devlinkfedilinkEnglisharrow-up6·2 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?
minus-squareHawk@lemmynsfw.comlinkfedilinkEnglisharrow-up5·3 days 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.