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.96) (envelope-from ) id 1w5PNA-003DqR-1i for pgsql-hackers@arkaria.postgresql.org; Wed, 25 Mar 2026 14:38:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w5PN8-00EQmr-2o for pgsql-hackers@arkaria.postgresql.org; Wed, 25 Mar 2026 14:38:15 +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.96) (envelope-from ) id 1w5PN8-00EQmV-1V for pgsql-hackers@lists.postgresql.org; Wed, 25 Mar 2026 14:38:14 +0000 Received: from relay7-d.mail.gandi.net ([2001:4b98:dc4:8::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w5PN5-00000001587-3ARC for pgsql-hackers@postgresql.org; Wed, 25 Mar 2026 14:38:14 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id 498013EBE9; Wed, 25 Mar 2026 14:38:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vondra.me; s=gm1; t=1774449486; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=DWh7xgLjx0CA12m64VNecFI6WprRoabP6qZe0nAUUvY=; b=GNnsUjJe1koxavE1L29cas2eUNfDSke9l+t5bsaVED/yMH3+T2l0DBvOJlXsFjHG7Y8/sH GqEijxIj1o/IAy/aCIY7ThE147sp60XosqfenxE1HYZ9YRBF8rL3S+gJv/HVd8mH4mFYVs IYcarVvD9us03dnrkEGyOd4idYahuIHOuUwSLFQ84w5k0m2+YuZCuyNuDA0EzNH16/t7rN BrjnnvWXUA7SAuNampAj8TX/vq9JMpJ7aHs3Gh7WPAVS6Jgt2kGNbAKvqKGM8N+k1Q5SYB xXKCpgv5FqIhbN7UhE8htLtXrssCHrePz1Jfnrg5OWicv0UvgilD/a2lNL4Gkw== Message-ID: <753e7734-95d9-45d3-85d9-a53638b1b3dd@vondra.me> Date: Wed, 25 Mar 2026 15:38:01 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Test timings are increasing too fast for cfbot To: Andres Freund , pgsql-hackers@postgresql.org Cc: Dilip Kumar , Jelte Fennema-Nio , Thomas Munro , Noah Misch References: Content-Language: en-US From: Tomas Vondra In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-GND-Sasl: tomas@vondra.me X-GND-Score: -100 X-GND-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgdefvdegjedvucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuifetpfffkfdpucggtfgfnhhsuhgsshgtrhhisggvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfevfhfhjggtgfesthejredttddvjeenucfhrhhomhepvfhomhgrshcugghonhgurhgruceothhomhgrshesvhhonhgurhgrrdhmvgeqnecuggftrfgrthhtvghrnhepledugeeikefglefhgfffuedvleetteevgefhvdeikeefudduuddvhfevudefhfevnecukfhppeegiedrudefhedrudehrddujeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpeegiedrudefhedrudehrddujedphhgvlhhopegluddtrddufeejrddtrdduiegnpdhmrghilhhfrhhomhepthhomhgrshesvhhonhgurhgrrdhmvgdpqhhiugepgeelkedtudefgfeugfelpdhmohguvgepshhmthhpohhuthdpnhgspghrtghpthhtohepiedprhgtphhtthhopegrnhgurhgvshesrghnrghrrgiivghlrdguvgdprhgtphhtthhopehpghhsqhhlqdhhrggtkhgvrhhssehpohhsthhgrhgvshhqlhdrohhrghdprhgtphhtthhopeguihhlihhpsggrlhgruhhtsehgmhgrihhlrdgtohhmpdhrtghpthhtohepphhoshhtghhrvghssehjvghlthgvfhdrnhhlpdhrtghpthhtohepthhhohhmrghsmhhunhhrohesghhmrghil hdrtghomhdprhgtphhtthhopehnohgrhheslhgvrggusghorghtrdgtohhm X-GND-State: clean List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 3/25/26 04:15, Andres Freund wrote: > ... > > The slowest test is stats_ext.sql - Not surprising, it does sequential scans > of tables with ~1000-10000 rows over and over again. I don't see why it has > to do that with as many rows as it does. > IIRC we needed to use non-trivial amounts of data to ensure building the right right type of statistics (e.g. no MCV). But I understand it can be annoyingly expensive, so I'll try to make it cheaper. > ... > 2) AssertCheckRanges() (only in the brin test, but there a very large portion > of the runtime) True. It is a very comprehensive validation of the ranges, and it was very useful - particularly during development. But I'll try to make it more targeted at the stuff actually changed / called less often. Both changes will require time (so that we don't lose test coverage), but I assume it's OK if that happens sometime after the feature freeze. regards -- Tomas Vondra