pgsql: Prevent integer overflow within the integer-datetimes version of

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Prevent integer overflow within the integer-datetimes version of
Date: 2008-01-23 21:26:20
Message-ID: 20080123212620.96ACC754108@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Prevent integer overflow within the integer-datetimes version of
TimestampTzPlusMilliseconds. An integer argument of more than INT_MAX/1000
milliseconds (ie, about 35 minutes) would provoke a wrong result, resulting
in incorrect enforcement of statement_timestamp values larger than that.
Bug was introduced in my rewrite of 2006-06-20, which fixed some other
overflow risks, but missed this one :-( Per report from Elein.

Tags:
----
REL8_2_STABLE

Modified Files:
--------------
pgsql/src/include/utils:
timestamp.h (r1.64 -> r1.64.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/timestamp.h?r1=1.64&r2=1.64.2.1)

Browse pgsql-committers by date

  From Date Subject
Next Message User Eggyknap 2008-01-24 03:17:16 pllolcode - pllolcode: Add some TODOs, improve messages for unsupported
Previous Message Tom Lane 2008-01-23 21:26:13 pgsql: Prevent integer overflow within the integer-datetimes version of