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 1tmXZG-007UPY-T9 for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Feb 2025 12:28:15 +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 1tmXYI-002JBX-3S for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Feb 2025 12:27:14 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tmXYH-002J6Z-Nq for pgsql-hackers@lists.postgresql.org; Mon, 24 Feb 2025 12:27:13 +0000 Received: from forward502d.mail.yandex.net ([2a02:6b8:c41:1300:1:45:d181:d502]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tmXYE-000TQf-05 for pgsql-hackers@lists.postgresql.org; Mon, 24 Feb 2025 12:27:12 +0000 Received: from mail-nwsmtp-smtp-production-main-99.klg.yp-c.yandex.net (mail-nwsmtp-smtp-production-main-99.klg.yp-c.yandex.net [IPv6:2a02:6b8:c42:42ad:0:640:7db8:0]) by forward502d.mail.yandex.net (Yandex) with ESMTPS id 2708560D44; Mon, 24 Feb 2025 15:27:06 +0300 (MSK) Received: by mail-nwsmtp-smtp-production-main-99.klg.yp-c.yandex.net (smtp/Yandex) with ESMTPSA id 2RaKYC2LdSw0-uYlfLTZY; Mon, 24 Feb 2025 15:27:05 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tantorlabs.com; s=mail; t=1740400025; bh=qyRP+ZXw4dOdxHGmHce2603NIn0Jd8H6n7WWODj/mBw=; h=From:In-Reply-To:Cc:Date:References:To:Subject:Message-ID; b=pyOCFrWx/d1ZLtTDvrhZNTTBsDtrEMYyy2BpRfTMI//oRNZX6xM6jAGSBAkYNrnhW AlcO1cAOIaJlpQG2vYMkZGb5cGPSZolxQVNglLicWu2BXNBfGKVORSEHIZRxV+JKJp Sil/IlRKFRyKSuXIvlA0w0u0MUbxGnAFHXDXnpbw= Authentication-Results: mail-nwsmtp-smtp-production-main-99.klg.yp-c.yandex.net; dkim=pass header.i=@tantorlabs.com Message-ID: <5abac84e-fc78-459a-a191-13efeb58c161@tantorlabs.com> Date: Mon, 24 Feb 2025 15:27:02 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: a very significant fraction of the buildfarm is now pink To: Jelte Fennema-Nio , Robert Haas Cc: Andres Freund , Tom Lane , Andrei Lepikhov , PostgreSQL Hackers References: <01ec86c1-e04b-4cbe-b641-22cae8b87604@tantorlabs.com> <73e2440e-7d8b-4860-974d-931a93326d95@gmail.com> <3737950.1740182671@sss.pgh.pa.us> Content-Language: en-US From: Ilia Evdokimov In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, Regarding the patch push, I am not a committer, but perhaps my perspective might be interesting. When I noticed late on Friday evening that the tests had failed, I was quite anxious about the situation, thinking I would need to fix it right away. However, Robert committed the fix before that. In general, when someone commits in any project, I believe the scale of the commit should be taken into account. In the case of postgres, if the commit changes code in critical areas like the planner, WAL, or some API, or involves large code changes, it’s important to be prepared to fix any issues that may arise. However, when changes are more minor—such as documentation, renaming something, or small refactors—committing late on a Friday may be less of a concern. In other words, the larger the changes or the more vulnerable the areas of the code, the more one should be prepared for potential issues. But how to determine this boundary in postgres, I am not sure. I am confident that you will have a much better sense and experience of how to handle it. -- Best regards, Ilia Evdokimov, Tantor Labs LLC.