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

Implement an efficient and low space ratio log file structure meta(key range and timestamp). #30099

Open
Tracked by #29501
3pointer opened this issue Nov 24, 2021 · 2 comments
Open
Tracked by #29501

Implement an efficient and low space ratio log file structure meta(key range and timestamp). #30099

3pointer opened this issue Nov 24, 2021 · 2 comments
Labels
type/enhancement The issue or PR belongs to an enhancement.

Comments

@3pointer
Copy link
Contributor

3pointer commented Nov 24, 2021 •
edited
Loading

According to Meta structure
we have several keys for each table.

  1. DB key
  2. Table key
  3. AutoTableID key
  4. AutoRandom key
  5. Sequence/Sequence cycle key
  6. Policy key (ignore?)
  7. DDL history key (ignore?)

we need to avoid to record frequency change key (AutoTableID/AutoRandom).
@3pointer 3pointer mentioned this issue Nov 24, 2021
Closed
41 tasks
@3pointer
Copy link
Contributor Author

I think we can ignore AutoTableID/AutoRandom/Sequence/Sequence cycle key. Let tidb re-allocate these key after restoration. @kennytm WDYT?

@mjonss
Copy link
Contributor

mjonss commented Dec 1, 2021

/type enhancement

@ti-chi-bot ti-chi-bot added the type/enhancement The issue or PR belongs to an enhancement. label Dec 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mjonss @3pointer @ti-chi-bot