Rails Daily: Postgres and MySQL Schema Reliability
Database dump and load work dominates today's Rails activity, with Postgres extension fixes and MySQL structure load changes leading. A set of smaller correctness fixes for Server-Timing, Active Job logging, and associations rounds out the day.
Duration: PT2M12S
Episode overview
This episode is a short developer briefing from Rails Daily.
It explains recent repository work in plain language.
- Show: Rails Daily
- Published: 2026-09-23T06:03:19Z
- Audio duration: PT2M12S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, it's September 23rd, 2026, and this is Rails Daily.
The clear pattern today is database reliability, with four pull requests tightening how Rails dumps and loads schema on Postgres and MySQL.
On Postgres, two open proposals address extensions like PostGIS. PR 58856 would stop dumping extension-owned tables and enum types when the extension lives in a dumped schema, preventing load failures where Postgres refuses to drop and recreate those objects. The related PR 58855 ensures the extension's schema…
On MySQL, two merged changes modernize structure loading. PR 58828 removes the explicit foreign key checks toggles around the load, which date back to when Rails replayed tables statement by statement. PR 58829, building on that, pipes the structure file through standard input instead of using a source command,…
Elsewhere, merged fixes correct small but sharp bugs. PR 58800 fixes Server Timing double-counting when nested events share a name, where a parent duration already includes its children. PR 58850 fixes a no-method error when Active Job uses a broadcast logger for tagging. PR 58852 restores memoization for…
What's next is testing and review: if you run SQL-format…
Nearby episodes from Rails Daily
- Migration Compatibility Overhaul and Logging Fixes
- Weekly Recap - Active Record Correctness and Ractor Readiness
- Ruby 4 Compatibility and MySQL Schema Loads
- Test Isolation Fixes and Parser Compatibility
- Query Correctness Gets Serious Attention
- Correctness Fixes Across the Data Layer
- Cleaning Up Old Assumptions
- Quiet Data Leaks and Silent Config Bugs