From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | mailtch(at)163(dot)com |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16571: "time with time zone" type can input '00:00:00+1559'::time with time zone |
Date: | 2020-08-03 14:18:00 |
Message-ID: | 2329418.1596464280@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> In Document(https://www.postgresql.org/docs/current/datatype-datetime.html),
> "time with time zone" range is: 00:00:00+1459 to 24:00:00-1459
> but you can input:
> osdba=# select '00:00:00+1559'::time with time zone;
> timetz
> ----------------
> 00:00:00+15:59
> (1 row)
Hmm, the code is quite clear about it:
/*
* We allow numeric timezone offsets up to 15:59:59 either way from Greenwich.
* Currently, the record holders for wackiest offsets in actual use are zones
* Asia/Manila, at -15:56:00 until 1844, and America/Metlakatla, at +15:13:42
* until 1867. If we were to reject such values we would fail to dump and
* restore old timestamptz values with these zone settings.
*/
#define MAX_TZDISP_HOUR 15 /* maximum allowed hour part */
Apparently this documentation reference got overlooked the last time
we changed that :-(. Will fix, thanks for the report!
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Verite | 2020-08-03 17:35:50 | Re: BUG #16570: Collation not working |
Previous Message | PG Bug reporting form | 2020-08-03 07:26:09 | BUG #16571: "time with time zone" type can input '00:00:00+1559'::time with time zone |