Re: how to be related with the schedule and step

From: Dave Page <dpage(at)pgadmin(dot)org>
To: jimmy <mpokky(at)126(dot)com>
Cc: "pgadmin-support lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: Re: how to be related with the schedule and step
Date: 2018-09-12 08:22:24
Message-ID: CA+OCxoz5HzwRAecBY-UD-OeQFQYRL_phaQdnFsOX=D7003GSaw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

On Wed, Sep 12, 2018 at 7:43 AM, jimmy <mpokky(at)126(dot)com> wrote:

> I use pgAgent 3.4 in pgAdmin 4 to create a job. In this job I create a
> schedule and a step.
> I query the table pga_job, pga_jobagent, I find pga_job.jobagentid is null.
> That means it is not related with this schedule and step.
> How to operate that it will be related with the pga_job.jobagentid and
> pga_jobagent.jagpid,
>

Those fields are used for internal tracking, and should not be modified.

What are you trying to do exactly?

> this is the error logs:
> ============================================================
> ============================================================
> 2018-09-12 11:00:06 HKT [7300]: [1-1] user=postgres,db=postgres,app=jpgAgent:
> WIN-IL4VKOA9EAB,client=127.0.0.1 ERROR: insert or update on table
> "pga_job" violates foreign key constraint "pga_job_jobagentid_fkey"
> 2018-09-12 11:00:06 HKT [7300]: [2-1] user=postgres,db=postgres,app=jpgAgent:
> WIN-IL4VKOA9EAB,client=127.0.0.1 DETAIL: Key (jobagentid)=(7300) is not
> present in table "pga_jobagent".
> 2018-09-12 11:00:06 HKT [7300]: [3-1] user=postgres,db=postgres,app=jpgAgent:
> WIN-IL4VKOA9EAB,client=127.0.0.1 STATEMENT: UPDATE pgagent.pga_job SET
> jobagentid=$1, joblastrun=now() WHERE jobenabled AND jobagentid IS NULL AND
> jobnextrun <= now() AND (jobhostagent = '' OR jobhostagent = $2) RETURNING
> jobid, jobname, jobdesc
> ============================================================
> ================================================================
>
>
>
>

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Johann Spies 2018-09-12 09:12:09 Re: PgAdmin4 stopped working: "The application server could not be contacted."
Previous Message Dave Page 2018-09-12 08:05:37 Re: PgAdmin4 stopped working: "The application server could not be contacted."