Help Center/ Data Replication Service/ Real-Time Synchronization/ Operation Reference in Synchronization Scenarios/ Forcibly Stopping Synchronization of GaussDB Centralized
Updated on 2025-07-22 GMT+08:00
View PDF

Forcibly Stopping Synchronization of GaussDB Centralized

This section describes how to delete residual logical replication slots that may remain in the source GaussDB Centralized database after an incremental or a full+incremental synchronization task is forcibly stopped.

Procedure

  1. Query the replication slot name used by DRS in "create replication slot [Replication slot name] successfully by replication connection" on the Synchronization Logs page.
  2. Log in to the GaussDB Centralized instance as the user used when you tested connectivity between the DRS instance and the instance.
  3. Run the following statement to query information about all replication slots in the database selected in the synchronization task: 

    select slot_name from pg_replication_slots where database = 'database';

    In the preceding command, database indicates the database selected in the synchronization task.

  4. If the query result contains the replication slot name used by the DRS task but the replication slot is not used (active='f'), run the following statement to delete its logical replication slot: 

    select * from pg_drop_replication_slot('slot_name');

    In the preceding command, slot_name indicates the replication slot name queried in 1.

  5. Run the following statement to check whether the logical replication slot is successfully deleted: 

    select slot_name from pg_replication_slots where  slot_name = 'slot_name';

    If the query result is empty, the logical replication slot is deleted.