Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wKcgn-001Bqe-1k for pgsql-docs@arkaria.postgresql.org; Wed, 06 May 2026 13:53:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wKcfk-00HB5X-39 for pgsql-docs@arkaria.postgresql.org; Wed, 06 May 2026 13:52:20 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wKcfk-00HB5J-2R for pgsql-docs@lists.postgresql.org; Wed, 06 May 2026 13:52:20 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wKcfd-00000000pZt-1q03 for pgsql-docs@lists.postgresql.org; Wed, 06 May 2026 13:52:15 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 646Dq2R4767366; Wed, 6 May 2026 09:52:02 -0400 From: Tom Lane To: "David G. Johnston" cc: scoobster17@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: Suspected documentation error In-reply-to: References: <177801333530.795.16999885814007014333@wrigleys.postgresql.org> Comments: In-reply-to "David G. Johnston" message dated "Tue, 05 May 2026 16:27:42 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <767364.1778075522.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 06 May 2026 09:52:02 -0400 Message-ID: <767365.1778075522@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" writes: > On Tue, May 5, 2026 at 3:02=E2=80=AFPM PG Doc comments form > wrote: >> in the Udemy course I'm following, I noticed that the notes "OF" state >> "time-zone offset from UTC (HH or HH:MM)", which I believe should be >> "time-zone offset from UTC (HH or HH:MI)". > Technically interpreting either of those according to the format specifi= ers > co-located in that table is wrong. Yeah; I think writing MI would make for more confusion not less, since this specifier doesn't emit the same values that HH and MI refer to. > All HH and MM stand for here are hours > and minutes, trying to communicate fixed two-digits. I'm inclined to try to fix it via formatting: change HH and MM to lower case and wrap them in so they render in italics. The other details are easily discovered by experiment, so I don't feel a need to make the table entries any more verbose. Thoughts? regards, tom lane