| From: | Alena Rybakina <lena(dot)ribackina(at)yandex(dot)ru> |
|---|---|
| To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com> |
| Subject: | Re: Support "Right Semi Join" plan shapes |
| Date: | 2024-03-05 20:10:00 |
| Message-ID: | 689d20f8-b08d-4e7c-b554-f61492f22c98@yandex.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
To be honest, I didn't see it in the code, could you tell me where they
are, please?
On 05.03.2024 05:44, Richard Guo wrote:
>
> On Tue, Jan 30, 2024 at 2:51 PM Alena Rybakina
> <lena(dot)ribackina(at)yandex(dot)ru> wrote:
>
> I have reviewed your patch and I think it is better to add an
> Assert for
> JOIN_RIGHT_SEMI to the ExecMergeJoin and ExecNestLoop functions to
> prevent the use of RIGHT_SEMI for these types of connections
> (NestedLoop
> and MergeJoin).
>
>
> Hmm, I don't see why this is necessary. The planner should already
> guarantee that we won't have nestloops/mergejoins with right-semi joins.
>
> Thanks
> Richard
--
Regards,
Alena Rybakina
Postgres Professional:http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2024-03-05 21:22:09 | Re: processes stuck in shutdown following OOM/recovery |
| Previous Message | Matthias van de Meent | 2024-03-05 20:08:08 | Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements |