From: Tom Lane <tgl@sss.pgh.pa.us>
To: mailtch@163.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16571: "time with time zone" type can input
 '00:00:00+1559'::time with time zone
In-reply-to: <16571-eb7501598de78c8a@postgresql.org>
References: <16571-eb7501598de78c8a@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 03 Aug 2020 07:26:09 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2329417.1596464280.1@sss.pgh.pa.us>
Date: Mon, 03 Aug 2020 10:18:00 -0400
Message-ID: <2329418.1596464280@sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.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