From: | Tory M Blue <tmblue(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | bigint integers up to 19 digits. |
Date: | 2010-02-04 18:15:56 |
Message-ID: | 8a547c841002041015o57d533fdg7237c50dea7a9278@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Greetings,
I have a column that is a bigint that needs to store integers up to 19
digits long. For the most part this works but we sometimes have
numbers that are greater than 9223372036854775807.
I was thinking of changing this to a real or double precision field,
but read in the docs that the value stored is not always the value
inserted. From the docs " Inexact means that some values cannot be
converted exactly to the internal format and are stored as
approximations, so that storing and printing back out a value may show
slight discrepancies".
Is it known what level of precision is provided by the double data
type. My number will always be 19 digits long and always an integer.
I looked into the numeric data type, but the docs say that it can be slow.
Any feedback would be appreciated.
Thanks
Tory
From | Date | Subject | |
---|---|---|---|
Next Message | Craig James | 2010-02-04 18:43:09 | Re: bigint integers up to 19 digits. |
Previous Message | Matthew Wakeling | 2010-02-04 11:19:57 | Re: Optimizing Postgresql server and FreeBSD for heavy read and writes |