Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pgUS1-0000mM-9s for pgsql-committers@arkaria.postgresql.org; Sun, 26 Mar 2023 17:46:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pgUS0-0008Ew-4w for pgsql-committers@arkaria.postgresql.org; Sun, 26 Mar 2023 17:46:40 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pgURz-0008Em-UF for pgsql-committers@lists.postgresql.org; Sun, 26 Mar 2023 17:46:39 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pgURx-0000Nz-H0 for pgsql-committers@lists.postgresql.org; Sun, 26 Mar 2023 17:46:39 +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 32QHkZ3S3008878; Sun, 26 Mar 2023 13:46:35 -0400 From: Tom Lane To: Tomas Vondra cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Fix netmask handling in inet_minmax_multi_ops In-reply-to: <200b709d-6b1d-54e6-971d-b9dec75bd8a8@enterprisedb.com> References: <200b709d-6b1d-54e6-971d-b9dec75bd8a8@enterprisedb.com> Comments: In-reply-to Tomas Vondra message dated "Sun, 26 Mar 2023 18:48:45 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3008876.1679852795.1@sss.pgh.pa.us> Date: Sun, 26 Mar 2023 13:46:35 -0400 Message-ID: <3008877.1679852795@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Tomas Vondra writes: > On 3/20/23 10:28, Tomas Vondra wrote: >> Reported by Dmitry Dolgov, investigation and fix by me. >> Reported-by: Dmitry Dolgov > Correction - the issue was reported by Robins Tharakan, I got confused > while writing the commit message. I don't know if this issue is to be > mentioned in release notes (considering it mostly affects just assert > builds), but if we do we should the correct name. We don't normally cite the bug reporter's name in release notes, just the person(s) who wrote the patch. So this won't be an issue for the notes. regards, tom lane