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.94.2) (envelope-from ) id 1uFaTP-006F8z-Br for pgsql-general@arkaria.postgresql.org; Thu, 15 May 2025 15:26:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uFaTO-00FFik-34 for pgsql-general@arkaria.postgresql.org; Thu, 15 May 2025 15:26:14 +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.94.2) (envelope-from ) id 1uFaTN-00FFic-Om for pgsql-general@lists.postgresql.org; Thu, 15 May 2025 15:26:13 +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.96) (envelope-from ) id 1uFaTK-0022zL-1V for pgsql-general@postgresql.org; Thu, 15 May 2025 15:26:13 +0000 Received: from pro.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 54FFQ8CL1774589; Thu, 15 May 2025 11:26:08 -0400 From: Tom Lane To: "=?ISO-8859-1?B?bWlv?=" <850455645@qq.com> cc: "=?ISO-8859-1?B?cGdzcWwtZ2VuZXJhbA==?=" Subject: Re: where to find pg coverage report of history release In-reply-to: References: Comments: In-reply-to "=?ISO-8859-1?B?bWlv?=" <850455645@qq.com> message dated "Thu, 15 May 2025 12:15:35 +0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <11792.1747322768.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 15 May 2025 11:26:08 -0400 Message-ID: <11793.1747322768@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "=3D?ISO-8859-1?B?bWlv?=3D" <850455645@qq.com> writes: > In https://coverage.postgresql.org, there is only the coverage report fo= r the latest pg release. where can i find report of historical versions? We don't track that. It's not very hard to make your own though: https://www.postgresql.org/docs/current/regress-coverage.html regards, tom lane