lightning: add PK to internal tables

[lance6716]

What problem does this PR solve?

Issue Number: close #57479

Problem Summary:

What changed and how does it work?

as title

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @lance6716. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[lance6716]

/check-issue-triage-complete

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.6201%. Comparing base (fe1b9ed) to head (c004c4d).
Report is 81 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #57480        +/-   ##
================================================
+ Coverage   72.8112%   73.6201%   +0.8088%     
================================================
  Files          1676       1706        +30     
  Lines        463677     471772      +8095     
================================================
+ Hits         337609     347319      +9710     
+ Misses       105228     102962      -2266     
- Partials      20840      21491       +651     

Flag	Coverage Δ
integration	46.2491% <ø> (?)
unit	72.1908% <ø> (-0.0212%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.7673% <ø> (ø)
parser	∅ <ø> (∅)
br	45.4348% <ø> (-0.0242%)	⬇️

[lance6716]

/retest

[tiprow]

@lance6716: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Benjamin2037]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-11-21 04:16:08.56477882 +0000 UTC m=+91556.184433335: ☑️ agreed by D3Hunter.
• 2024-11-21 04:29:47.02455105 +0000 UTC m=+92374.644205567: ☑️ agreed by Benjamin2037.

[lance6716]

/assign @yudongusa

[ti-chi-bot]

@lance6716: GitHub didn't allow me to assign the following users: yudongusa.

Note that only pingcap members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @yudongusa

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[lance6716]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Benjamin2037, D3Hunter, lance6716, yudongusa

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• lightning/OWNERS [Benjamin2037,D3Hunter,lance6716,yudongusa]
• pkg/lightning/OWNERS [Benjamin2037,D3Hunter,lance6716]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.5: #57932.