From 0f6be37fcb08b7d66834bd9dce287ef7196f0e02 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 17 Jan 2005 18:47:15 +0000 Subject: [PATCH] Clarify that the --enable-integer-datetimes switch affects the time and interval datatypes as well as timestamp. --- doc/src/sgml/datatype.sgml | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index f515108d50..0ca87bfb2c 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -1,5 +1,5 @@ @@ -1351,7 +1351,7 @@ SELECT b, char_length(b) FROM test2; time intervals -178000000 years 178000000 years - 1 microsecond + 1 microsecond / 14 digits date @@ -1367,7 +1367,7 @@ SELECT b, char_length(b) FROM test2; times of day only 00:00:00.00 23:59:59.99 - 1 microsecond + 1 microsecond / 14 digits time [ (p) ] with time zone @@ -1375,7 +1375,7 @@ SELECT b, char_length(b) FROM test2; times of day only, with time zone 00:00:00.00+12 23:59:59.99-12 - 1 microsecond + 1 microsecond / 14 digits @@ -1410,7 +1410,11 @@ SELECT b, char_length(b) FROM test2; eight-byte integers (a compile-time option), microsecond precision is available over the full range of values. However eight-byte integer timestamps have a more limited range of - dates than shown above: from 4713 BC up to 294276 AD. + dates than shown above: from 4713 BC up to 294276 AD. The same + compile-time option also determines whether time and + interval values are stored as floating-point or eight-byte + integers. In the floating-point case, large interval values + degrade in precision as the size of the interval increases. -- 2.40.0