A safe MySQL upgrade that wasn't so safe
el1s7
39 points
10 comments
August 29, 2026
Related Discussions
Found 5 related stories in 99.3ms across 9,386 title embeddings via pgvector HNSW
- Is your Postgres migration safe or not safe? vira28 · 122 pts · September 26, 2026 · 54% similar
- Rsync 3.5.0: a huge number of security fixes zdkaster · 13 pts · August 14, 2026 · 44% similar
- A flaky test exposed a Redis client use-after-free DrNemski · 38 pts · July 22, 2026 · 44% similar
- Backups Aren't Simple afilipovski · 170 pts · September 16, 2026 · 42% similar
- My Homelab Got Hacked – A Postmortem birdculture · 19 pts · August 13, 2026 · 42% similar
Discussion Highlights (3 comments)
Insimwytim
That's kinda fun (not in a fun way). Since the update is done semi-automatically by the means of AWS RDS, does AWS takes any responsibility for that? Unless this use case is warned against in migration notes, I would think they ought to.
krautburglar
Mixing binlog formats across replicas sounds like user error to me.
190n
I don't understand why this issue only appeared after the upgrade, not immediately after the migration to add the column?