pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pgsql: Doc: fix bogus example about ambiguous timestamps.
6+ messages / 1 participants
[nested] [flat]

* pgsql: Doc: fix bogus example about ambiguous timestamps.
@ 2022-01-10 16:47  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 2022-01-10 16:47 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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_10_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/9a8b1b6777178c76c48043c3d7bfbe911d2ee577

Modified Files
--------------
doc/src/sgml/datetime.sgml | 20 +++++++++-----------
1 file changed, 9 insertions(+), 11 deletions(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Doc: fix bogus example about ambiguous timestamps.
@ 2022-01-10 16:47  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 2022-01-10 16:47 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/2180833ba90e9657a7e622b419194763890c8a6d

Modified Files
--------------
doc/src/sgml/datetime.sgml | 20 +++++++++-----------
1 file changed, 9 insertions(+), 11 deletions(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Doc: fix bogus example about ambiguous timestamps.
@ 2022-01-10 16:47  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 2022-01-10 16:47 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/05cdda68f8f6e63cb87bc1776236d7619cd89fb7

Modified Files
--------------
doc/src/sgml/datetime.sgml | 20 +++++++++-----------
1 file changed, 9 insertions(+), 11 deletions(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Doc: fix bogus example about ambiguous timestamps.
@ 2022-01-10 16:47  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 2022-01-10 16:47 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/790d6edf639a8c6cb12eb9f81069349c28767976

Modified Files
--------------
doc/src/sgml/datetime.sgml | 20 +++++++++-----------
1 file changed, 9 insertions(+), 11 deletions(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Doc: fix bogus example about ambiguous timestamps.
@ 2022-01-10 16:47  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 2022-01-10 16:47 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Doc: fix bogus example about ambiguous timestamps.
@ 2022-01-10 16:47  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 2022-01-10 16:47 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/9ef2c655558bb1ec20c4f87850d9322420e35acb

Modified Files
--------------
doc/src/sgml/datetime.sgml | 20 +++++++++-----------
1 file changed, 9 insertions(+), 11 deletions(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread


end of thread, other threads:[~2022-01-10 16:47 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-01-10 16:47 pgsql: Doc: fix bogus example about ambiguous timestamps. Tom Lane <tgl@sss.pgh.pa.us>
2022-01-10 16:47 pgsql: Doc: fix bogus example about ambiguous timestamps. Tom Lane <tgl@sss.pgh.pa.us>
2022-01-10 16:47 pgsql: Doc: fix bogus example about ambiguous timestamps. Tom Lane <tgl@sss.pgh.pa.us>
2022-01-10 16:47 pgsql: Doc: fix bogus example about ambiguous timestamps. Tom Lane <tgl@sss.pgh.pa.us>
2022-01-10 16:47 pgsql: Doc: fix bogus example about ambiguous timestamps. Tom Lane <tgl@sss.pgh.pa.us>
2022-01-10 16:47 pgsql: Doc: fix bogus example about ambiguous timestamps. Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox