| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
| Cc: | Brendan Jurd <direvus(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: to_char, support for EEEE format |
| Date: | 2009-08-03 01:55:18 |
| Message-ID: | 27841.1249264518@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Euler Taveira de Oliveira <euler(at)timbira(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brendan Jurd | 2009-08-03 02:10:07 | Re: WIP: to_char, support for EEEE format |
| Previous Message | Tom Lane | 2009-08-03 01:49:45 | Re: CommitFest Status Summary - 2009-08-03 |