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 1q3hsy-0003TR-Oz for pgsql-hackers@arkaria.postgresql.org; Mon, 29 May 2023 18:46:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q3hsx-0000Be-EM for pgsql-hackers@arkaria.postgresql.org; Mon, 29 May 2023 18:46:27 +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 1q3hsx-0000BV-5M for pgsql-hackers@lists.postgresql.org; Mon, 29 May 2023 18:46:27 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q3hst-002vDR-OW; Mon, 29 May 2023 18:46:26 +0000 Received: from bruce by momjian.us with local (Exim 4.94.2) (envelope-from ) id 1q3hss-00FME6-Sv; Mon, 29 May 2023 14:46:22 -0400 Date: Mon, 29 May 2023 14:46:22 -0400 From: Bruce Momjian To: David Rowley Cc: "Jonathan S. Katz" , PostgreSQL-development , Thomas Munro , Melanie Plageman Subject: Re: PG 16 draft release notes ready Message-ID: References: <2fd2cc0e-df39-3e77-8fcf-35aad5796b0a@postgresql.org> 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, May 24, 2023 at 04:13:14PM +1200, David Rowley wrote: > On Wed, 24 May 2023 at 15:54, Bruce Momjian wrote: > > First, I need to mention parallel _hash_ join. Second, I think this > > item is saying that the _inner_ side of a parallel hash join can be an > > OUTER or FULL join. How about? > > > > Allow hash joins to be parallelized where the inner side is > > processed as an OUTER or FULL join (Melanie Plageman, Thomas Munro) > > > > In this case, the inner side is the hashed side. > > I think Jonathan's text is safe to swap OUTER to RIGHT as it mentions > "execution". For the release notes, maybe the mention of it can be > moved away from "E.1.3.1.1. Optimizer" and put under "E.1.3.1.2. > General Performance" and ensure we mention that we're talking about > the executor? > > I'm thinking it might be confusing if we claim that this is something > that we switched on in the planner. It was a limitation with the > executor which the planner was just onboard with not producing plans > for. Well, I try to keep plan changes in the optimizer section because that is where the decisions are made, and how people think of plans since EXPLAIN makes them visible. I agree it is an executor change but I think that distinction will be more confusing than helpful. Frankly, almost all the optimizer items are really executor changes. Maybe the "Optimizer" title needs to be changed, but I do think it is good to group plan changes together. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.