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

Re: RFC: pgAgent Scheduler Design

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: RFC: pgAgent Scheduler Design
Date: 2005-03-03 10:49:50
Message-ID: 4226EBCE.8060709@pse-consulting.de (view raw or flat)
Thread:
Lists: pgadmin-hackers
Dave Page wrote:
> 
>>Exceptions are probably only needed for days, e.g. "I want to 
>>do backups 
>>every weekday, but on Jan 1st nobody will change the tape so I don't 
>>want to have it run then."
>>
>>So I'd propose an additional exception table:
>>
>>CREATE TABLE pgagent.pga_exception
>>(
>>   jexscid int4 NOT NULL,
>>   jexdate date NOT NULL,
>>   jexdorun bool,   -- run in addition to schedule if true
> 
> 
> Run in addition is easy anyway - a new schedule may be added to the
> existing job.
> 

Ok. I was thinking of just extending an existing schedule with a simple 
click for a "run additonally" exception, but this is maybe too much 
effort for very rare cases.

> How about adding a simple date[] column to the schedule in which the
> user can add arbitrary 'don't run' dates?

Ok. I'm usually not designing data models using vector/array datatypes 
because inter-db portability issues are always implicitely considered by 
  some cells deep in my brain.
In case of exceptions, IMHO it's a bit unfortunate to use them, because 
adding/deleting a single value would always mean to modify the whole 
column, so I'd still prefer an additional table (jexdorun omitted).

Regards,
Andreas

In response to

pgadmin-hackers by date

Next:From: Andreas PflugDate: 2005-03-03 11:48:46
Subject: graphical explain done
Previous:From: cvsDate: 2005-03-03 08:34:56
Subject: CVS Commit by dpage: Don't wrap queries accross multiple lines to avoid

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