From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "John D(dot) Burger" <john(at)mitre(dot)org> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Reduce NUMERIC size by 2 bytes, reduce max length to 508 |
Date: | 2005-12-06 18:20:15 |
Message-ID: | 8796.1133893215@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-patches |
"John D. Burger" <john(at)mitre(dot)org> writes:
> Tom Lane wrote:
>> Hm ... between that, the possible crypto connection, and John's
>> personal testimony
> Just to be clear, this John has yet to use NUMERIC for any
> calculations, let alone in that range.
My mistake, got confused as to who had said what.
The point remains though: in discussing this proposed patch, we were
assuming that 10^508 would still be far beyond what people actually
needed. Even one or two reports from the list membership of actual
use of larger values casts a pretty big shadow on that assumption.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-12-06 18:27:49 | Re: Reduce NUMERIC size by 2 bytes, reduce max length to 508 |
Previous Message | Tom Lane | 2005-12-06 18:15:41 | Re: Should I fix something after disk full error |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-12-06 18:27:49 | Re: Reduce NUMERIC size by 2 bytes, reduce max length to 508 |
Previous Message | Andrew Dunstan | 2005-12-06 17:34:32 | more locale problems on Windows |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-12-06 18:27:49 | Re: Reduce NUMERIC size by 2 bytes, reduce max length to 508 |
Previous Message | Andrew Dunstan | 2005-12-06 15:42:53 | Re: [PATCHES] snprintf() argument reordering not working |