On Sat, May 22, 2010 at 4:33 PM, Matthew Gabeler-Lee <chee...@fastcat.org> wrote: > I'm trying to customize an existing pgAgent job by adding some steps, one of > which needs to run before the existing step. Unfortunately this doesn't > seem to be possible without re-creating the job from scratch. > > It appears that the order is determined simply by the job step table's PK. > Since the foriegn key from the step log table doesn't have an "on update > cascade" clause, nor is it deferrable, the ID of existing jobs that have run > at least once can't be changed.
Steps are ordered by their name - pgAgent does something like SELECT steps FROM steptable ORDER BY stepname, so ordering will be per the locale of your database. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
