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 1qlHjZ-0026dc-T6 for pgsql-hackers@arkaria.postgresql.org; Tue, 26 Sep 2023 23:44:53 +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 1qlHjX-00GHKc-Hy for pgsql-hackers@arkaria.postgresql.org; Tue, 26 Sep 2023 23:44:51 +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 1qlHjX-00GHKM-7P for pgsql-hackers@lists.postgresql.org; Tue, 26 Sep 2023 23:44:51 +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 1qlHjU-006pL4-AB for pgsql-hackers@postgresql.org; Tue, 26 Sep 2023 23:44:49 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2023062407; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=XAMfy7IOUu0lafosAjGsbF2i89dHYxeabdd3eOoB3Vc=; b=ZxLNr SeyHvXCbeIOh0UixE+dJ28cMgwxQsU8cFPY8xyMondgrfDGbWkquNzBNHh4uF/TW6ZCaZnzwbBBWW 4xyB3vZVrPwKXzOVlotHET5Cfjrh/yGAPccyTMBAT8i0poS4XkQkx2uVHlkV0DoujbPMaxVa+iuxX AW+ns8/nrt6TUEA4sa/OVyNxCSxWDcNqIgdPeKOHLprs9P9XaX+EQ84m3wYswZu/9bGO7MuD/CiHX 1tFvaal/6uZ3sTsCzGx2AlZCshiVndGM3OOVkjd/xAf/gefJtfDXNForIYioyuGtCPVNhb5ImAxBi 9UvWP8KpjJYRVEHveLx1dIy/lqoTA==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1qlHjQ-002y9Q-0K; Tue, 26 Sep 2023 19:44:44 -0400 Date: Tue, 26 Sep 2023 19:44:44 -0400 From: Bruce Momjian To: David Rowley Cc: "Imseih (AWS), Sami" , Tom Lane , Peter Eisentraut , "pgsql-hackers@postgresql.org" Subject: Re: Correct the documentation for work_mem Message-ID: References: <66590882-F48C-4A25-83E3-73792CF8C51F@amazon.com> <3363505.1682097301@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Sep 27, 2023 at 02:05:44AM +1300, David Rowley wrote: > On Tue, 12 Sept 2023 at 03:03, Bruce Momjian wrote: > > > > On Mon, Sep 11, 2023 at 10:02:55PM +1200, David Rowley wrote: > > > It's certainly not a show-stopper. I do believe the patch makes some > > > improvements. The reason I'd prefer to see either "and" or "and/or" > > > in place of "or" is because the text is trying to imply that many of > > > these operations can run at the same time. I'm struggling to > > > understand why, given that there could be many sorts and many hashes > > > going on at once that we'd claim it could only be one *or* the other. > > > If we have 12 sorts and 4 hashes then that's not "several sort or hash > > > operations", it's "several sort and hash operations". Of course, it > > > could just be sorts or just hashes, so "and/or" works fine for that. > > > > Yes, I see your point and went with "and", updated patch attached. > > Looks good to me. Patch applied back to Postgres 11. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.