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 1rcT5w-000IGH-Dp for pgsql-bugs@arkaria.postgresql.org; Tue, 20 Feb 2024 16:35:48 +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 1rcT4w-000rFj-Fi for pgsql-bugs@arkaria.postgresql.org; Tue, 20 Feb 2024 16:34:46 +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 1rcT4w-000rFb-7t for pgsql-bugs@lists.postgresql.org; Tue, 20 Feb 2024 16:34:46 +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.94.2) (envelope-from ) id 1rcT4u-00025w-0L for pgsql-bugs@lists.postgresql.org; Tue, 20 Feb 2024 16:34:46 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 41KGYflf199834; Tue, 20 Feb 2024 11:34:42 -0500 From: Tom Lane To: harukat@sraoss.co.jp cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18353: PG16.2 release note doc bug in "In contrib/bloom, fix overly tight assertion ..." In-reply-to: <18353-926aa99cfe58aa78@postgresql.org> References: <18353-926aa99cfe58aa78@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Tue, 20 Feb 2024 07:37:06 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <199832.1708446881.1@sss.pgh.pa.us> Date: Tue, 20 Feb 2024 11:34:41 -0500 Message-ID: <199833.1708446881@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > In the release note for 16.2, 15.6 and 14.11, the following entry looks > wrong. > The fix is not on contrib/bloom but BRIN's bloom operator class. You're right, I misread the commit log entry. I'll adjust this, although it won't show up anywhere till the next quarterly releases. regards, tom lane