Re: Should consider materializing the cheapest inner path in consider_parallel_nestloop()

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: Tender Wang <tndrwang(at)gmail(dot)com>, Tomasz Rybak <tomasz(dot)rybak(at)post(dot)pl>, pgsql-hackers(at)lists(dot)postgresql(dot)org, robertmhaas(at)gmail(dot)com, David Rowley <dgrowleyml(at)gmail(dot)com>, "Fujii(dot)Yuki(at)df(dot)MitsubishiElectric(dot)co(dot)jp" <Fujii(dot)Yuki(at)df(dot)mitsubishielectric(dot)co(dot)jp>
Subject: Re: Should consider materializing the cheapest inner path in consider_parallel_nestloop()
Date: 2024-07-18 08:11:50
Message-ID: CAMbWs48fpP=OU5VLOGBBgvA4kxnPXTCVJh3Qayo1i-K=3Pt4Nw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 18, 2024 at 4:00 PM Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
> Please look at a recent buildfarm failure [1], which shows some
> instability of that test addition:
> -- the joinrel is not parallel-safe due to the OFFSET clause in the subquery
> explain (costs off)
> select * from tenk1 t1, (select * from tenk2 t2 offset 0) t2 where t1.two > t2.two;
> - QUERY PLAN
> --------------------------------------------
> + QUERY PLAN
> +-------------------------------------------------
> Nested Loop
> Join Filter: (t1.two > t2.two)
> - -> Gather
> - Workers Planned: 4
> - -> Parallel Seq Scan on tenk1 t1
> + -> Seq Scan on tenk2 t2
> -> Materialize
> - -> Seq Scan on tenk2 t2
> + -> Gather
> + Workers Planned: 4
> + -> Parallel Seq Scan on tenk1 t1
> (7 rows)

Thank you for the report and investigation. Will have a look.

Thanks
Richard

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2024-07-18 08:12:35 Re: CI, macports, darwin version problems
Previous Message Laurenz Albe 2024-07-18 08:05:34 Re: Built-in CTYPE provider