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 1vzzO0-001VZ4-2s for pgsql-docs@arkaria.postgresql.org; Tue, 10 Mar 2026 15:52:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vzzNx-004Kn6-1h for pgsql-docs@arkaria.postgresql.org; Tue, 10 Mar 2026 15:52:42 +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 1vzxnf-003gbb-2n for pgsql-docs@lists.postgresql.org; Tue, 10 Mar 2026 14:11:08 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vzxnd-00000001yk3-3ov8 for pgsql-docs@lists.postgresql.org; Tue, 10 Mar 2026 14:11:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=IVHiGuhcb3FOWA/yaoQc+cKuGXixm/7haqInmJMRZPQ=; b=K1jhZhWk2nPv871afohQqy9Wz9 Z5G/OhSruwjitDQsIjFcEbhspfIdVUF/nKgd8avh9QhBvmsTG1w73OW1T9aiTJlLZ7cnJB0iMcbTF ku17ghLf7DG2pmXj4EenKFUyi0qMARJjv5hsmOt+yuT3eWk6k2+DUmpLNwsshgb9IRMR7YfPRxbKE FUAcxFYYztowi0yvLLOJjZwBWErctua82s/kqxCgr2T6nQnGw/y0JKXjewnhHCWoSCh02+Y9Ilihy enIUUI9r2fAZHmaGfMQfufF39rqA5hhVOnm6vMrpfhyLGclXkCHFNQQ4idIOVwpIkGEO2p6dIg+l9 QxTKc8rA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vzxnc-003Rxk-1L for pgsql-docs@lists.postgresql.org; Tue, 10 Mar 2026 14:11:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vzxnZ-007Bfa-2s for pgsql-docs@lists.postgresql.org; Tue, 10 Mar 2026 14:11:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: INTERVAL output format for iso_8601 is without dashes To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: benjamin.kroeger@gmail.com Reply-To: benjamin.kroeger@gmail.com, pgsql-docs@lists.postgresql.org Date: Tue, 10 Mar 2026 14:10:47 +0000 Message-ID: <177315184745.772.13880446320967157412@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/datatype-datetime.html Description: https://www.postgresql.org/docs/current/datatype-datetime.html#DATATYPE-INT= ERVAL-OUTPUT The output format for mixed Interval in style specification iso_8601 is documented incorrectly. The documentation says `P-1Y-2M3D=E2=80=8BT-4H-5M-6S` while in reality ther= e are no dashes: `P1Y2M3D=E2=80=8BT4H5M6S`