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 1sjCdz-00GKpP-Eb for pgsql-general@arkaria.postgresql.org; Wed, 28 Aug 2024 06:59:03 +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 1sjCdx-000wWq-Hu for pgsql-general@arkaria.postgresql.org; Wed, 28 Aug 2024 06:59:02 +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 1sjCdw-000wWh-H7 for pgsql-general@lists.postgresql.org; Wed, 28 Aug 2024 06:59:01 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sjCdt-001saw-NV for pgsql-general@lists.postgresql.org; Wed, 28 Aug 2024 06:59:00 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date:MIME-Version:Sender :Reply-To:Content-ID:Content-Description; bh=H8B7Ae5dH29KeYSR4Ym/dfQsKHYtJ2LUeQ8JDYJ1lug=; b=QEenLGBUZArvyw2ANmZ4N9GZ7p XDODpoC8TItneINAIDHXW5P7z54VqfkxyRd8OBJdJuoylldDRSeOew7GxHcmdCmgw7TCY+PucAL+l piuH5SokfutGE031LyEmVsUEYEUuJEiUbMOHXSXJP6nSo8q+4ZF1L9WRe96/CZlRpHeT7SGhwmPzz LMcnGlCzV0CHeWSRs3jNbbrhb5/Uy9psdR7LGWcf2KeeZ2zBqLeQMGXugW+t1GyeiY1qDxtk2DBcu EnDnvlP9ggarOYrwsfp+8QabtuDlYleZR74P7Cd17giNaJvVBYh5g1cWH5npwoTUjw225i/D924Dh ZobY5gtQ==; Received: from meldrar.postgresql.org ([87.238.57.231] helo=webmail.postgresql.org) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sjCds-007Xud-4X; Wed, 28 Aug 2024 06:58:58 +0000 MIME-Version: 1.0 Date: Wed, 28 Aug 2024 16:58:56 +1000 From: Justin Clift To: David Rowley Cc: Tom Lane , nikhil raj , "pgsql-generallists.postgresql.org" , NIKITA PATEL , Patel Khushbu Subject: Re: Significant Execution Time Difference Between PG13.14 and PG16.4 for Query on information_schema Tables. In-Reply-To: References: <2962669.1724722813@sss.pgh.pa.us> User-Agent: Roundcube Webmail/1.4.15 Message-ID: <7b97171e276c41ec6ae4eeb8c2e8b47d@postgresql.org> X-Sender: justin@postgresql.org Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2024-08-27 20:14, David Rowley wrote: > On Tue, 27 Aug 2024 at 18:00, Justin Clift > wrote: >> As a general thought, seeing that this might be an actual problem >> should some kind of automated testing be added that checks for >> performance regressions like this? > > We normally try to catch these sorts of things with regression tests. > Of course, that requires having a test that would catch a particular > problem, which we don't seem to have for this particular case. A > performance test would also require testing a particular scenario, so > I don't see why that's better. A regression test is better suited as > there's no middle ground between pass and fail. Yeah, that's the kind of thing I was thinking. Any idea who normally does those, and if it would be reasonable to add test(s) for the internal information tables? Regards and best wishes, Justin Clift