|
8 | 8 | * |
9 | 9 | * |
10 | 10 | * IDENTIFICATION |
11 | | - * $Header: /cvsroot/pgsql/src/backend/utils/adt/timestamp.c,v 1.76 2003/01/09 01:06:57 tgl Exp $ |
| 11 | + * $Header: /cvsroot/pgsql/src/backend/utils/adt/timestamp.c,v 1.77 2003/01/22 20:44:20 tgl Exp $ |
12 | 12 | * |
13 | 13 | *------------------------------------------------------------------------- |
14 | 14 | */ |
@@ -206,7 +206,7 @@ AdjustTimestampForTypmod(Timestamp *time, int32 typmod) |
206 | 206 | /* |
207 | 207 | * Note: this round-to-nearest code is not completely consistent |
208 | 208 | * about rounding values that are exactly halfway between integral |
209 | | - * values. On most platforms, rint() will implement round-to-nearest, |
| 209 | + * values. On most platforms, rint() will implement round-to-nearest-even, |
210 | 210 | * but the integer code always rounds up (away from zero). Is it |
211 | 211 | * worth trying to be consistent? |
212 | 212 | */ |
@@ -677,7 +677,7 @@ AdjustIntervalForTypmod(Interval *interval, int32 typmod) |
677 | 677 | /* |
678 | 678 | * Note: this round-to-nearest code is not completely consistent |
679 | 679 | * about rounding values that are exactly halfway between integral |
680 | | - * values. On most platforms, rint() will implement round-to-nearest, |
| 680 | + * values. On most platforms, rint() will implement round-to-nearest-even, |
681 | 681 | * but the integer code always rounds up (away from zero). Is it |
682 | 682 | * worth trying to be consistent? |
683 | 683 | */ |
|