Re: First draft of PG 17 release notes - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: First draft of PG 17 release notes
Date
Msg-id ZkQDv9bF4pWnB9JG@momjian.us
Whole thread Raw
In response to Re: First draft of PG 17 release notes  (Andy Fan <zhihuifan1213@163.com>)
List pgsql-hackers
On Tue, May 14, 2024 at 10:32:14AM +0800, Andy Fan wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > It was unclear from the commit message exactly what user-visible
> > optimization this allowed.  Do you have details?
> 
> Yes, It allows the query like "SELECT * FROM t1 WHERE t1.a in (SELECT a
> FROM t2 WHERE t2.b = t1.b)" be pulled up a semi join, hence more join
> methods / join orders are possible.
> 
> 
> Yes, for example:  (subquery-1) UNION ALL (subquery-2) LIMIT n;
> 
> When planning the subquery-1 or subquery-2, limit N should be
> considered. As a consequence, maybe hash join should be replaced with
> Nested Loop. Before this commits, it is ignored if it is flatten into 
> appendrel, and the "flatten" happens very often.
> 
> David provided a summary for the both commits in [1].

Okay, attached patch applied.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.

Attachment

pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: Row pattern recognition
Next
From: Bruce Momjian
Date:
Subject: Re: First draft of PG 17 release notes