| From: | Ravi Krishna <ravi_krishna(at)aol(dot)com> |
|---|---|
| To: | sandeep(dot)lko(at)gmail(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Oracle Migration Approach (Open source vs Vendor Specific) |
| Date: | 2019-05-08 15:55:15 |
| Message-ID: | 826746.1622354.1557330915304@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> EDB or Aurora to Open source Postgres assuming we dont use AWS services OR
> would you suggest to move to Community version from the start by taking support/consultancy
> from other companies like 2nd quadrant and etc?
EDB is mainly attractive to Oracle shops who want Oracle compatibility. In my previous work place
EDB turned out to be highly compatible with PLSQL, but performance was twice as slow. This was
ver 9.5 something. Also keep in kind EDB is not cheap. Once you are in EDB, you are in another
closed vendor and you are locked as long as you use PLSQL. Non EDB version of PG does not
support PLSQL.
>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 ...
pl/pgsql is no match to PLSQL in productivity. I am not a fan of Oracle RDBMS, but I
think PL/SQL is top notch. If you are already using bulk collect type of features, it won't
be easy to replicate it in PL/PGSQL.
That being said, PG offers other languages too, like Java, Python, Perl. You can try them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Schneider | 2019-05-08 16:54:59 | Re: PostgreSQL on Amazon RDS |
| Previous Message | Sandeep Saxena | 2019-05-08 15:39:15 | Oracle Migration Approach (Open source vs Vendor Specific) |