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 1vxuo9-00HFwh-32 for pgsql-hackers@arkaria.postgresql.org; Wed, 04 Mar 2026 22:35:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vxuo7-00EeF4-0n for pgsql-hackers@arkaria.postgresql.org; Wed, 04 Mar 2026 22:35:07 +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 1vxuo6-00EeEv-35 for pgsql-hackers@lists.postgresql.org; Wed, 04 Mar 2026 22:35:07 +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.98.2) (envelope-from ) id 1vxunw-00000000gdy-2kOF for pgsql-hackers@postgresql.org; Wed, 04 Mar 2026 22:35:02 +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 624MYn3e1669306; Wed, 4 Mar 2026 17:34:49 -0500 From: Tom Lane To: Jacob Champion cc: Michael Paquier , PostgreSQL Hackers , Mark Wong Subject: Re: pgsql: Change default value of default_toast_compression to "lz4", when In-reply-to: References: Comments: In-reply-to Jacob Champion message dated "Wed, 04 Mar 2026 09:01:06 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1669304.1772663689.1@sss.pgh.pa.us> Date: Wed, 04 Mar 2026 17:34:49 -0500 Message-ID: <1669305.1772663689@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jacob Champion writes: > I know there's no "good time" to change a configuration default, but > the timing now is especially unfortunate, because Mark maintains many > of those failing animals and he is traveling this week. Any chance we > can delay this patch a bit to coordinate, and keep the buildfarm > green? By my count, two-thirds of the buildfarm is broken. (100 failing animals, 56 working ones have reported since this commit.) We would not normally tolerate leaving things that way for any great length of time, and I don't think this commit should get a pass. I think it needs to be reverted until a very much larger fraction of buildfarm owners have prepared for it. regards, tom lane