Revert "fix: specialize server-prepared parameter types at execution …

[daviszhen]

What type of PR is this?

• API-change
• BUG
• Improvement
• Documentation
• Feature
• Test and CI
• Code Refactoring

Which issue(s) this PR fixes:

issue #27477

What this PR does / why we need it:

导致回归性能下降 。 reverts commit 0e5db4c.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[aunjgr]

Reviewed exact head b561897. The revert removes the per-COM_STMT_EXECUTE specialization/deep copy, while the independent generic plan-clone fields and tests remain intact (including OnDuplicateAction, SEND/RECV message headers, ScanSnapshot, and CREATE AS SELECT cloning). No blocking issue found.

[XuPeng-SH]

Reviewed exact head b561897.

The new commit closes my prior blocker: the revert is now scoped to the per-COM_STMT_EXECUTE parameter-specialization/deep-copy traversal that caused the TPCC regression, while generic DeepCopyNode/DeepCopyQuery/DeepCopyDataDefinition correctness remains intact. OnDuplicateAction, SEND/RECV headers, snapshots, CTAS execution fields, and independent YEAR literal materialization are retained with ownership-focused tests.

Focused plan, colexec, and frontend prepared-statement tests pass locally, and CI is green. No remaining blocking issue found.

[mergify]

Queued — the merge queue status continues in this comment ↓.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-08-23 12:07 UTC · Rule: main · triggered by @XuPeng-SH with the merge queue checkbox
• 🟠 Checks running · in-place
• 🚫 Left the queue — 2026-08-23 12:08 UTC · at 66f1555b7b18ad31cb6237baed403d858283f467

This pull request spent 1 minute 12 seconds in the queue, with no time running CI.

Waiting for

• any of: [🛡 GitHub branch protection]
  • check-neutral = Matrixone CI / UT Test on Ubuntu/x86
  • check-skipped = Matrixone CI / UT Test on Ubuntu/x86
  • check-success = Matrixone CI / UT Test on Ubuntu/x86
• any of: [🛡 GitHub branch protection]
  • check-neutral = Matrixone CI / SCA Test on Linux/arm64
  • check-skipped = Matrixone CI / SCA Test on Linux/arm64
  • check-success = Matrixone CI / SCA Test on Linux/arm64
• any of: [🛡 GitHub branch protection]
  • check-neutral = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY)
  • check-skipped = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY)
  • check-success = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY)
• any of: [🛡 GitHub branch protection]
  • check-neutral = Matrixone Utils CI / Coverage
  • check-skipped = Matrixone Utils CI / Coverage
  • check-success = Matrixone Utils CI / Coverage
• any of: [🛡 GitHub branch protection]
  • check-neutral = Matrixone UT Coverage / UT Coverage on Ubuntu/x86
  • check-skipped = Matrixone UT Coverage / UT Coverage on Ubuntu/x86
  • check-success = Matrixone UT Coverage / UT Coverage on Ubuntu/x86
• any of: [🛡 GitHub branch protection]
  • check-neutral = Matrixone Standlone CI / multi CN e2e BVT Test on Linux/x64(COMPOSE, PESSIMISTIC)
  • check-skipped = Matrixone Standlone CI / multi CN e2e BVT Test on Linux/x64(COMPOSE, PESSIMISTIC)
  • check-success = Matrixone Standlone CI / multi CN e2e BVT Test on Linux/x64(COMPOSE, PESSIMISTIC)

All conditions

• any of [🛡 GitHub branch protection]:
  • check-neutral = Matrixone CI / UT Test on Ubuntu/x86
  • check-skipped = Matrixone CI / UT Test on Ubuntu/x86
  • check-success = Matrixone CI / UT Test on Ubuntu/x86
• any of [🛡 GitHub branch protection]:
  • check-neutral = Matrixone CI / SCA Test on Linux/arm64
  • check-skipped = Matrixone CI / SCA Test on Linux/arm64
  • check-success = Matrixone CI / SCA Test on Linux/arm64
• any of [🛡 GitHub branch protection]:
  • check-neutral = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY)
  • check-skipped = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY)
  • check-success = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY)
• any of [🛡 GitHub branch protection]:
  • check-neutral = Matrixone Utils CI / Coverage
  • check-skipped = Matrixone Utils CI / Coverage
  • check-success = Matrixone Utils CI / Coverage
• any of [🛡 GitHub branch protection]:
  • check-neutral = Matrixone UT Coverage / UT Coverage on Ubuntu/x86
  • check-skipped = Matrixone UT Coverage / UT Coverage on Ubuntu/x86
  • check-success = Matrixone UT Coverage / UT Coverage on Ubuntu/x86
• any of [🛡 GitHub branch protection]:
  • check-neutral = Matrixone Standlone CI / multi CN e2e BVT Test on Linux/x64(COMPOSE, PESSIMISTIC)
  • check-skipped = Matrixone Standlone CI / multi CN e2e BVT Test on Linux/x64(COMPOSE, PESSIMISTIC)
  • check-success = Matrixone Standlone CI / multi CN e2e BVT Test on Linux/x64(COMPOSE, PESSIMISTIC)
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • Revert "fix: specialize server-prepared parameter types at execution … #27485
• github-review-approved [🛡 GitHub branch protection]
  • Revert "fix: specialize server-prepared parameter types at execution … #27485

Reason

Pull request #27485 has been dequeued

Pull request from fork cannot be queued. This pull request comes from a fork, and Mergify needs the author's permission to update its branch.

The author needs to enable "Allow edits from maintainers" on this pull request.

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Tick the box to put this pull request back in the merge queue (same as @mergifyio queue).

• Requeue this pull request