Re: double precision to numeric overflow error - Mailing list pgsql-general

From Thomas O'Connell
Subject Re: double precision to numeric overflow error
Date
Msg-id tfo-EC7463.21010907012003@news.hub.org
Whole thread Raw
In response to Re: [SQL] double precision to numeric overflow error  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
Responses Re: double precision to numeric overflow error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Indeed, it seems as though my inability to count digits was the real
problem. Still, does this not strike anyone as a somewhat abstruse error
message?

-tfo

In article <20030107152951.R67168-100000@megazone23.bigpanda.com>,
 sszabo@megazone23.bigpanda.com (Stephan Szabo) wrote:

> On Tue, 7 Jan 2003, Thomas O'Connell wrote:
>
> > is this expected behavior? if so, then why?
>
> I'd guess so if the timestamp value's integer part is
> 10 digits long since I believe trying to fit that into
> a numeric(15,6) wouldn't work (9 digits . 6 digits).
>
> > db=# create table foo( col timestamp );
> > db=# select cast( extract( epoch from col ) as numeric( 15, 6 ) ) from
> > foo;
> >  date_part
> > -----------
> > (0 rows)
> > db=# insert into foo values( current_timestamp );
> > INSERT 1705954 1
> > db=# select cast( extract( epoch from col ) as numeric( 15, 6 ) ) from
> > foo;
> > ERROR:  overflow on numeric ABS(value) >= 10^9 for field with precision
> > 15 scale 6

pgsql-general by date:

Previous
From: davoid@softhome.net
Date:
Subject: PostgreSQL + Visual Basic .NET
Next
From: Joseph Shraibman
Date:
Subject: shared buffers in config