Help Center > > Developer Guide> System Catalogs and System Views> System Catalogs> PG_JOB

PG_JOB

Updated at: Jul 15, 2020 GMT+08:00

PG_JOB records detailed information about jobs created by users. Dedicated threads poll the pg_job table and trigger jobs based on scheduled job execution time, and update job status in the pg_job table. This table belongs to the Shared Relation category. All job records are visible to all databases.

Table 1 PG_JOB columns

Name

Type

Description

job_id

bigint

Job ID, primary key, unique (with a unique index)

current_postgres_pid

bigint

If the current job has been executed, the postgres thread ID of this job is recorded. The default value is -1, indicating that the job has not yet been executed.

log_user

name

User name of the job creator

priv_user

name

User name of the job executor

dbname

name

Name of the database in which the job will be executed

node_name

name

CN node on which the job will be executed

job_status

"char"

Status of the current job. The value range is 'r', 's', 'f', 'd'. The default value is 's'. The indications are as follows:

Status of job step: r=running, s=successfully finished, f=job failed, d=disable

If a job fails to be executed for 16 consecutive times, job_status is automatically set to 'd', and no more attempt will be made on this job.

Note: When you disable a scheduled task (by setting job_queue_processes to 0), the thread monitor the job execution is not started, and the job status will not be updated. You can ignore this status. Only when the scheduled task function is enabled (that is, when job_queue_processes is not 0), the system updates the value of this column based on the real-time job status.

start_date

timestamp without time zone

Start time of the first job execution, accurate to millisecond

next_run_date

timestamp without time zone

Scheduled time of the next job execution, accurate to millisecond

failure_count

smallint

Number of times the job has started and failed. If a job fails to be executed for 16 consecutive times, no more attempt will be made on it.

interval

text

Job execution interval

last_start_date

timestamp without time zone

Start time of the last job execution, accurate to millisecond

last_end_date

timestamp without time zone

End time of the last job execution, accurate to millisecond

last_suc_date

timestamp without time zone

Start time of the last successful job execution, accurate to millisecond

this_run_date

timestamp without time zone

Start time of the ongoing job execution, accurate to millisecond

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel