From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Charlin Barak <charlinbarak(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Oracle number to PostgreSQL |
Date: | 2019-05-01 13:25:18 |
Message-ID: | 20190501132518.GC6197@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Greetings,
* Charlin Barak (charlinbarak(at)gmail(dot)com) wrote:
> When migrating from Oracle number(10,3) to PostgreSQL, is numeric(10,3)
> ideal or should I consider some other data types?
This really depends on what data is actually in that field and if you
need it to be exact.
If the field actually contains integers and always will, then using an
integer type field is *much* more efficient, either 'integer' if the
values will always be less than 2B, or 'bigint' if it'll be larger.
If the field actually contains floating point and can be inexact, then
using 'real' or 'float8' will be more efficient than numeric.
If the field needs to be exact (eg: monetary fields), then using
numeric(10,3) is correct.
I strongly recommend considering the data that goes into the field when
making this decision- there really is no 'one size fits all' when going
from number to numeric.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Charlin Barak | 2019-05-01 14:31:58 | Re: Oracle number to PostgreSQL |
Previous Message | Charlin Barak | 2019-05-01 13:01:40 | Oracle number to PostgreSQL |