| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Doc: fix bogus example about ambiguous timestamps. |
| Date: | 2022-01-10 16:47:22 |
| Message-ID: | E1n6xpK-0002kH-QO@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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
Branch
------
REL_12_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/850c704c72a2e86c682948a36c65c1bd6618829f
Modified Files
--------------
doc/src/sgml/datetime.sgml | 20 +++++++++-----------
1 file changed, 9 insertions(+), 11 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-01-11 00:56:16 | pgsql: Improve error handling of cryptohash computations |
| Previous Message | Andrew Dunstan | 2022-01-10 15:13:34 | pgsql: Avoid warning about uninitialized value in MSVC python3 tests |