The Top 10 Mistakes When Migrating Oracle Databases to PostgreSQL
summary
Concrete pitfalls and fixes: a real migration case of 7,500 databases and 75 PB shows what actually breaks and why. Covers why the dual table workaround and Oracle table spaces mislead, how nulls and unique indexes differ, when bi‑directional failback becomes a second project, and why choosing numerics vs bigint alone can cost 20–40% slowdowns. Mentions practical tools (ora2pg, AWS DMS) and native Postgres types like inet that let teams delete thousands of lines of ported code.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:05Amazon Oracle Database Migration
- 3:19Why do people make these mistakes
- 4:22The dual table
- 5:58Table spaces
- 7:08Case folding
- 8:42Failback
- 12:44Synonyms
- 15:30Nulls
- 17:30Unique
- 21:00Indexing
- 27:10Native PostgreSQL Features
- 31:09Exceptions
- 35:12Data Types
- 41:17Conclusion
related talks
48mMigrating to PostgreSQL: Strategies, Sovereignty, and Success
06mMigration Consideration Oracle to PostgreSQL
29mTales from the Field - Oracle to PostgreSQL migrations
01h 09mReplacing Oracle Features in PostgreSQL: HA, Functions & Extensibility
36mTales from the Postgres Front, and What We Can Learn
45mSQL Server to PostgreSQL: Migration Challenges & Solutions
53mTop Development Mistakes When Working with PostgreSQL
35mThe PostgreSQL Twin Bill: The 7 Deadly PostgreSQL Mistakes & Review of What's New in PostgreSQL 14