docs: to_timestamp and to_date do minimal range checking

Initial patch from Steve Crawford

diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index a1f627cbd6cf9d5bbb71abea93380b3fd79bf912..b1ea46677c175037cc44b5c5e24314dd6be31cc6 100644 (file)
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -5783,6 +5783,20 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
       
      
 
+     
+      
+       to_timestamp and to_date
+       exist to handle input formats that cannot be converted by
+       simple casting.  These functions interpret input liberally,
+       with minimal error checking.  While they produce valid output,
+       the conversion can yield unexpected results.  For example,
+       input to these functions is not restricted by normal ranges,
+       thus to_date('20096040','YYYYMMDD') returns
+       2014-01-17 rather than causing an error.
+       Casting does not have this behavior.
+      
+     
+  
      
       
        Ordinary text is allowed in to_char