Re: Oracle Migration Approach (Open source vs Vendor Specific)

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Oracle Migration Approach (Open source vs Vendor Specific)
Date: 2019-05-10 01:20:36
Message-ID: 20190510012036.vq75zleshuez2wwh@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, May 8, 2019 at 04:23:06PM -0500, Ron wrote:
> On 5/8/19 3:30 PM, Sandeep Saxena wrote:
> [snip]
> > @Ravi
> > My company is trying to avoid another vendor lockin too , thats why we
> > are bit skeptical on going to EDB as once we start using their Oracle
> > compatability
> > feature then it will be very difficult to move to community addition again.
>
> What about converting using EDB and then -- once the database is up, running
> and completely off of Oracle -- slowly converting to vanilla PG one "module"
> at at time?

I did blog posts about lockin and vendor selection strategy that might
help:

https://momjian.us/main/blogs/pgblog/2019.html#March_5_2019
https://momjian.us/main/blogs/pgblog/2019.html#March_7_2019

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2019-05-10 03:25:01 Re: Query on pg_stat_activity table got stuck
Previous Message neeraj kumar 2019-05-09 23:35:37 Re: Query on pg_stat_activity table got stuck