Cleanup bgw_job_stat_history table #47
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Closing since we're incorporating it in the tsdb extension: timescale/timescaledb#8494 |
kpan2034
added a commit
to kpan2034/timescaledb
that referenced
this pull request
Aug 22, 2025
Previously a delete query was run on the `bgw_job_stat_history` table to remove job history. This could be slow once the job history table became very large. We now use a temporary table to keep recent history and truncate the job history table instead. We also introduce a `job_history_bsearch` function which finds the ids of the jobs that need to be deleted using binary search. This PR is based on experiments done previously (timescale/timescaledb-extras#47).
kpan2034
added a commit
to kpan2034/timescaledb
that referenced
this pull request
Aug 22, 2025
Previously a delete query was run on the `bgw_job_stat_history` table to remove job history. This could be slow once the job history table became very large. We now use a temporary table to keep recent history and truncate the job history table instead. We also introduce a `job_history_bsearch` function which finds the ids of the jobs that need to be deleted using binary search. This PR is based on experiments done previously (timescale/timescaledb-extras#47).
kpan2034
added a commit
to kpan2034/timescaledb
that referenced
this pull request
Aug 25, 2025
Previously a delete query was run on the `bgw_job_stat_history` table to remove job history. This could be slow once the job history table became very large. We now use a temporary table to keep recent history and truncate the job history table instead. We also introduce a `job_history_bsearch` function which finds the ids of the jobs that need to be deleted using binary search. This PR is based on experiments done previously (timescale/timescaledb-extras#47).
kpan2034
added a commit
to kpan2034/timescaledb
that referenced
this pull request
Aug 25, 2025
Previously a delete query was run on the `bgw_job_stat_history` table to remove job history. This could be slow once the job history table became very large. We now use a temporary table to keep recent history and truncate the job history table instead. We also introduce a `job_history_bsearch` function which finds the ids of the jobs that need to be deleted using binary search. This PR is based on experiments done previously (timescale/timescaledb-extras#47).
kpan2034
added a commit
to kpan2034/timescaledb
that referenced
this pull request
Aug 25, 2025
Previously a delete query was run on the `bgw_job_stat_history` table to remove job history. This could be slow once the job history table became very large. We now use a temporary table to keep recent history and truncate the job history table instead. We also introduce a `job_history_bsearch` function which finds the ids of the jobs that need to be deleted using binary search. This PR is based on experiments done previously (timescale/timescaledb-extras#47).
kpan2034
added a commit
to kpan2034/timescaledb
that referenced
this pull request
Aug 25, 2025
Previously a delete query was run on the `bgw_job_stat_history` table to remove job history. This could be slow once the job history table became very large. We now use a temporary table to keep recent history and truncate the job history table instead. We also introduce a `job_history_bsearch` function which finds the ids of the jobs that need to be deleted using binary search. This PR is based on experiments done previously (timescale/timescaledb-extras#47).
kpan2034
added a commit
to kpan2034/timescaledb
that referenced
this pull request
Aug 25, 2025
Previously a delete query was run on the `bgw_job_stat_history` table to remove job history. This could be slow once the job history table became very large. We now use a temporary table to keep recent history and truncate the job history table instead. We also introduce a `job_history_bsearch` function which finds the ids of the jobs that need to be deleted using binary search. This PR is based on experiments done previously (timescale/timescaledb-extras#47).
kpan2034
added a commit
to kpan2034/timescaledb
that referenced
this pull request
Aug 25, 2025
Previously a delete query was run on the `bgw_job_stat_history` table to remove job history. This could be slow once the job history table became very large. We now use a temporary table to keep recent history and truncate the job history table instead. We also introduce a `job_history_bsearch` function which finds the ids of the jobs that need to be deleted using binary search. This PR is based on experiments done previously (timescale/timescaledb-extras#47).
kpan2034
added a commit
to kpan2034/timescaledb
that referenced
this pull request
Aug 26, 2025
Previously a delete query was run on the `bgw_job_stat_history` table to remove job history. This could be slow once the job history table became very large. We now use a temporary table to keep recent history and truncate the job history table instead. We also introduce a `job_history_bsearch` function which finds the ids of the jobs that need to be deleted using binary search. This PR is based on experiments done previously (timescale/timescaledb-extras#47).
kpan2034
added a commit
to kpan2034/timescaledb
that referenced
this pull request
Aug 26, 2025
Previously a delete query was run on the `bgw_job_stat_history` table to remove job history. This could be slow once the job history table became very large. We now use a temporary table to keep recent history and truncate the job history table instead. We also introduce a `job_history_bsearch` function which finds the ids of the jobs that need to be deleted using binary search. This PR is based on experiments done previously (timescale/timescaledb-extras#47).
kpan2034
added a commit
to kpan2034/timescaledb
that referenced
this pull request
Aug 26, 2025
Previously a delete query was run on the `bgw_job_stat_history` table to remove job history. This could be slow once the job history table became very large. We now use a temporary table to keep recent history and truncate the job history table instead. We also introduce a `job_history_bsearch` function which finds the ids of the jobs that need to be deleted using binary search. This PR is based on experiments done previously (timescale/timescaledb-extras#47).
kpan2034
added a commit
to kpan2034/timescaledb
that referenced
this pull request
Aug 26, 2025
Previously a delete query was run on the `bgw_job_stat_history` table to remove job history. This could be slow once the job history table became very large. We now use a temporary table to keep recent history and truncate the job history table instead. We also introduce a `job_history_bsearch` function which finds the ids of the jobs that need to be deleted using binary search. This PR is based on experiments done previously (timescale/timescaledb-extras#47).
kpan2034
added a commit
to timescale/timescaledb
that referenced
this pull request
Aug 26, 2025
Previously a delete query was run on the `bgw_job_stat_history` table to remove job history. This could be slow once the job history table became very large. We now use a temporary table to keep recent history and truncate the job history table instead. We also introduce a `job_history_bsearch` function which finds the ids of the jobs that need to be deleted using binary search. This PR is based on experiments done previously (timescale/timescaledb-extras#47).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.