From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: WIP: Relaxing the constraints on numeric scale |
Date: | 2021-07-03 10:14:37 |
Message-ID: | CAEZATCWYwOj6fUqdyXrbRLt+9bsyUzVSeMUB+awPmWhxmk6tog@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Attached is a more complete patch, with updated docs and tests.
I chose to allow the scale to be in the range -1000 to 1000, which, to
some extent, is quite arbitrary. The upper limit of 1000 makes sense,
because nearly all numeric computations (other than multiply, add and
subtract) have that as their upper scale limit (that's the maximum
display scale). It also has to be at least 1000 for SQL compliance,
since the precision can be up to 1000.
The lower limit, on the other hand, really is quite arbitrary. -1000
is a nice round number, giving it a certain symmetry, and is almost
certainly sufficient for any realistic use case (-1000 means numbers
are rounded to the nearest multiple of 10^1000).
Also, keeping some spare bits in the typemod might come in handy one
day for something else (e.g., rounding mode choice).
Regards,
Dean
Attachment | Content-Type | Size |
---|---|---|
numeric-scale-v2.patch | text/x-patch | 15.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Yura Sokolov | 2021-07-03 10:20:52 | Re: rand48 replacement |
Previous Message | Andrey Borodin | 2021-07-03 09:06:24 | Re: Synchronous commit behavior during network outage |