Hi Amit. PSA the v11 patch for the Tablesync Solution1.
Difference from v10: - Addresses several recent review comments. - pg_indent has been run ==== Features: * tablesync slot is now permanent instead of temporary. The tablesync slot name is no longer tied to the Subscription slot na * the tablesync slot cleanup (drop) code is added for DropSubscription and for finish_sync_worker functions * tablesync worked now allowing multiple tx instead of single tx * a new state (SUBREL_STATE_COPYDONE) is persisted after a successful copy_table in LogicalRepSyncTableStart. * if a re-launched tablesync finds the state is SUBREL_STATE_COPYDONE then it will bypass the initial copy_table phase. * tablesync sets up replication origin tracking in LogicalRepSyncTableStart (similar as done for the apply worker). The origin is advanced when first created. * tablesync replication origin tracking is cleaned up during DropSubscription and/or process_syncing_tables_for_apply. * the DropSubscription cleanup code was enhanced (v7+) to take care of crashed sync workers. * minor updates to PG docs TODO / Known Issues: * address review comments --- Kind Regards, Peter Smith. Fujitsu Australia
v11-0001-Tablesync-Solution1.patch
Description: Binary data
v11-0002-Tablesync-extra-logging.patch
Description: Binary data
