From: Bruce Momjian <bruce@momjian.us>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Jonathan S. Katz <jkatz@postgresql.org>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: Melanie Plageman <melanieplageman@gmail.com>
Subject: Re: PG 16 draft release notes ready
Date: Mon, 29 May 2023 14:46:22 -0400
Message-ID: <ZHTy/sYjUlTiwrnB@momjian.us> (raw)
In-Reply-To: <CAApHDvo5tiqiWkTF6yTcEbe6-uXq5YVevq=cP0pTEa8Q_B6TAQ@mail.gmail.com>
References: <ZGaPa7M3gc2THeDJ@momjian.us>
<2fd2cc0e-df39-3e77-8fcf-35aad5796b0a@postgresql.org>
<CAApHDvph4djrP+zjOK67VcgbB_p9Zn8QoO7Qctt4oQgUC_ejEw@mail.gmail.com>
<ZG2KdmzCRTluyQS9@momjian.us>
<CAApHDvo5tiqiWkTF6yTcEbe6-uXq5YVevq=cP0pTEa8Q_B6TAQ@mail.gmail.com>
On Wed, May 24, 2023 at 04:13:14PM +1200, David Rowley wrote:
> On Wed, 24 May 2023 at 15:54, Bruce Momjian <bruce@momjian.us> 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 <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-hackers@postgresql.org
Cc: bruce@momjian.us, dgrowleyml@gmail.com, jkatz@postgresql.org, thomas.munro@gmail.com, melanieplageman@gmail.com
Subject: Re: PG 16 draft release notes ready
In-Reply-To: <ZHTy/sYjUlTiwrnB@momjian.us>
References: <ZGaPa7M3gc2THeDJ@momjian.us> <2fd2cc0e-df39-3e77-8fcf-35aad5796b0a@postgresql.org> <CAApHDvph4djrP+zjOK67VcgbB_p9Zn8QoO7Qctt4oQgUC_ejEw@mail.gmail.com> <ZG2KdmzCRTluyQS9@momjian.us> <CAApHDvo5tiqiWkTF6yTcEbe6-uXq5YVevq=cP0pTEa8Q_B6TAQ@mail.gmail.com> <ZHTy/sYjUlTiwrnB@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox