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

5.4.1 execute select * from xx where id in (1,2,3,4,5,6,7……15000); when in 10000+ postgresql occurs error mysql ok #29672

Open
Keanhua opened this issue Jan 8, 2024 · 1 comment
Labels

Comments

@Keanhua
Copy link

Keanhua commented Jan 8, 2024

Bug Report

For English only, other languages will not accept.

Before report a bug, make sure you have:

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Which version of ShardingSphere did you use?

5.4.1

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

ShardingSphere-JDBC

Expected behavior

query the correct result

Actual behavior

occurs error
image

Reason analyze (If you can)

image

image

every the ExprListContext have the same children

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

select * from xx where id in (1,2,3,4,5,6,7……15000);

Example codes for reproduce this issue (such as a github link).

@Keanhua Keanhua changed the title postgresql in 10000+ occurs error postgresql 5.4.1 execute select * from xx where id in (1,2,3,4,5,6,7……15000); when in 10000+ occurs error Jan 12, 2024
@Keanhua Keanhua changed the title postgresql 5.4.1 execute select * from xx where id in (1,2,3,4,5,6,7……15000); when in 10000+ occurs error 5.4.1 execute select * from xx where id in (1,2,3,4,5,6,7……15000); when in 10000+ postgresql occurs error mysql ok Jan 31, 2024
Copy link

github-actions bot commented Mar 1, 2024

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.

@github-actions github-actions bot added the stale label Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant