-
Notifications
You must be signed in to change notification settings - Fork 885
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
Reduce Log Level for Compress Chunk #7280
Labels
enhancement
An enhancement to an existing feature for functionality
Comments
gmilamjr
added
the
enhancement
An enhancement to an existing feature for functionality
label
Sep 18, 2024
On 2.15.2 I am seeing massive amounts of these log entries when compressing chunks:
I don't believe this was happening in previous versions. |
Here's an example of a complete call to
|
svenklemm
added a commit
to svenklemm/timescaledb
that referenced
this issue
Oct 9, 2024
Don't use LOG log level when printing out non-actionable progress information regarding compression. Fixes timescale#7280
svenklemm
added a commit
to svenklemm/timescaledb
that referenced
this issue
Oct 9, 2024
Don't use LOG log level when printing out non-actionable progress information regarding compression. Fixes timescale#7280
svenklemm
added a commit
to svenklemm/timescaledb
that referenced
this issue
Oct 9, 2024
Don't use LOG log level when printing out non-actionable progress information regarding compression. Fixes timescale#7280
svenklemm
added a commit
to svenklemm/timescaledb
that referenced
this issue
Oct 9, 2024
Don't use LOG log level when printing out non-actionable progress information regarding compression. Fixes timescale#7280
svenklemm
added a commit
to svenklemm/timescaledb
that referenced
this issue
Oct 9, 2024
Don't use LOG log level when printing out non-actionable progress information regarding compression. Fixes timescale#7280
svenklemm
added a commit
that referenced
this issue
Oct 9, 2024
Don't use LOG log level when printing out non-actionable progress information regarding compression. Fixes #7280
antekresic
added
force-auto-backport
Automatically backport this PR or fix of this issue, even if it's not marked as "bug"
and removed
force-auto-backport
Automatically backport this PR or fix of this issue, even if it's not marked as "bug"
labels
Oct 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What type of enhancement is this?
Other
What subsystems and features will be improved?
Other
What does the enhancement do?
Reduce the log volume generated by the compress_chunk function. Currently, we have a maintenance job that processes existing chunks and calls the compress_chunk function as needed. This operation produces a significant amount of output in the PostgreSQL server log at the current LOG level, leading to excessive log volume. Would it make sense to lower the log level from LOG to INFO? Otherwise, suppressing the output would require setting the log_min_messages to FATAL.
Implementation challenges
No response
The text was updated successfully, but these errors were encountered: