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

sql: validate row level ttl schedule for insights tables #108911

Conversation

koorosh
Copy link
Collaborator

@koorosh koorosh commented Aug 17, 2023

This change adds permanent migration to validate and schedule job for
row level TTL for system.txn_exec_insights and system.stmt_exec_insights
tables. It is necessary because RowLevelTTL for those system tables
defined as part of descriptors and isn't started.

Release note (sql change): ensure that row level TTL schedule is
valid and active for system.txn_exec_insights and system.stmt_exec_insights
tables.

Epic: None

Related to: #104582

Created on top of #104714 PR, only last commit should be reviewed.

This change adds two new system tables to store statements and
transaction execution insights.

Before, this data was kept in memory only and tracked limited
number of latest insights. These tables will be used to persist
this data periodically.

Tables allow to store the same information as in memory store without
aggregation.

Tables implement Row level TTL to delete old records.

Release note (sql change): added new system.txn_exec_insights and
stmt_exec_insights tables to persist execution insights.
This change adds permanent migration to validate and schedule job for
row level TTL for system.txn_exec_insights and system.stmt_exec_insights
tables. It is necessary because RowLevelTTL for those system tables
defined as part of descriptors and isn't started.

Release note (sql change): ensure that row level TTL schedule is
valid and active for system.txn_exec_insights and system.stmt_exec_insights
tables.
@koorosh koorosh requested review from a team as code owners August 17, 2023 15:14
@koorosh koorosh requested review from lidorcarmel and cucaroach and removed request for a team August 17, 2023 15:14
@blathers-crl
Copy link

blathers-crl bot commented Aug 17, 2023

Thank you for contributing to CockroachDB. Please ensure you have followed the guidelines for creating a PR.

Before a member of our team reviews your PR, I have some potential action items for you:

  • We notice you have more than one commit in your PR. We try break logical changes into separate commits, but commits such as "fix typo" or "address review commits" should be squashed into one commit and pushed with --force
  • Please ensure your git commit message contains a release note.
  • When CI has completed, please ensure no errors have appeared.

I have added a few people who may be able to assist in reviewing:

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

@blathers-crl blathers-crl bot added O-community Originated from the community X-blathers-triaged blathers was able to find an owner labels Aug 17, 2023
@blathers-crl blathers-crl bot requested a review from j82w August 17, 2023 15:14
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@koorosh koorosh marked this pull request as draft August 18, 2023 12:48
@koorosh
Copy link
Collaborator Author

koorosh commented Oct 12, 2023

Closed as it is not valid implementation anymore.

@koorosh koorosh closed this Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O-community Originated from the community X-blathers-triaged blathers was able to find an owner
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants