Actually I ran our schema against AWS Schema conversion tool ,and when i looked at converted code then i saw that for some stuff it was using other services of AWS which is only in AWS ,
So thats what i meant by not using AWS services and just keeping usage of Postgres and its extensions.
@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.
Thank you for reply , I have run schema against Ora2Pg too ,and results were encouraging again only issue was making sure all objects are valid and wont throw error
and typical data type issues of migration but ora2pg do generate really good report to guide newbies.
Regards,
Sandeep
On 5/8/19 8:39 AM, Sandeep Saxena wrote:
> Hi All,
>
> In our company we are looking to migrate oracle db to postgres , now
> since we dont have any expertise in Postgres in our organization so we
> are planning to go
> with AWS aurora or EDB postgres so that we have helping hand in
> migration(in dev and dba) while we get mature in postgres ... do you
> guys think after 1-2 years if required it will be easy to move from EDB
> or Aurora to Open source Postgres assuming we dont use AWS services OR
Not sure how you can use Aurora without AWS?
> would you suggest to move to Community version from the start by taking
> support/consultancy from other companies like 2nd quadrant and etc?
I would say move directly to the community version, save yourself a
second transition cycle. Sign up with one the Postgres support companies
and/or use these lists.
>
>
> All our developers are experienced in pl/sql so I assume it will be
> easier to learn PL/pgsql ,isnt that right? so far only things i dont
> like about PL/pgsql that validation of program units doesnt happen until
> you run it ... though i did find extension plpgsql_check to achieve that
> to some extent.
>
> Regards,
> Sandeep
--
Adrian Klaver
adrian.klaver@aklaver.com