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

From: Ravi Krishna <ravi_krishna(at)aol(dot)com>
To: sandeep(dot)lko(at)gmail(dot)com, adrian(dot)klaver(at)aklaver(dot)com
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Oracle Migration Approach (Open source vs Vendor Specific)
Date: 2019-05-08 20:42:15
Message-ID: 854619151.1770877.1557348135984@mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>@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.

As far as I know, vendor lock in applies only if you want to use Oracle features like PLSQL.
If I am not mistaken, EDB also supports community version of PG, no different than support from
Crunchy Data Solutions or 2nd Q. You have that option too if you don't want to be locked in.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Julie Nishimura 2019-05-08 21:01:18 Re: postgresql 9.4 restart
Previous Message Sandeep Saxena 2019-05-08 20:30:19 Re: Oracle Migration Approach (Open source vs Vendor Specific)