Re: WIP: to_char, support for EEEE format - Mailing list pgsql-hackers

From Tom Lane
Subject Re: WIP: to_char, support for EEEE format
Date
Msg-id 27841.1249264518@sss.pgh.pa.us
Whole thread Raw
In response to Re: WIP: to_char, support for EEEE format  (Euler Taveira de Oliveira <euler@timbira.com>)
Responses Re: WIP: to_char, support for EEEE format  (Brendan Jurd <direvus@gmail.com>)
Re: WIP: to_char, support for EEEE format  (Brendan Jurd <direvus@gmail.com>)
List pgsql-hackers
Euler Taveira de Oliveira <euler@timbira.com> writes:
> As I said in a prior e-mail, Oracle has a diferent overflow limit (-84 to 127).
> In PostgreSQL, the numeric datatype can have up to 1000 digits (ie 1e+999) and
> the double precision datatype can have up to 309 digits (ie 1e-307 or 1e+308).
> We should support up to 3 exponent digits so all of our native datatypes are
> covered by the to_char() function.

Uh, no, we had better support more.  The actual limit of the current
numeric format is 1e+131072.

As long as we consider that EEEE should emit as many exponent digits
as needed, this isn't particularly critical.  But it would be if we
try to specify an exact number of output digits.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: CommitFest Status Summary - 2009-08-03
Next
From: Brendan Jurd
Date:
Subject: Re: WIP: to_char, support for EEEE format