Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id D7784475E8A; Tue, 7 Jan 2003 18:12:06 -0500 (EST) Received: from news.hub.org (news.hub.org [64.49.215.80]) by postgresql.org (Postfix) with ESMTP id 4F7A4475D39; Tue, 7 Jan 2003 18:12:06 -0500 (EST) Received: by news.hub.org (Postfix, from userid 8) id 33ACC43A941; Tue, 7 Jan 2003 18:12:06 -0500 (EST) From: Thomas O'Connell X-Newsgroups: comp.databases.postgresql.sql, , comp.databases.postgresql.general Subject: double precision to numeric overflow error Date: Tue, 07 Jan 2003 17:12:08 -0600 Organization: Monster Labs, Inc. Lines: 16 Message-ID: X-Complaints-To: usenet@news.hub.org User-Agent: MT-NewsWatcher/3.3b1 (PPC Mac OS X) To: pgsql-general@postgresql.org, pgsql-sql@postgresql.org X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/263 X-Sequence-Number: 35384 is this expected behavior? if so, then why? -tfo 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