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 1rVitD-000wYP-1Q for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Feb 2024 02:02:47 +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 1rVitB-0092Mq-KS for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Feb 2024 02:02:45 +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 1rVitB-0092Mg-Af for pgsql-hackers@lists.postgresql.org; Fri, 02 Feb 2024 02:02:45 +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 1rVit8-004zy9-DS for pgsql-hackers@lists.postgresql.org; Fri, 02 Feb 2024 02:02:44 +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 41222ZkS3046976; Thu, 1 Feb 2024 21:02:35 -0500 From: Tom Lane To: Alexander Korotkov cc: Andrei Lepikhov , Richard Guo , Pavel Borisov , vignesh C , PostgreSQL Developers , Tomas Vondra , Teodor Sigaev , David Rowley , "a.rybakina" Subject: Re: POC: GROUP BY optimization In-reply-to: References: <138cb2df-1a0d-48c0-be80-48aaf62e8aeb@postgrespro.ru> Comments: In-reply-to Alexander Korotkov message dated "Fri, 19 Jan 2024 16:21:48 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3046974.1706839355.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 01 Feb 2024 21:02:35 -0500 Message-ID: <3046975.1706839355@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Alexander Korotkov writes: > I'm going to push this if there are no objections. One of the test cases added by this commit has not been very stable in the buildfarm. Latest example is here: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dprion&dt=3D2024-= 02-01%2021%3A28%3A04 and I've seen similar failures intermittently on other machines. I'd suggest building this test atop a table that is more stable than pg_class. You're just waving a red flag in front of a bull if you expect stable statistics from that during a regression run. Nor do I see any particular reason for pg_class to be especially suited to the test. regards, tom lane