1berry/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix overflow for INTERVAL 'x ms' where x is more than a couple million,

Browse Source 
and integer datetimes are in use.  Per bug report from Hubert Depesz
Lubaczewski.

Alex Hunsaker
This commit is contained in:
Tom Lane 2009-08-18 21:23:58 +00:00
parent c5b758bcb9
commit 2e78dc85e0
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/backend/utils/adt/datetime.c
View File

@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
* $Header: /cvsroot/pgsql/src/backend/utils/adt/datetime.c,v 1.118.2.12 2009/05/01 19:29:42 tgl Exp $
* $Header: /cvsroot/pgsql/src/backend/utils/adt/datetime.c,v 1.118.2.13 2009/08/18 21:23:58 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@ -3093,6 +3093,9 @@ DecodeInterval(char **field, int *ftype, int nf, int *dtype, struct tm * tm, fse
break;
case DTK_MILLISEC:
/* avoid overflowing the fsec field */
tm->tm_sec += val / 1000;
val -= (val / 1000) * 1000;
#ifdef HAVE_INT64_TIMESTAMP
*fsec += ((val + fval) * 1000);
#else