vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/drs/umn/drs_03_1131.html
wangdengke2 b937f7e416 drs umn 20230210 version 
Reviewed-by: Boka, Ladislav <ladislav.boka@t-systems.com>
Co-authored-by: wangdengke2 <wangdengke2@huawei.com>
Co-committed-by: wangdengke2 <wangdengke2@huawei.com>
2024-01-11 07:40:50 +00:00

3.3 KiB
Raw Permalink Blame History

Forcibly Stopping Synchronization of GaussDB Distributed

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

Prerequisites

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

Procedure

  1. Log in to each primary DN node of GaussDB distributed instance as the user used when you tested the connectivity between the DRS instance and the GaussDB distributed 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.