]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Doc: fix bogus example about ambiguous timestamps.
authorTom Lane <tgl@sss.pgh.pa.us>
Mon, 10 Jan 2022 16:46:16 +0000 (11:46 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Mon, 10 Jan 2022 16:46:33 +0000 (11:46 -0500)
commit850c704c72a2e86c682948a36c65c1bd6618829f
treef0ef517baabe422cb25f474f8a29774c3cf5b073
parent5b2cb9c29e09419bcce2e1be47a78a7e3d0a1156
Doc: fix bogus example about ambiguous timestamps.

I had a brain fade in commit d32899157, and used 2:30AM as the
example timestamp for both spring-forward and fall-back cases.
But it's not actually ambiguous at all in the fall-back case,
because that transition is from 2AM to 1AM under USA rules.
Fix the example to use 1:30AM, which *is* ambiguous.

Noted while answering a question from Aleksander Alekseev.
Back-patch to all supported branches.

Discussion: https://postgr.es/m/2191355.1641828552@sss.pgh.pa.us
doc/src/sgml/datetime.sgml