You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
import resync_button from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/resync_button.png'
9
9
10
-
### What does Resync do?
10
+
### What does Resync do? {#what-does-resync-do}
11
11
12
12
Resync involves the following operations in order:
13
13
1. The existing ClickPipe is dropped, and a new "resync" ClickPipe is kicked off. Thus, changes to source table structures will be picked up when you resync.
14
14
2. The resync ClickPipe creates (or replaces) a new set of destination tables which have the same names as the original tables except with a `_resync` suffix.
15
15
3. Initial load is performed on the `_resync` tables.
16
16
4. The `_resync` tables are then swapped with the original tables. Soft deleted rows are transferred from the original tables to the `_resync` tables before the swap.
17
17
18
-
19
18
All the settings of the original ClickPipe are retained in the resync ClickPipe. The statistics of the original ClickPipe are cleared in the UI.
20
19
21
-
### Use cases for resyncing a ClickPipe
20
+
### Use cases for resyncing a ClickPipe {#use-cases-for-resyncing-a-clickpipe}
22
21
Here are a few scenarios:
23
22
24
23
1. You may need to perform major schema changes on the source tables which would break the existing ClickPipe and you would need to restart. You can just click Resync after performing the changes.
@@ -30,7 +29,7 @@ You can resync multiple times, however please account for the load on the source
30
29
since initial load with parallel threads is involved each time.
0 commit comments