NotificationsYou must be signed in to change notification settings
Fork28
Star153

Commitb3d7af4

committed

Fix sloppy comment.

1 parentc4d0ff3 commitb3d7af4Copy full SHA for b3d7af4

File tree

2 files changed

-5

lines changed

src/backend/utils/adt
- date.c
- timestamp.c

2 files changed

-5

lines changed

`‎src/backend/utils/adt/date.c‎`

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -8,7 +8,7 @@`
`8`	`8`	`*`
`9`	`9`	`*`
`10`	`10`	`* IDENTIFICATION`
`11`		`- * $Header: /cvsroot/pgsql/src/backend/utils/adt/date.c,v 1.75 2003/01/09 01:06:57 tgl Exp $`
	`11`	`+ * $Header: /cvsroot/pgsql/src/backend/utils/adt/date.c,v 1.76 2003/01/22 20:44:20 tgl Exp $`
`12`	`12`	`*`
`13`	`13`	`*-------------------------------------------------------------------------`
`14`	`14`	`*/`
`@@ -656,7 +656,7 @@ AdjustTimeForTypmod(TimeADT *time, int32 typmod)`
`656`	`656`	`/*`
`657`	`657`	`* Note: this round-to-nearest code is not completely consistent`
`658`	`658`	`* about rounding values that are exactly halfway between integral`
`659`		`- * values. On most platforms, rint() will implement round-to-nearest,`
	`659`	`+ * values. On most platforms, rint() will implement round-to-nearest-even,`
`660`	`660`	`* but the integer code always rounds up (away from zero). Is it`
`661`	`661`	`* worth trying to be consistent?`
`662`	`662`	`*/`

`‎src/backend/utils/adt/timestamp.c‎`

Lines changed: 3 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -8,7 +8,7 @@`
`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`	`*/`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commitb3d7af4

File tree

2 files changed

2 files changed

`‎src/backend/utils/adt/date.c‎`

`‎src/backend/utils/adt/timestamp.c‎`

0 commit comments