| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | David Greco <David_Greco(at)harte-hanks(dot)com> |
| Cc: | "PgAdmin Support (pgadmin-support(at)postgresql(dot)org)" <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: PGAgent runs all jobs on startup |
| Date: | 2013-08-13 08:13:06 |
| Message-ID: | CA+OCxoz8Lrq+6htvfHVN+RA82qZVU15C1Aj7PBESamfZf2dp3g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Mon, Aug 12, 2013 at 7:35 PM, David Greco
<David_Greco(at)harte-hanks(dot)com> wrote:
> I have about 20 jobs scheduled via PGAgent to run at various times. Some
> daily, some every X minutes, some at certain times, etc. I just started
> pgagent on the server and noticed it ran all my jobs upon startup, despite
> it not being a scheduled time. Is this an option somewhere I’m missing?
No, this was an intentional design choice - we actually polled the
community to find out what behaviour people wanted here. Essentially,
when the agent restarts it plays "catchup", and runs all the jobs it
missed. It then recalculates the new runtime for each that is always
in the future. So, if you had an hourly job and the agent was down
from 11:30 until 17:30, it would run the 12:00 instance of the job at
startup (17:30) then resume the normal schedule at 18:00.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dinesh Kumar | 2013-08-13 09:55:57 | Re: Password setting having somewhat bizarre results. |
| Previous Message | John Foelster | 2013-08-13 00:30:11 | Re: Password setting having somewhat bizarre results. |