From 23b8a0ce61c0fac72c9b40acb875bb0ab0a5b915 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Wed, 29 Jan 2003 01:08:42 +0000 Subject: Repair array subscript overrun identified by Yichen Xie. Reduce the value of MAX_TIME_PRECISION in floating-point-timestamp-storage case from 13 to 10, which is as much as time_out is actually willing to print. (The alternative of increasing the number of digits we are willing to print looks risky; we might find ourselves printing roundoff garbage.) --- doc/src/sgml/datatype.sgml | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 3d75edca765..9bbd5146c2a 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -1,5 +1,5 @@ @@ -1297,8 +1297,7 @@ SELECT b, char_length(b) FROM test2; fractional digits retained in the seconds field. By default, there is no explicit bound on precision. The allowed range of p is from 0 to 6 for the - timestamp and interval types, 0 to 13 - for the time types. + timestamp and interval types. @@ -1314,6 +1313,12 @@ SELECT b, char_length(b) FROM test2; + + For the time types, the allowed range of + p is from 0 to 6 when eight-byte integer + storage is used, or from 0 to 10 when floating-point storage is used. + + Time zones, and time-zone conventions, are influenced by political decisions, not just earth geometry. Time zones around the @@ -1485,7 +1490,7 @@ SELECT b, char_length(b) FROM test2; The time type can be specified as time or as time without time zone. The optional precision - p should be between 0 and 13, and + p should be between 0 and 6, and defaults to the precision of the input time literal. -- cgit v1.2.3