apache / apache/cloudberry

No plan has been computed for required properties

Open
#183 2 comments 1 reaction 0 assignees View on GitHub
type: Bug
Dominant language
C
Stars
1.4k
Forks
247
Avg merge
4d 3h
Merged PRs (30d)
39

Description

### Cloudberry Database version

warehouse=# select version();
version

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------
PostgreSQL 14.4 (Cloudberry Database 1.4.0 build commit:e83e3ffc22d538deb2dbceeeae0138ca2de064e6) on x86_64-pc-linux-gnu, compiled by gcc (GCC) 10.2.1 20210130 (Red Hat 10.2.1-11), 64-b
it compiled on Aug 3 2023 10:15:47
(1 row)

### What happened

```
2023-09-01 05:12:12.984031 CST,"54430",2023-09-01 05:08:39 CST,0,con144997,cmd157,seg-1,,,,sx1,"LOG","00000","2023-09-01 05:12:12:970795 CST,THD000,ERROR,""No plan has been computed for required properties"",
2023-09-01 05:12:12:983885 CST,THD000,ERROR,""No plan has been computed for required properties"",
",,,,,,"INSERT INTO

2023-09-01 05:12:51.507950 CST,",2023-09-01 05:08:39 CST,0,con144997,cmd157,seg-1,,,,sx1,"ERROR","XX000","Canceling query because of high VMEM usage. Used: 18330MB, available 2046MB, red zone: 18432MB (runaway_cleaner.c:200)",,,,,,"
INSERT INTO

```

From the log we can find that cbdb orca failed to generate a plan: No plan has been computed for required properties
the query then fallback to pg optimizer and then it failed due to error: high VMEM usage.

### What you think should happen instead

_No response_

### How to reproduce

run the query with setting: set optimizer = off;

### Operating System

Centos 7.9

### Anything else

_No response_

### Are you willing to submit PR?

- [ ] Yes, I am willing to submit a PR!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://cloudberrydb.org/community/coc).

Contributor guide

Open the contributing guide

Research direction

Reproduce the INSERT INTO workload on Cloudberry Database 1.4.0 with optimizer off, then compare the ORCA planning error and VMEM fallback in the log. The issue provides no complete query, files, tests, or expected behavior, so first obtain a complete reproducer and define what successful planning should look like.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql, sql
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.