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

Backport to 2.16.x: #7270: Reset per compressed row memory context during tuple filtering #7277

Merged
merged 1 commit into from
Sep 18, 2024

Conversation

timescale-automation
Copy link

This is an automated backport of #7270: Reset per compressed row memory context during tuple filtering.
This PR will be merged automatically after all the relevant CI checks pass. If this fix should not be backported, or will be backported manually, just close this PR. You can use the backport branch to add your changes, it won't be modified automatically anymore.

For more details, please see the documentation

Original description

Reset per compressed row memory context during tuple filtering

When a batch was skipped due to compression tuple filtering the per compressed row memory context would not be reset leading to memory usage increasing linearly with number of consecutive filtered batches.

When a batch was skipped due to compression tuple filtering the
per compressed row memory context would not be reset leading to
memory usage increasing linearly with number of consecutive filtered
batches.

(cherry picked from commit 460994c)
@timescale-automation timescale-automation added the is-auto-backport PR created by backport automation label Sep 18, 2024
@timescale-automation timescale-automation merged commit bd6354e into 2.16.x Sep 18, 2024
33 of 35 checks passed
@timescale-automation timescale-automation deleted the backport/2.16.x/7270 branch September 18, 2024 11:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is-auto-backport PR created by backport automation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants