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.
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.
Jon
> -----Original Message-----
> From: Dave Page [mailto:dpage@pgadmin.org]
> Sent: Wednesday, February 27, 2008 3:14 AM
> To: Roberts, Jon
> Cc: pgadmin-hackers; Lucas, Craig
> Subject: Re: FW: [pgadmin-hackers] pgAgent job limit
>
> On Wed, Feb 27, 2008 at 3:29 AM, Roberts, Jon
<Jon.Roberts@asurion.com>
> wrote:
> >
> > I agree that a UI change would be ideal.
>
> Required, if this design is to be accepted in the standard code. Let
> me check it over first though - I may have other concerns.
>
> --
> Dave Page
> EnterpriseDB UK: http://www.enterprisedb.com
> The HOT PostgreSQL Company
