Dave Page wrote:
>>From: Miha Radej
>>- if a job does not execute, i'd like to set an option whether to be
>>executed as soon as possible, delayed or nor, or if execution
>>held until the next planned time.
> You mean the run one missed job and then go back to normal as Andreas
> suggested, or run *all* missed instances?
hmm... i have the innate ability to not properly express what i am
thinking about :)
what i meant with the above was a setting for this: you set a job to be
executed, say, at a certain time. if it doesn't execute at that
specified time, then sometimes it might be possible that someone doesn't
want the job to be executed at all (eg. heavy duty jobs where it would
take up too much resources, time, etc) and rather wait until the next
execution time, while other people might like the job to get executed as
soon as possible, even if the set time is way in the past.
for example, if i have a large database of, say a forum, and have a few
jobs set to be executed. one at 0100 to do some magic with it, next one
at 0400 to do sth else, last one at 0500. so that when people would come
to work at 0600 the jobs would be finished and people would be able to
post as usual while at work :) if it should happen that the last job
couldn't be executed at 0500, i don't want it to be executed at all,
because it might take a lot of time to finish so i risk that the
database will be overloaded with work to do and users might experience
large load times. which might turn some users away, which i don't want.
but if i have some simple tasks planned or have a private database where
i don't care what gets executed and when, then i could set the option to
simply execute the job when it gets its turn, regardless whether the
start time has already passed.
the above option, along with this one:
"- an option whether to execute jobs several times or only once, would
be handy. for example, if i have a daily job and have an incrementing
value set to n, i'd expect it to be n+5 5 days later. sometimes, when,
say, refreshing data in a table, multiple executions aren't necessary,
so a checkbox or something would be nice imo. "
are imho somewhat connected. so some jobs i would like to be executed
all at once (those that were delayed), while others i don't need
executed more than once. i can't help myself, i like lots of options and
checkboxes and so forth :)
this was what i was trying to say and i hope i didn't complicate matters
too much as i usually do :)
In response to
pgadmin-hackers by date
|Next:||From: cvs||Date: 2005-03-11 09:40:12|
|Subject: CVS Commit by dpage: Updated pgAgent schema with cron-style scheduling.|
|Previous:||From: Dave Page||Date: 2005-03-09 10:38:52|
|Subject: Re: RFC: pgAgent Scheduler Design|