yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
0110b557aa09e8af8559549d0f32cef2afd3d328
doc-exports/docs/drs/umn/drs_03_1131.html
wangdengke2 0110b557aa drs_umn 
Reviewed-by: Székely, Ond <ond.szekely@t-systems.com>
Co-authored-by: wangdengke2 <wangdengke2@huawei.com>
Co-committed-by: wangdengke2 <wangdengke2@huawei.com>
2025-08-14 14:05:39 +00:00

3.3 KiB
Raw Blame History

Forcibly Stopping Synchronization from GaussDB Distributed

This section describes how to delete streaming replication slots of the source distributed GaussDB database after an incremental or a full+incremental synchronization task is forcibly stopped.

Prerequisites

Common users do not have the permission to perform EXECUTE DIRECT. To delete streaming replication slots, contact GaussDB O&M personnel.

Procedure

  1. Log in to each primary DN node of the distributed GaussDB instance as the user used when you tested the connectivity between the DRS instance and the distributed GaussDB instance.
  2. Run the following statement to query the streaming replication slot name of the database object selected for 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.

  3. Run the following statement to delete the streaming replication slot:

    select * from pg_drop_replication_slot('slot_name');

    In the preceding command, slot_name indicates the name of the streaming replication slot queried in 2.

  4. Run the following statement to check whether the streaming replication slot is successfully deleted:

    select slot_name from pg_replication_slots where database = 'database';

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

  5. Repeat the preceding operations to ensure that the streaming replication slot on each primary DN is deleted.