You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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: