[Bug]: since 2.12.0, user-defined actions are too verbose #6161
Comments
|
I recommend changing from My I don't want to have to change it.
|
|
This is added as part of the enhancement request #5876 |
Hi @jflambert! This is a reasonable request. Since it is necessary to be able to debug background workers (a notoriously difficult area to debug) we probably need to add a GUC to be able to tweak the log level of the jobs and the scheduler without having to restart the server. |
|
@mkindahl any chance this could be in 2.12.1, I see it's being worked on otherwise I will have to rollback to 2.11.2, this is too annoying |
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). Fixes timescale#6161
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). It also adds some additional job progress messages at debug level. Fixes timescale#6161
mkindahl
added
bgw
@jflambert Sorry, but it is not likely to be in 2.12.1: the release is already cut. It will be available in the release after that. |
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). It also adds some additional job progress messages at debug level. Fixes timescale#6161
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). It also adds some additional job progress messages at debug level. Fixes timescale#6161
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). It also adds some additional job progress messages at debug level. Fixes timescale#6161
|
OK @mkindahl I'll wait patiently for the fix, since I see you already have a PR for it. Thank you. Forgive my ignorance, but will I (as an enduser) have to do anything in my deployments? |
No, I don't think so. I am lowering the log level of the offending message and adding support for setting this for the background workers, but the default is the same as for |
|
This will also take care of retention policy jobs right?
|
It should be all policies. The printout was for all jobs and that is changed to DEBUG1 instead of LOG. |
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). It also adds some additional job progress messages at debug level. Fixes timescale#6161
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). It also adds some additional job progress messages at debug level. Fixes timescale#6161
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). It also adds some additional job progress messages at debug level. Fixes timescale#6161
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). It also adds some additional job progress messages at debug level. Fixes timescale#6161
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). It also adds some additional job progress messages at debug level. Fixes timescale#6161
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). It also adds some additional job progress messages at debug level. Fixes timescale#6161
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). It also adds some additional job progress messages at debug level. Fixes timescale#6161
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). It also adds some additional job progress messages at debug level. Fixes #6161
|
@mkindahl I see 2.12.2 is out today but my issue is not part of the release notes?
|
|
@jflambert The above was an unplanned fast-tracked release with minimal changes. This fix will be out with the next minor release 2.13. |
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). It also adds some additional job progress messages at debug level. Fixes timescale#6161
To avoid having to spam the log with unecessary background worker progress messages a GUC for controlling the background worker log level is introduced. This can be set using `ALTER SYSTEM` plus a call of `pg_reload_conf()` and will set the `log_min_messages` for the background workers only (scheduler and all job runners). It also adds some additional job progress messages at debug level. Fixes timescale#6161
|
Hi @mkindahl can confirm v2.13.0 fixes my logging issues. thanks. |
Thanks for confirming @jflambert ! |
|
Hi @mkindahl looks like I still get some logging for retention policy jobs in 2.13.1
|
Thanks @jflambert , will look into it. |
What type of bug is this?
Other
What subsystems and features are affected?
Background worker
What happened?
It's minor, but I notice since upgrading to 2.12.0 I have way too many logs from timescaledb
Yes we do have a job every 5 seconds. No I don't need to see it being logged so much!
This wasn't a "problem" prior to 2.12.0
TimescaleDB version affected
2.12.0
PostgreSQL version used
13.12
What operating system did you use?
alpine 3.18
What installation method did you use?
Docker
What platform did you run on?
On prem/Self-hosted
Relevant log output and stack trace
How can we reproduce the bug?
create a user job, have it run every 5 seconds, notice overwhelming output in pg logsThe text was updated successfully, but these errors were encountered: