SHOW LOGICAL REPLICATION JOBS

This feature is in and subject to change. To share feedback and/or issues, contact Support.

Logical data replication is only supported in CockroachDB self-hosted clusters. The SHOW LOGICAL REPLICATION JOBS statement shows details of jobs on a cluster.

This page is a reference for the SHOW LOGICAL REPLICATION JOBS SQL statement, which includes information on its parameters and possible options. For more details on monitoring LDR, refer to the page.

Required privileges

You must have one of the following to run SHOW LOGICAL REPLICATION JOBS:

• The .
• The , which can view all jobs (including admin -owned jobs).

Use the statement:

GRANT SYSTEM VIEWJOB TO user;

Synopsis

xml version=“1.0” encoding=“UTF-8”?

Parameters

Parameter	Description
show\_logical\_replication\_jobs\_options	Option to modify the output.

Options

Option	Description
details	Includes the additional columns: replication\_start\_time, conflict\_resolution\_type, description.

Responses

Field	Response
job\_id	The job’s ID. Use with , , , .
status	The job’s current state. Possible values: pending, paused, pause-requested, failed, succeeded, canceled, cancel-requested, running, retry-running, retry-reverting, reverting, revert-failed. Refer to for a description of each status.
tables	The fully qualified name of the table(s) that are part of the LDR job.
replicated\_time	The latest at which the destination cluster has consistent data. This time advances automatically as long as the LDR job proceeds without error. replicated\_time is updated periodically (every 30s).
replication\_start\_time	The start time of the LDR job.
conflict\_resolution\_type	The type of : LWW last write wins.
command	Description of the job including the replicating table(s) and the cluster connections.

Example

In the destination cluster’s SQL shell, you can query SHOW LOGICAL REPLICATION JOBS to view the LDR jobs running on the cluster:

SHOW LOGICAL REPLICATION JOBS;

        job_id        | status  |          tables          |    replicated_time
----------------------+---------+--------------------------+-------------------------
  1131000153784844289 | running | {db_b.public.test_table} | 2025-12-09 19:33:20+00
  1131000167682211841 | running | {db_a.public.test_table} | 2025-12-09 19:33:20+00
(2 rows)

For additional detail on each LDR job, use the WITH details option:

SHOW LOGICAL REPLICATION JOBS WITH details;

        job_id        | status  |          tables          |    replicated_time     |    replication_start_time     | conflict_resolution_type |                                                                             command
----------------------+---------+--------------------------+------------------------+-------------------------------+--------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------
  1131000153784844289 | running | {db_b.public.test_table} | 2025-12-09 19:35:50+00 | 2025-12-08 20:04:15.512126+00 | LWW                      | CREATE LOGICALLY REPLICATED TABLE test_table FROM TABLE test_table ON 'external://conn_a' WITH OPTIONS (BIDIRECTIONAL ON 'external://conn_b')
  1131000167682211841 | running | {db_a.public.test_table} | 2025-12-09 19:35:50+00 | 2025-12-08 20:04:19.758587+00 | LWW                      | CREATE LOGICAL REPLICATION STREAM FROM TABLE test_table ON 'external://conn_b' INTO TABLE test_table WITH OPTIONS (CURSOR = $1, PARENT = '1131000153784844289')

See also