pgsql: Prevent integer overflow within the integer-datetimes version of - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Prevent integer overflow within the integer-datetimes version of
Date
Msg-id 20080123212620.96ACC754108@cvs.postgresql.org
Whole thread Raw
List 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)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Prevent integer overflow within the integer-datetimes version of
Next
From: eggyknap@pgfoundry.org (User Eggyknap)
Date:
Subject: pllolcode - pllolcode: Add some TODOs, improve messages for unsupported