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 1weW3m-004qPr-0V for pgsql-hackers@arkaria.postgresql.org; Tue, 30 Jun 2026 10:51:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1weW3i-007hoe-2f for pgsql-hackers@arkaria.postgresql.org; Tue, 30 Jun 2026 10:51:18 +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 1weW3i-007hoV-1E for pgsql-hackers@lists.postgresql.org; Tue, 30 Jun 2026 10:51:18 +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 1weW3g-00000000u8E-0Zwd for pgsql-hackers@postgresql.org; Tue, 30 Jun 2026 10:51:17 +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=IZm/EoQ4OJEFRGlcSNJaYr4Dr96079zV1hcr+6RR1zE=; b=IzFn7cU2aIElazfFH6vQ0FOBlo MfFZxF3cbWPsc0DbEZ2ubntyB587TNg4x53OWE0+D8HZtOrmvhqcxxE6w3zIAPRbtxdMwYByE/Ubw d8xdajbhoaojffNX0U3jXIDENyFm0R8foCxynDLbOb/ztLOnht+L9kt1ByUECdavBDToijg7gRJ1s 7tYiCTk1QOPrmrIIPTvIhLVYEyi/nA7IFYMQ4fCsA/WhePA+4X++6DPLaq1iapNyqLqxhjTbDuWIE hNlZmQ6wcfG0+NjMjrrCf+Kb41iCZJde1te7/03ukBHnikPij1thUEaxrR8prtuIW5pmuyK7tRmLI lGsJzIbA==; 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 1weW3d-0070wl-2Q; Tue, 30 Jun 2026 10:51:14 +0000 Date: Tue, 30 Jun 2026 12:51:13 +0200 From: Christoph Berg To: wenhui qiu Cc: pgsql-hackers , Japin Li , John Naylor , Michael Paquier Subject: Re: WAL compression setting after PostgreSQL LZ4 default change Message-ID: Mail-Followup-To: Christoph Berg , wenhui qiu , pgsql-hackers , Japin Li , John Naylor , Michael Paquier References: 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: wenhui qiu > The recent PostgreSQL commit changes the default TOAST compression to lz4 > when LZ4 support is available, based on the rationale that LZ4 is generally > more efficient than pglz in terms of CPU usage and compression ratio.Given > that, should we also consider changing the default compression method used > by wal_compression = on from pglz to lz4? +1 from me. I would prefer this patch over the doc-only one that I sent in the other thread. This should go into PG19 so we don't have two different versions that flip the default from pglz to lz4. Christoph