forked from MigOpsRepos/pg_dbms_job
-
Notifications
You must be signed in to change notification settings - Fork 0
/
ChangeLog
71 lines (55 loc) · 3.14 KB
/
ChangeLog
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
Mon Apr 11 2022 - Version 1.2.0
This release is maintenance release since last release to fix issues
reported by users since the past height months. It also adds some
improvements.
* Add configuration directive job_queue_processes to control the
maximum number of job processed at the same time.
* Keep entries in the jobs table to be able to monitor the duration
of a task. Thank to Jagrab3 for the patch.
* Allow strftime() escapes in log filename, for example to have a
log file per week day use %a in the file name.
* Add new configuration directive log_truncate_on_rotation to truncate file
on rotation. When activated an existing log file with the same name as the
new log file will be truncated rather than appended to. But such truncation
only occurs on time-driven rotation, not on restarts.
Thanks to K RamaKrishna Sastry for the feature request.
* Allow pg_dbms_job to run on a standby server without reporting error.
The daemon detects that it is running on a standby and disconnect
immediately, it will try to connect 3 seconds later. Thanks to
K RamaKrishna Sastry for the feature request.
* Try to reconnect PostgreSQL after 3 seconds when the connection fail.
Thanks to K RamaKrishna Sastry for the report.
Here is the complete list of other changes:
- Fix an extract comma that make the update on failure fail.
- Fix single execution mode with lasted change on connection error and
update regression tests configuration file.
- Prevent removing the pid file if pg_dbms_job can't find the
configuration file and the -k option is used.
- Do not die on error when pg_dbms_job reload the configuration file.
- Explain the behavior of the update done on table dbms_job.all_scheduled_jobs
after a job completion when it fails or it is successful.
Sat Aug 28 2021 - Version 1.1.0
This release is maintenance release since last release to fix some
possible wrong behaviors, control other ones and improve documentation.
- Add configuration directive job_queue_processes to control the limit
of jobs that can be run at the same time.
- Fix insertion failure in job history table when PQSTATUS returned
contains single quote.
- Fix possible case where asynchronous jobs can be executed twice
if they are not removed fast enough from the queue.
- Fix regression test to use latest SQL version of the extension.
- Add limitations on pg_dbms_job use and especially about the NOTIFY
queue size limits. Thanks to Julien Rouhaud for the report.
- Add missing information on how to stop or reload configuration of
the scheduler.
- Add information that unlike with cron-like scheduler, when the scheduler
starts it executes all active jobs with a next date in the past.
- Add information that jobs are executed with the role that has submitted
the job and with the search path was used at job creation time.
To upgrade installed pg_dbms_job version 1.0.1 execute:
ALTER EXTENSION pg_dbms_job UPDATE;
after installing the new version using: make && sudo make install
Wed Aug 25 2021: Version 1.0.1
- Fix CREATE EXTENSION that was broken.
Wed Aug 25 2021: Version 1.0.0
- Initial release