From: Jonathan S. Katz <jkatz@postgresql.org>
To: David Rowley <dgrowleyml@gmail.com>
To: Bruce Momjian <bruce@momjian.us>
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: Wed, 24 May 2023 12:58:07 -0400
Message-ID: <45e5025c-7f59-7b1b-e685-9de0571e63cf@postgresql.org> (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 5/24/23 12:13 AM, David Rowley wrote:
> On Wed, 24 May 2023 at 15:54, Bruce Momjian <bruce@momjian.us> wrote:
>>
>> On Wed, May 24, 2023 at 08:37:45AM +1200, David Rowley wrote:
>>> On Mon, 22 May 2023 at 07:05, Jonathan S. Katz <jkatz@postgresql.org> wrote:
>>>> * Parallel execution of queries that use `FULL` and `OUTER` joins
>>>
>>> I think this should be `RIGHT` joins rather than `OUTER` joins.
>>>
>>> LEFT joins have been parallelizable I think for a long time now.
>>
>> Well, since we can swap left/right easily, why would we not have just
>> have swappted the tables and done the join in the past? I think there
>> are two things missing in my description.
>>
>> 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".
I made this swap in the release announcement. Thanks!
Jonathan
Attachments:
OpenPGP_signature (application/pgp-signature, 839B) download
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: jkatz@postgresql.org, dgrowleyml@gmail.com, bruce@momjian.us, thomas.munro@gmail.com, melanieplageman@gmail.com
Subject: Re: PG 16 draft release notes ready
In-Reply-To: <45e5025c-7f59-7b1b-e685-9de0571e63cf@postgresql.org>
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> <45e5025c-7f59-7b1b-e685-9de0571e63cf@postgresql.org>
* 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