| From: | Peter Smith <smithpb2250(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Single transaction in the tablesync worker? |
| Date: | 2021-01-25 02:32:52 |
| Message-ID: | CAHut+Psj7Xm8C1LbqeAbk-3duyS8xXJtL9TiGaeu3P8g272mAA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Amit.
PSA the v19 patch for the Tablesync Solution1.
Main differences from v18:
+ Patch has been rebased off HEAD @ 24/Jan
+ Addressing some review comments [ak0123]
====
Features:
* The tablesync worker is now allowing multiple tx instead of single tx.
* A new state (SUBREL_STATE_FINISHEDCOPY) is persisted after a
successful copy_table in tablesync's LogicalRepSyncTableStart.
* If a re-launched tablesync finds state SUBREL_STATE_FINISHEDCOPY
then it will bypass the initial copy_table phase.
* Now tablesync sets up replication origin tracking in
LogicalRepSyncTableStart (similar as done for the apply worker). The
origin is advanced when first created.
* The tablesync replication origin tracking record is cleaned up by:
- process_syncing_tables_for_apply
- DropSubscription
- AlterSubscription_refresh
* Updates to PG docs.
* New TAP test case.
Known Issues:
* None.
---
Kind Regards,
Peter Smith.
Fujitsu Australia
| Attachment | Content-Type | Size |
|---|---|---|
| v19-0001-Tablesync-Solution1.patch | application/octet-stream | 18.1 KB |
| v19-0002-Tablesync-extra-logging.patch | application/octet-stream | 5.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | japin | 2021-01-25 02:47:21 | Re: About to add WAL write/fsync statistics to pg_stat_wal view |
| Previous Message | Andy Fan | 2021-01-25 02:21:12 | Re: Extend more usecase for planning time partition pruning and init partition pruning. |