pgsql: Fix power_var_int() for large integer exponents. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Fix power_var_int() for large integer exponents.
Date
Msg-id E1XSHa1-00086V-1x@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix power_var_int() for large integer exponents.

The code for raising a NUMERIC value to an integer power wasn't very
careful about large powers.  It got an outright wrong answer for an
exponent of INT_MIN, due to failure to consider overflow of the Abs(exp)
operation; which is fixable by using an unsigned rather than signed
exponent value after that point.  Also, even though the number of
iterations of the power-computation loop is pretty limited, it's easy for
the repeated squarings to result in ridiculously enormous intermediate
values, which can take unreasonable amounts of time/memory to process,
or even overflow the internal "weight" field and so produce a wrong answer.
We can forestall misbehaviors of that sort by bailing out as soon as the
weight value exceeds what will fit in int16, since then the final answer
must overflow (if exp > 0) or underflow (if exp < 0) the packed numeric
format.

Per off-list report from Pavel Stehule.  Back-patch to all supported
branches.

Branch
------
REL9_2_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/228ed43708a048680d2bf45e744e90032b1efec1

Modified Files
--------------
src/backend/utils/adt/numeric.c       |   30 ++++++++++++++++++++++++++----
src/test/regress/expected/numeric.out |   19 +++++++++++++++++++
src/test/regress/sql/numeric.sql      |    9 +++++++++
3 files changed, 54 insertions(+), 4 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix power_var_int() for large integer exponents.
Next
From: Tom Lane
Date:
Subject: pgsql: Fix power_var_int() for large integer exponents.