- Fixes PostgreSQL 11- support
- Adds a cron.alter_job function to change job properties, by Bertrand Drouvot
- Adds a cron.schedule_in_database function to schedule in a custom database, by Bertrand Drouvot
- Adds a cron.log_min_messages setting to control log_min_messages in pg_cron launcher, by Bertrand Drouvot
- Adds a cron.enable_superuser_jobs setting to disallow superuser jobs
- Fixes a bug that could cause jobs to hang when using cron.use_background_workers, by Bertrand Drouvot
- Fixes a small memory allocation bug, by @mrdrivingduck
- PostgreSQL 14 is supported (no changes were needed)
- Fixes a memory leak
- Background worker support by Bertrand Drouvot
- Audit table support by Bertrand Drouvot
- PostgreSQL 13 support by Alexander Kukushkin
- Schedule jobs by name
- Fixes a bug that could cause cron.schedule to crash with long schedules
- Fixes a bug that could cause cron.schedule to get into an infinite loop
- Fixes a bug that caused overlapping runs not to start
- PostgreSQL 12 support by dverite
- Fixes a bug that caused the cron.job table to not appear in pg_dump
- Adds a cron.host setting to make the postgres host configurable
- Fixes a bug that could cause segmentation fault after cron.unschedule
- Fixes a bug that causes pg_cron to run during pg_upgrade
- Fixes a bug that causes pg_cron to show up incorrectly in pg_stat_activity in PG11
- PostgreSQL 11 support by dverite
- Fix a clang build error by kxjhlele
- Fixed a bug that would cause new jobs to be created as inactive
- Add new 'active' column on cron.job table to enable or disable job(s).
- Added a regression test, simply run 'make installcheck'
- Set relevant application_name in pg_stat_activity
- Increased pg_cron version to 1.1
- PostgreSQL 10 support
- Restrict the maximum number of concurrent tasks
- Ensure table locks on cron.job are kept after schedule/unschedule
- Fixes a memory leak that occurs when a connection fails immediately
- Fixes a memory leak due to switching memory context when loading metadata
- Fixes a segmentation fault that can occur when using an error message after PQclear
- Use WaitLatch instead of pg_usleep when there are no tasks
- Initial 1.0 candidate