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 1kej2b-0002x0-4k for pgsql-docs@arkaria.postgresql.org; Mon, 16 Nov 2020 18:15:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kej2T-0001fz-Bx for pgsql-docs@arkaria.postgresql.org; Mon, 16 Nov 2020 18:15:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kej0z-0007so-Sf for pgsql-docs@lists.postgresql.org; Mon, 16 Nov 2020 18:14:09 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kej0x-0004rc-GC for pgsql-docs@lists.postgresql.org; Mon, 16 Nov 2020 18:14:08 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1kej0v-00068V-Th; Mon, 16 Nov 2020 13:14:05 -0500 Date: Mon, 16 Nov 2020 13:14:05 -0500 From: Bruce Momjian To: Chris Wilson Cc: Thomas Munro , Pg Docs Subject: Re: What does "[backends] should seldom or never need to wait for a write to occur" mean? Message-ID: <20201116181405.GE22426@momjian.us> References: <20201110013632.GA8789@momjian.us> <20201110160801.GA25651@momjian.us> <20201111232417.GH25840@momjian.us> <20201112165412.GC25584@momjian.us> <20201112173730.GF25584@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20201112173730.GF25584@momjian.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, Nov 12, 2020 at 12:37:30PM -0500, Bruce Momjian wrote: > On Thu, Nov 12, 2020 at 05:25:30PM +0000, Chris Wilson wrote: > > Hi Bruce, > > > > Thanks, I absolutely agree that this documentation needs to explain properly > > how the bgwriter works. Your latest patch looks good, it significantly improves > > this section of the manual. I would just suggest changing "non-dirty" to > > "clean" in "When the number of non-dirty shared buffers appears to be > > insufficient", as this makes the language simpler and avoids introducing > > another new term (non-dirty, which means the same as clean). > > OK, done. I wasn't sure 'clean' would be assumed to be non-dirty, but you > are right the language is clearer with 'clean'. (I was afraid 'clean' > would be assumed to be 'empty'.) Patch applied to all supported versions. -- Bruce Momjian https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee