Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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)

pgsql-committers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group