Skip site navigation (1) Skip section navigation (2)

Re: RFC: pgAgent Scheduler Design

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Miha Radej" <miha(dot)radej(at)siix(dot)com>
Cc: <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: RFC: pgAgent Scheduler Design
Date: 2005-03-11 11:26:08
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E472BAA1@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgadmin-hackers
 

> -----Original Message-----
> From: Miha Radej [mailto:miha(dot)radej(at)siix(dot)com] 
> Sent: 09 March 2005 22:03
> To: Dave Page
> Cc: pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] RFC: pgAgent Scheduler Design
> 
> hmm... i have the innate ability to not properly express what i am 
> thinking about :)

<grin>

> 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.

OK. I guess that we'd need some tolerance to do this, so combined with
previous thinking:

jsccatchup  bool 		-- If set, run all missed occurances
when catching up after missing runs.
jscmaxdelay interval	-- If the job doesn't start within this time of
it's scheduled start, don't run at all.

I'm not sure that is entirely logical with the existing 'play first run
after missing one' design though (which isn't overly easy to change too
much).

Regards, Dave.

pgadmin-hackers by date

Next:From: cvsDate: 2005-03-11 15:47:24
Subject: CVS Commit by dpage: Display schedules properly in the properties pane
Previous:From: cvsDate: 2005-03-11 09:40:12
Subject: CVS Commit by dpage: Updated pgAgent schema with cron-style scheduling.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group