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 1tDnTp-003G3a-Fm for pgsql-docs@arkaria.postgresql.org; Wed, 20 Nov 2024 16:23:01 +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 1tDnTn-007LRx-Vm for pgsql-docs@arkaria.postgresql.org; Wed, 20 Nov 2024 16:22:59 +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 1tDnTn-007LRo-N9 for pgsql-docs@lists.postgresql.org; Wed, 20 Nov 2024 16:22:59 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tDnTh-002u9F-3l for pgsql-docs@lists.postgresql.org; Wed, 20 Nov 2024 16:22:58 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:To:From:Date:Sender:Reply-To:Cc: Content-ID:Content-Description; bh=SMqj+GR4cbfk+Uim9AHKcs2H6W1cNWxmeii/mNNSbNs=; b=PB2VVFeT+SeS6Oa6dIUxYs21FF bX/y4RfBVGorHxNmtncSfy4pNk+IKggSj4l2KBYP5rrnAMs7JnEn8Vgw3NPe78GyDMWkiy97qGXlh 9zVhO5SFpVaTicPov2EY0KJ6aRqZjJbze/4hxV1GlD0ipluAEElCThM8kNl8oNDiZ5IHF6QoM4BMA ur1onrZs2KtDGweQ+cAr2elsz+UlaBfPjPy3/V6SKKnd2lLLCP+ztfZaCbue7LIjMAsufYUX1mAaZ n+/ivXHvCdwnkA2dUADiDYpPK5PxW8vGalJlGGsvYnm+YofV+Ds2wsVrh2v+rDdmp+K+dytUWEPkE MIY9qpnw==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1tDnTf-00EWta-0T; Wed, 20 Nov 2024 11:22:51 -0500 Date: Wed, 20 Nov 2024 11:22:51 -0500 From: Bruce Momjian To: christophe.courtois@dalibo.com, pgsql-docs@lists.postgresql.org Subject: Re: wal_compression = on: what is the algorithm? Message-ID: References: <173168465965.1547981.1990746268682320616@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <173168465965.1547981.1990746268682320616@wrigleys.postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Nov 15, 2024 at 03:30:59PM +0000, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/runtime-config-wal.html > Description: > > In > https://www.postgresql.org/docs/16/runtime-config-wal.html#GUC-WAL-COMPRESSION, > the option "on" is not described: > > “The supported methods are pglz, lz4 (if PostgreSQL was compiled with > --with-lz4) and zstd (if PostgreSQL was compiled with --with-zstd). The > default value is off. ” > > "on" was an available option before PG 15, and still seen in some docs. > If I understand the code in src/backend/utils/misc/guc_tables.c, "on" is the > same as "pglz". So I suggest: > > “The supported methods are pglz, lz4 (if PostgreSQL was compiled with > --with-lz4) and zstd (if PostgreSQL was compiled with --with-zstd). The > default value is off. The value on is synonym of pglz.” I think we kept 'on' just for backward compatibility, so we don't mention it in the docs anymore. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com When a patient asks the doctor, "Am I going to die?", he means "Am I going to die soon?"