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 1jeebL-0000xE-Pc for pgsql-docs@arkaria.postgresql.org; Fri, 29 May 2020 12:59:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jeebK-0002ZY-Mn for pgsql-docs@arkaria.postgresql.org; Fri, 29 May 2020 12:59:06 +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 1jeebK-0002ZR-D9 for pgsql-docs@lists.postgresql.org; Fri, 29 May 2020 12:59:06 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jeebH-0006AY-I7 for pgsql-docs@lists.postgresql.org; Fri, 29 May 2020 12:59:06 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.postgrespro.ru (Postfix) with ESMTP id 6C95E21C6AE0; Fri, 29 May 2020 15:59:02 +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 mail.postgrespro.ru (unknown [93.174.131.138]) (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 3AAB921C6ADF; Fri, 29 May 2020 15:59:02 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1590757142; bh=QEtawNX6YpiYRuU4YuZ0dO8Ldin7Y8P2fmI6Vrisd0w=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=g8ecuHLdVYCOnFPzXjI26cDuUKGlDkAregEI496BuSIEPGj9Pum+dmbH27eut/YmY S5H1Nq65lzrwYxPQiN2PURAxj/aLK6bGNeHXyybXGOPb7cH9p9ibsF/vOhqNRlKaRQ RY44so0TUWCDRLTNj+Mh9smiCIKulTg+qeH3aBTQ= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 29 May 2020 15:59:02 +0300 From: p.luzanov@postgrespro.ru To: "David G. Johnston" Cc: pluzanov@postgrespro.ru, pgsql-docs@lists.postgresql.org Subject: Re: max_wal_size In-Reply-To: References: <159057129673.7025.17016799863173731176@wrigleys.postgresql.org> <92491c6d07a3216ef2caee8ef55c02b5@postgrespro.ru> <8aac88e2a22cd84e50ee1a2bcf3da9b7@postgrespro.ru> User-Agent: Roundcube Webmail/1.4.0 Message-ID: <845b6836d5712d76f970333f19dc3c6a@postgrespro.ru> X-Sender: p.luzanov@postgrespro.ru List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk David, > I don't know whether a change along those lines to the configuration > reference page is useful or not - I wouldn't make one without a > comprehensive re-read of the actual background/learning section of the > documentation. My gut instinct is that I just don't think the > documentation can do this situation justice and that, as illustrated > by this thread, there are better resources available for these less > common situations. Hm, After some cool down period, I looked with a fresh look. I'm sure there is no need to make changes to the configuration reference page. And I'm not sure that there is a need to make changes to the main section. In any case, it was interesting discussion. Thank you. ----- Pavel Luzanov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company