mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-12-27 08:39:28 +08:00
Fix sloppy comment.
This commit is contained in:
parent
c4d0ff32e9
commit
b3d7af46a9
@ -8,7 +8,7 @@
|
||||
*
|
||||
*
|
||||
* IDENTIFICATION
|
||||
* $Header: /cvsroot/pgsql/src/backend/utils/adt/date.c,v 1.75 2003/01/09 01:06:57 tgl Exp $
|
||||
* $Header: /cvsroot/pgsql/src/backend/utils/adt/date.c,v 1.76 2003/01/22 20:44:20 tgl Exp $
|
||||
*
|
||||
*-------------------------------------------------------------------------
|
||||
*/
|
||||
@ -656,7 +656,7 @@ AdjustTimeForTypmod(TimeADT *time, int32 typmod)
|
||||
/*
|
||||
* Note: this round-to-nearest code is not completely consistent
|
||||
* about rounding values that are exactly halfway between integral
|
||||
* values. On most platforms, rint() will implement round-to-nearest,
|
||||
* values. On most platforms, rint() will implement round-to-nearest-even,
|
||||
* but the integer code always rounds up (away from zero). Is it
|
||||
* worth trying to be consistent?
|
||||
*/
|
||||
|
@ -8,7 +8,7 @@
|
||||
*
|
||||
*
|
||||
* IDENTIFICATION
|
||||
* $Header: /cvsroot/pgsql/src/backend/utils/adt/timestamp.c,v 1.76 2003/01/09 01:06:57 tgl Exp $
|
||||
* $Header: /cvsroot/pgsql/src/backend/utils/adt/timestamp.c,v 1.77 2003/01/22 20:44:20 tgl Exp $
|
||||
*
|
||||
*-------------------------------------------------------------------------
|
||||
*/
|
||||
@ -206,7 +206,7 @@ AdjustTimestampForTypmod(Timestamp *time, int32 typmod)
|
||||
/*
|
||||
* Note: this round-to-nearest code is not completely consistent
|
||||
* about rounding values that are exactly halfway between integral
|
||||
* values. On most platforms, rint() will implement round-to-nearest,
|
||||
* values. On most platforms, rint() will implement round-to-nearest-even,
|
||||
* but the integer code always rounds up (away from zero). Is it
|
||||
* worth trying to be consistent?
|
||||
*/
|
||||
@ -677,7 +677,7 @@ AdjustIntervalForTypmod(Interval *interval, int32 typmod)
|
||||
/*
|
||||
* Note: this round-to-nearest code is not completely consistent
|
||||
* about rounding values that are exactly halfway between integral
|
||||
* values. On most platforms, rint() will implement round-to-nearest,
|
||||
* values. On most platforms, rint() will implement round-to-nearest-even,
|
||||
* but the integer code always rounds up (away from zero). Is it
|
||||
* worth trying to be consistent?
|
||||
*/
|
||||
|
Loading…
Reference in New Issue
Block a user