Oracle vs. PostgreSQL: First Glance
I've been on a project where we were forced to migrate the opposite direction: From PostgreSQL to Oracle, because the client was already paying for Oracle licenses and really, <i>really</i>, wanted us to use Oracle to justify the expense.<p>It was actually a pretty big setback.  We were using PostGIS to support spatial queries (a key requirement), and Oracle Spatial was just not at the same level (both in performance and features).  The development experience with Oracle was also awful.  The licensing for Oracle was highly granular, down to the feature level.  More than once I'd identify a feature that provided a solution to an issue through online research only to be prevented from using it due to the customer not having the requisite license for it.<p>And the support was useless.  Oracle was so complex (by design) we resorted to contacting support a couple of times - they would send out an "engineer" who could turn any technical troubleshooting session into a sales presentation for some Oracle product or feature that would "solve" whatever the issue was.<p>I will never work on a project involving Oracle again (barring obscene amounts of money to assuage my frustration, of course).