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 1wuBJI-000WD8-1V for pgsql-committers@arkaria.postgresql.org; Wed, 12 Aug 2026 15:56:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wuBJG-008pNi-15 for pgsql-committers@arkaria.postgresql.org; Wed, 12 Aug 2026 15:56: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 1wuBJG-008pNW-0P for pgsql-committers@lists.postgresql.org; Wed, 12 Aug 2026 15:56: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 1wuBJB-00000000NkE-0xN1 for pgsql-committers@lists.postgresql.org; Wed, 12 Aug 2026 15:56:06 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 67CFtxCg2730784; Wed, 12 Aug 2026 11:55:59 -0400 From: Tom Lane To: Tomas Vondra cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Change wal_compression=on to the first of zstd, lz4, pglz In-reply-to: References: <2569564.1786492371@sss.pgh.pa.us> Comments: In-reply-to Tomas Vondra message dated "Wed, 12 Aug 2026 17:46:49 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2730782.1786550159.1@sss.pgh.pa.us> Date: Wed, 12 Aug 2026 11:55:59 -0400 Message-ID: <2730783.1786550159@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Tomas Vondra writes: > On 8/12/26 01:52, Tom Lane wrote: >> [ raised eyebrow... ] I don't object to this change in master, >> but it seems pretty out of scope for v19 at this point. > Yeah. The consensus in the discussion thread was it'd be good to do this > in 19, together with the TOAST compression default. I wasn't sure about > that, so I consulted with the RMT and the response was it's OK. Ah. The point about changing this along with the TOAST compression default does make sense. Objection withdrawn ... but this needs to get into the v19 release notes beside the other change. regards, tom lane