Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jgDkD-0000Sc-It for pgsql-docs@arkaria.postgresql.org; Tue, 02 Jun 2020 20:42:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jgDkC-0002Pg-Gw for pgsql-docs@arkaria.postgresql.org; Tue, 02 Jun 2020 20:42:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jgDja-0008Qn-6P for pgsql-docs@lists.postgresql.org; Tue, 02 Jun 2020 20:42:06 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jgDjX-0008GO-DA for pgsql-docs@lists.postgresql.org; Tue, 02 Jun 2020 20:42:05 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.postgrespro.ru (Postfix) with ESMTP id DC4FD21C6C2D; Tue, 2 Jun 2020 23:42:01 +0300 (MSK) X-Virus-Scanned: Debian amavisd-new at postgrespro.ru X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=x tagged_above=-99 required=4 WHITELISTED tests=[] autolearn=unavailable Received: from [10.0.1.13] (unknown [188.123.231.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mail.postgrespro.ru (Postfix) with ESMTPSA id A36D121C6C2B; Tue, 2 Jun 2020 23:42:01 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1591130521; bh=Y3Z/b8YocmB1/s5apJJgXHLmTK3tRN4UydckyyejiUg=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=JZuibkrhuxFYIhDU02seAoQbVDY5YUzJ7iHBhWN/f1PZr9NkNbwZUHh8KwyZHc984 Pj/oa6wsg8hXgOxYyHV23JfWIjNxuyYLDOx0Gk9oYRM6OKzw6fBWeDhCk+ewFj/PyZ 2s12xtWCe1Uky7EhjDjn4W/6sS6Ew4ovvm9qyYEk= Subject: Re: max_wal_size To: Bruce Momjian Cc: "David G. Johnston" , pluzanov@postgrespro.ru, pgsql-docs@lists.postgresql.org References: <159057129673.7025.17016799863173731176@wrigleys.postgresql.org> <92491c6d07a3216ef2caee8ef55c02b5@postgrespro.ru> <8aac88e2a22cd84e50ee1a2bcf3da9b7@postgrespro.ru> <20200602193547.GA26240@momjian.us> From: Pavel Luzanov Message-ID: <26906a54-d7cb-2f8e-eed7-e31660024694@postgrespro.ru> Date: Tue, 2 Jun 2020 23:42:01 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200602193547.GA26240@momjian.us> Content-Type: multipart/mixed; boundary="------------1255E948D8BFE28B6FA31ABB" Content-Language: ru-RU List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------1255E948D8BFE28B6FA31ABB Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello, On 02.06.2020 22:35, Bruce Momjian wrote: > On Thu, May 28, 2020 at 12:21:14PM +0300, p.luzanov@postgrespro.ru wrote: >> WAL |-----------|-----+-----|-----+-----|-----+-----> >> >> a b c >> CP +-----+ +-----+ +-----+ >> b e b e b e >> >> Checkpointer process for point A starts at a(b) and ends at a(e). >> At the end of the work, CP makes a WAL record(plus symbol on WAL line). >> >> Back to the max_wal_size description: >> "Maximum size to let the WAL grow to between automatic WAL checkpoints." >> >> As I understand now, this is true when we talk about the checkpoint as a >> process. >> "Maximum size to let the WAL grow to between a(b) and b(e), between b(b) and c >> (e), etc". > What if we say: > > "Maximum size to let the WAL grow during automatic WAL checkpoints." > > That highlights the "process" part. > Really, "during" is associated with the process, while "between" with points. If there is no objection, simpe patch attached. ----- Pavel Luzanov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company --------------1255E948D8BFE28B6FA31ABB Content-Type: text/x-patch; charset=UTF-8; name="docs_max_wal_size.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="docs_max_wal_size.patch" diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 4eef970d41..7398806203 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -3085,7 +3085,7 @@ include_dir 'conf.d' - Maximum size to let the WAL grow to between automatic WAL + Maximum size to let the WAL grow during automatic WAL checkpoints. This is a soft limit; WAL size can exceed max_wal_size under special circumstances, such as heavy load, a failing archive_command, or a high --------------1255E948D8BFE28B6FA31ABB--