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 1wpn0i-001qhI-0u for pgsql-hackers@arkaria.postgresql.org; Fri, 31 Jul 2026 13:10:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wpn0h-00G5SS-0h for pgsql-hackers@arkaria.postgresql.org; Fri, 31 Jul 2026 13:10:47 +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.96) (envelope-from ) id 1wpn0g-00G5SJ-2l for pgsql-hackers@lists.postgresql.org; Fri, 31 Jul 2026 13:10:46 +0000 Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wpn0a-00000001Etg-3ZFF for pgsql-hackers@postgresql.org; Fri, 31 Jul 2026 13:10:45 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=WaN5L/4pX75cugZoRjYz00d4QLDQ2r0wQvEBWBRtTvc=; b=l2DfKftsdHdwYGOpZDtwl822Yz GU4smB4Bs5Bxyx8UsAZBJ+kupmybWFeubdnIN+1sAq2VODTodu95El4seUp8IWONxRMH+eJXofTxz 3giV1BzG+/YEqKAslEjsfIRUih6tucmpcr9qul+CYg5PkqmmaWB+tifk3LT68Gr7J0VdDsRYb8fkE c2hwmmUUmmj/teVWyS39eYd4fC4ehM2CMqvWsbcuiragm7znyoW+aX9wwl2wTlEStJxxLT86fgfcJ 8SawKokknA7TD2AIi41Qp955AXZe6bcaQfWQbMGCszCnkMBIwXiK+pdaR3YmaC1lTXYRsFHZx+8GG sG4NIqLQ==; Received: from authenticated-user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from ) id 1wpn0Q-00A2E8-0Y; Fri, 31 Jul 2026 13:10:30 +0000 Date: Fri, 31 Jul 2026 15:10:29 +0200 From: Christoph Berg To: Tomas Vondra Cc: wenhui qiu , Laurenz Albe , Andres Freund , Jelte Fennema-Nio , Michael Paquier , Japin Li , Fujii Masao , pgsql-hackers , John Naylor Subject: Re: WAL compression setting after PostgreSQL LZ4 default change Message-ID: Mail-Followup-To: Christoph Berg , Tomas Vondra , wenhui qiu , Laurenz Albe , Andres Freund , Jelte Fennema-Nio , Michael Paquier , Japin Li , Fujii Masao , pgsql-hackers , John Naylor References: <50d60598-3fbf-4344-8b07-bf02114f7fd0@vondra.me> <1314f5843859d5f83d5eb0a47b15d9291567cf40.camel@cybertec.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Debian-User: myon List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Re: Tomas Vondra > The one thing I don't quite like on the patch is that it actually > defaults to zstd before lz4. Which seems to not quite match the intent > to have both toast and wal default to the same thing. I don't have a > strong preference for either algorithm, but I also don't see why to put > zstd before lz4. I'd do it the other way around, i.e. lz4->zstd->pglz. About the intent, I see it more as "PG19 is the version that switched away from pglz". It could be lz4 for both, or it could be lz4 for TOAST and zstd for WAL. There is some value in having both the same, but I'd defer to what the others are saying. I don't have a preference either way. This was just the last thing expressed here. (If we can't agree on that point, could we please still make the change and just toss a coin about this "bit"? :D) Christoph