Re: FW: pgAgent job limit

["Dave Page" <dpage(at)pgadmin(dot)org>]

On Wed, Mar 19, 2008 at 4:32 PM, Roberts, Jon <Jon(dot)Roberts(at)asurion(dot)com> wrote:
> I was thinking about this part of the pgagent.sql script the other day:
>
>  INSERT INTO pgagent.pga_jobclass (jclname) VALUES ('Routine
>  Maintenance');
>  INSERT INTO pgagent.pga_jobclass (jclname) VALUES ('Data Import');
>  INSERT INTO pgagent.pga_jobclass (jclname) VALUES ('Data Export');
>  INSERT INTO pgagent.pga_jobclass (jclname) VALUES ('Data
>  Summarisation');
>  INSERT INTO pgagent.pga_jobclass (jclname) VALUES ('Miscellaneous');
>
>  You don't have a UI for these job classes but they are used to populate
>  the drop down list when creating a new job.  If someone wants to
>  insert/update/delete any of these job classes, they have to do this
>  manually without a UI.  Based on this, I would think we could add this
>  feature without a UI change.

2 wrongs don't make a right.

>  I also thought about putting the job throttling into the job class by
>  throttling jobs based on the job class they are in.  It would take more
>  changes to the SQL code but I think it would be doable and add more
>  flexibility.

I would be less averse to letting that slide in.

-- 
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk