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.

Sign up for GitHub

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

Jump to bottom

unknownplan in execution plan for insert query #49271

Open
Tracked by #55861
shaoxiqian opened this issue Dec 8, 2023 · 1 comment
Open
Tracked by #55861

unknownplan in execution plan for insert query #49271

shaoxiqian opened this issue Dec 8, 2023 · 1 comment
Assignees
@YangKeao
Labels
may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 may-affects-8.1 severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@shaoxiqian
Copy link
Contributor

Bug Report

image

1. Minimal reproduce step (Required)

workload:web3bench

2. What did you expect to see? (Required)

correct execution plan

4. What is your TiDB version? (Required)

v7.5.0
@shaoxiqian shaoxiqian added the type/bug The issue is confirmed as a bug. label Dec 8, 2023
@jebter jebter added the sig/planner SIG: Planner label Dec 8, 2023
@YangKeao YangKeao self-assigned this Sep 24, 2024
@YangKeao YangKeao mentioned this issue Sep 24, 2024
Open
15 tasks
@YangKeao
Copy link
Member

I don't think it's a bug of TiDB itself. If a plan (with foreign key check) is decoded on a TiDB with lower version, it may produce UnknownPlanID. Let me check how it happens and whether it's reproducible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@YangKeao YangKeao

Labels
may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 may-affects-8.1 severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jebter @YangKeao @shaoxiqian