reshke commented on code in PR #1895:
URL: https://github.com/apache/cloudberry/pull/1895#discussion_r3798192926


##########
src/test/regress/expected/join_hash.out:
##########
@@ -1289,28 +1289,36 @@ select i8.q2, ss.* from
 int8_tbl i8,
 lateral (select t1.fivethous, i4.f1 from tenk1 t1 join int4_tbl i4
          on t1.fivethous = i4.f1+i8.q2 order by 1,2) ss;
-                                   QUERY PLAN                                  
  
+                                   QUERY PLAN                                  
 
 
---------------------------------------------------------------------------------
- Gather Motion 3:1  (slice1; segments: 3)
-   ->  Nested Loop
-         ->  Broadcast Motion 3:3  (slice2; segments: 3)
-               ->  Seq Scan on int8_tbl i8
-         ->  Materialize
-               ->  Sort
-                     Sort Key: t1.fivethous, i4.f1
-                     ->  Hash Join
-                           Hash Cond: (t1.fivethous = (i4.f1 + i8.q2))
-                           ->  Seq Scan on tenk1 t1
-                           ->  Hash
-                                 ->  Broadcast Motion 3:3  (slice3; segments: 
3)
+ Nested Loop

Review Comment:
   Yep this is intended. The before-plan is better in term of performance, 
expect it is not valid ;). We receive executor-time error becuase of motion 
rescan. The after-fix plan is worse, but can be executed correctly. In fact,  
the sole thing this PR do is correctly use infrastructure committed at 
https://github.com/apache/cloudberry/commit/00e25afe119c



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to