NJrslv commented on code in PR #1481:
URL: https://github.com/apache/cloudberry/pull/1481#discussion_r2602846488
##########
src/test/regress/expected/gporca_faults_optimizer.out:
##########
@@ -31,13 +31,13 @@ $$ LANGUAGE plpgsql VOLATILE;
-- Query that runs the function on an additional non-QD master slice
-- Include the EXPLAIN to ensure that this happens in the plan.
EXPLAIN SELECT * FROM func1_nosql_vol(5), foo;
- QUERY PLAN
--------------------------------------------------------------------------------------------------
- Gather Motion 3:1 (slice1; segments: 3)
(cost=10000000000.25..10000000001.34 rows=3 width=12)
- -> Nested Loop (cost=10000000000.25..10000000001.30 rows=1 width=12)
+ QUERY PLAN
+-----------------------------------------------------------------------------------------------------
+ Gather Motion 3:1 (slice1; segments: 3)
(cost=10000000000.25..10000001756.28 rows=86100 width=12)
Review Comment:
I ran this single test to generate `.out`:
```bash
src/test/regress/pg_regress --dbname=regression
--load-extension=gp_inject_fault gporca_faults
```
The `foo` table isn’t analyzed in this case, so it produces this cost and #
of rows (analyzing `foo` after creation doesn’t change the row count and costs).
I think the `.out` file was generated during a full regress run, where some
previous test turned something on that triggered analyze during table creation.
Not a big deal?
--
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]
