Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] PG optimizer will core in LASJ_NOTIN case #873

Closed
1 of 2 tasks
jiaqizho opened this issue Jan 15, 2025 · 3 comments
Closed
1 of 2 tasks

[Bug] PG optimizer will core in LASJ_NOTIN case #873

jiaqizho opened this issue Jan 15, 2025 · 3 comments
Labels
type: Bug Something isn't working

Comments

@jiaqizho
Copy link
Contributor

Apache Cloudberry version

Current main branch is 6cec348

What happened

create table t_13722(id int, tt timestamp)
  distributed by (id);
  
set optimizer to off;
select
  t1.*
from
  t_13722 t1
where
  t1.id not in (select id from t_13722 where id != 4)
  and
  t1.tt = (select min(tt) from t_13722 where id = t1.id);

Image

What you think should happen instead

No response

How to reproduce

upper

Operating System

no relatived

Anything else

No response

Are you willing to submit PR?

  • Yes, I am willing to submit a PR!

Code of Conduct

@jiaqizho jiaqizho added the type: Bug Something isn't working label Jan 15, 2025
@jiaqizho jiaqizho changed the title [Bug] PG optimizer will core in LASJ_NOTIN [Bug] PG optimizer will core in LASJ_NOTIN case Jan 15, 2025
@jiaqizho
Copy link
Contributor Author

jiaqizho commented Jan 15, 2025

I am not sure whether this case cause by cherry-pick missing some commits or not...

@yjhjstz
Copy link
Member

yjhjstz commented Jan 15, 2025

pls cherry-pick Possible qual postponing past ANTI-JOIN/LASJ_NOTIN-JOIN..

@yjhjstz
Copy link
Member

yjhjstz commented Jan 20, 2025

fixed by #878

@yjhjstz yjhjstz closed this as completed Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants