Tales from the Postgres Front, and What We Can Learn
summary
Migrations come mostly from Oracle and sequel server with a post‑2014 jump tied to Microsoft pricing and Hibernate often making migrations trivial, but the real problems are specific: misconfigured shared_buffers and work_mem misconfigured, pervasive bloat, and backup confusion. Health checks find 43% unable to do point in time recovery and many lack standby replicas; tuning changes are required in >70% of help cases, action concentrates on Linux (about 77% on Linux), and production outages are rare—less than one severity one a month.
AI-written summary · about
chapters (4)
related talks
46mThe Top 10 Mistakes When Migrating Oracle Databases to PostgreSQL
29mTales from the Field - Oracle to PostgreSQL migrations
42mPostgres: stories that will scare you
48mMigrating to PostgreSQL: Strategies, Sovereignty, and Success
30mPuny to Powerful PostgreSQL Rails Apps
06mMigration Consideration Oracle to PostgreSQL
51mHow Postgres is misused and abused in the wild
01h 09mReplacing Oracle Features in PostgreSQL: HA, Functions & Extensibility