The Top 10 Mistakes When Migrating Oracle Databases to PostgreSQL - Jim Mlodgenski

Many major organizations like Amazon have moved their fleets of Oracle database to #PostgreSQL, and many more are embarking on the change every day. As part of these #migrations, a distinct pattern of mistakes has emerged that lead to project delays, performance issues, and frustration.
Like👍 Comment💬 Share🔗 Subscribe✅ and tap the 🔔 to be the first to see new videos on #OpenSource #Databases & more! percona.tv/subscribe
These mistakes can be caused by the tools being used or just by not understanding how PostgreSQL is different than Oracle.
In this talk, we will discuss the top mistakes people generally make when moving to PostgreSQL from Oracle and what the correct course of action to take.
Get more on #PostgreSQL & #Database Tools + other Percona Database Talks below 👇👇👇
🎧 Watch / listen our PostgreSQL Database Podcasts ⏩ percona.tv/database-podcast
✅ Percona Operator for PostgreSQL ⏩per.co.na/kubernetes-operators
✅ Watch Percona Live 2021 Talks ⏩ percona.tv/PerconaLive2021
👨‍💻👩‍💻 PostgreSQL Jobs - Percona is Hiring ⏩ per.co.na/percona-jobs
✅PostgreSQL Support ⏩ per.co.na/postgresql-support
✅PostgreSQL info ⏩ per.co.na/postgresql-info
✅PostgreSQL events ⏩ per.co.na/pl2020
✅Percona Distribution for PostgreSQL ⏩ per.co.na/postgresql
✅Monitor your PostgreSQL For Free ⏩ percona.tv/pmm-yt
Follow Percona 👇👇👇
Twitter: per.co.na/twitter
Facebook: per.co.na/facebook
Instagram: per.co.na/instagram
LinkedIn: per.co.na/linkedin

[@afterthesmash]

Just finished the video. Absolutely first rate as far as it went.
I think perhaps Jim should have ended with an idealized game plan, summarizing all of this hard won knowledge as an abstract tactical roadmap.
I will never have any contact will Oracle at any level, but it helps enormously for me to understand what makes Postgres distinct within the database space.

[@afterthesmash]

When porting a system, it's often good to get the replacement running early, in any way, shape or form. Patching over the "dual" problem is a way to there sooner.
I think the point here is that patching "dual" gets you to a place where you can do more scouting.
At the same time, the real portability path should prioritize drilling into the superficial Oraclysms up front, to make this kind of thing unnecessary.

[@nmatheus]

this is very helpful und interesting, thanks for the video

[@alisaied4958]

So if text faster than varchar why have varchar??

[@elou87]

oracle to postgres