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
With a new feature allowing to schedule jobs with second granularity, job_run_details is clogged very-very fast rendering it practically useless, especially if you do want to keep log run details for your critical jobs and discard them for routine queries.
Adding an argument to disable logging per-schedule would be very helpful:
What blockage? My main concern is not about log inserts adding some kind of load on the server (although it's probably a valid point, too), but purely convenience. 1 job run per second will instantly render job_run_details not very useful as most of the runs will be those second-granilarity schedules.
With a new feature allowing to schedule jobs with second granularity,
job_run_details
is clogged very-very fast rendering it practically useless, especially if you do want to keep log run details for your critical jobs and discard them for routine queries.Adding an argument to disable logging per-schedule would be very helpful:
The text was updated successfully, but these errors were encountered: