From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Joanne Salerno - NOAA Federal <joanne(dot)salerno(at)noaa(dot)gov> |
Cc: | pgsql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgres 9.2.4 "Double Precision" Precision |
Date: | 2013-09-14 02:07:45 |
Message-ID: | 5233C4F1.7040000@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 09/13/2013 12:36 PM, Joanne Salerno - NOAA Federal wrote:
> Arian,
>
> It is a single database . Postgres was upgraded from 8.2.6 to 9.2.4...
> the database contents was not altered in upgrade, that is a 8.2.6 dump
> was not created then uploaded to 9.2.4.
>
> Perhaps handling of double precision, changed from 8.2.6 to 9.2.4 ?
To follow up, I don't think that is the case. By way of example, granted
on a 9.3 instance:
create table float_test (id int, f_fld double precision);
insert into float_test values (1, 6.31);
insert into float_test values (2, 6.32);
select * from float_test ;
id | f_fld
----+-------
1 | 6.31
2 | 6.32
(2 rows)
A couple of questions:
How is the data entered into the database?
Just wondering if there was any client side changes along with the
database change?
>
> Joanne
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Ray Stell | 2013-09-14 02:48:11 | Re: Hot standby & SR - log shipping required? |
Previous Message | Chris Travers | 2013-09-14 00:52:26 | Re: Best way to populate nested composite type from JSON` |