| From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Migration Query |
| Date: | 2017-05-09 06:10:46 |
| Message-ID: | oermh0$1hr$1@blaine.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
PAWAN SHARMA schrieb am 08.05.2017 um 17:13:
> Does one any having list of bottlenecks and workarounds while migrating data
> from Oracle to Postgresql. like what are thing which we can migrate from Oracle database to Postgresql and what we can't?
One thing I have seen regularly is the wrong translation of Oracle's NUMBER data type to the corresponding Postgres type.
e.g. NUMBER(22) is very often translated to a numeric in Postgres but it should be translated to integer or bigint.
numeric is slightly slower and takes more space then integer or bigint.
You also need to think about how you used the DATE data type in Oracle.
If you rely on the time part, you have to translate that into a TIMESTMAP in Postgres.
Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Olarte | 2017-05-09 09:26:05 | Re: Python versus Other Languages using PostgreSQL |
| Previous Message | Venkata B Nagothi | 2017-05-09 05:17:07 | Re: Migration Query |