…en joining against pg_stat_activty
…missing jobs existed
…k_job_status() output. Please read CHANGELOG for important info.
…en run but never finished with an end_time or status set in job_log, it wouldn't raise an alert that is was missing. Marked select functions as STABLE
…n. It can also notify on level 2 sensitivity issues now as well
…on multiple warning level incidents. fail_job() can now mark a job as finishing with different error levels. See CHANGELOG for more info.
…. See CHANGELOG for more details.
…ndard port of 5432
…n interval. Logs it too! Made foreign key in job_detail ON DELETE CASCADE.
…g and monitoring for single queries. Updated docs.
…t_time in job_log to determine the last run of a job. Also more clearly lets you know if a job is blocked by an object lock
…ext and made it use job_status_text.alert_text value for code 3 value. Made column names in job_status_text more consistent with the rest of extension
…bles. This update query must be run manually in addition to running the extension update command. Updates to the pg_extension table don't seem to be working via the extension update system. Brand new installations will be set up correctly from the start.
… to add role credentials to a new table
…l and cancel functions to no longer take custom config table. Table constraints explicitly named. update_step() no longer takes job_id parameter. job_alert_nagios table renamed. job_detail elapsed_time column data type changed. Fixed job_log trigger for monitoring table not actually working. Updated documentation and test scripts.
…table parameters and removing the overloaded functions. Changed show_detail default limit from 10 to 1. Fixed bugs in show_status and show_detail functions using the wrong limit parameter variable. Fixed bugs in testjob function. Created new sql file for testing show functions. Updated documentation to show change in logging functions and added show functions. Update script for 0.2.0 to 0.2.1.