Re: Asymmetric partition-wise JOIN

From: Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>
To: Zhihong Yu <zyu(at)yugabyte(dot)com>
Cc: Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Kohei KaiGai <kaigai(at)heterodb(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Asymmetric partition-wise JOIN
Date: 2021-07-06 09:28:05
Message-ID: 33b92be7-67ca-ac4a-35be-48a673d74dd9@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 5/7/21 23:15, Zhihong Yu wrote:
> On Mon, Jul 5, 2021 at 2:57 AM Andrey Lepikhov
> <a(dot)lepikhov(at)postgrespro(dot)ru <mailto:a(dot)lepikhov(at)postgrespro(dot)ru>> wrote:
> +            * Can't imagine situation when join relation already
> exists. But in
> +            * the 'partition_join' regression test it happens.
> +            * It may be an indicator of possible problems.
> Should a log be added in the above case ?
I made additional analysis of this branch of code. This situation can
happen in the case of one child or if we join two plane tables with
partitioned. Both situations are legal and I think we don't needed to
add any log message here.
Other mistakes were fixed.

--
regards,
Andrey Lepikhov
Postgres Professional

Attachment Content-Type Size
v16-0001-Asymmetric-partitionwise-join.patch text/plain 33.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2021-07-06 09:30:53 Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints
Previous Message David Rowley 2021-07-06 09:20:10 Re: [PATCH] expand the units that pg_size_pretty supports on output