Document handling of invalid/ambiguous timestamp input near DST boundaries.
authorTom Lane <tgl@sss.pgh.pa.us>
Thu, 29 Nov 2018 23:28:10 +0000 (18:28 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Thu, 29 Nov 2018 23:28:10 +0000 (18:28 -0500)
commitd328991578d9f637fd1866639bfcbdfff64aba75
tree700572648b41eeba87e8a7edfd24fc9275d548a3
parent88bdbd3f746049834ae3cc972e6e650586ec3c9d
Document handling of invalid/ambiguous timestamp input near DST boundaries.

The source code comments documented this, but the user-facing docs, not
so much.  Add a section to Appendix B that discusses it.

In passing, improve a couple other things in Appendix B --- notably,
a long-obsolete claim that time zone abbreviations are looked up in
a fixed table.

Per bug #15527 from Michael Davidson.

Discussion: https://postgr.es/m/15527-f1be0b4dc99ebbe7@postgresql.org
doc/src/sgml/datetime.sgml