$ the-wire · showcase
Configurable maintenance database for Postgres, plus retention sizing guidance for solid_cable
By RepoJournal · Filed · About Rails · Composed from the cited sources · methodology
3 people shipped this
Rails' PostgreSQL adapter can now point db:create, db:drop, and db:purge at a database other than postgres, unblocking managed providers that don't offer it, while solid_cable documents what its default message retention actually costs at high broadcast rates.
Add maintenance_database option to the PostgreSQL adapter rails/rails
db:create, db:drop, and db:purge always connected to the postgres database, which DigitalOcean and other managed services do not provide (DigitalOcean exposes only defaultdb and rejects connections to template1 and template0 in pg_hba.conf). The new maintenance_database option sets which database those tasks connect to, mirroring createdb's --maintenance-db, and defaults to postgres so existing...
Add maintenance_database option to the PostgreSQL adapter rails/rails
The option landed in the adapter after the pull request from yahonda, credited to asmrtfm for the original idea behind the issue it fixes.
README: sizing guidance for message_retention (#95) rails/solid_cable
solid_cable's README now spells out that message_retention must cover the slowest subscriber's polling interval plus a margin for a reconnecting listener. The measured cost of the default: at 60 messages per second, 1.day holds roughly 5 million rows (about 3.5 GB on SQLite), against about 18,000 rows for 5.minutes, on solid_cable 4.0.0 and 4.1.0.
Remove orphaned legacy adapter test fixtures rails/rails
Two fixtures in activerecord/test/active_record/connection_adapters/ that nothing loads anymore were removed; they date from the 7.2 deprecation of the pre-7.2 adapter registration API and were orphaned when the lookup they served was deleted.
