| From: | vignesh C <vignesh21(at)gmail(dot)com> |
|---|---|
| To: | "Kumar, Sachin" <ssetiya(at)amazon(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Initial Schema Sync for Logical Replication |
| Date: | 2023-10-19 09:40:33 |
| Message-ID: | CALDaNm3W4CLaALMzNMTJd7Hpunmecib4AUZc63HmmoGvXKdV2Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 31 Aug 2023 at 17:18, Kumar, Sachin <ssetiya(at)amazon(dot)com> wrote:
>
> Hi Everyone, based on internal discussion with Masahiko
> I have implemented concurrent DDL support for initial schema sync.
>
> Concurrent Patch workflow
>
> 1. When TableSync worker creates a replicaton slot, It will
> save the slot lsn into pg_subscription_rel with
> SUBREL_SYNC_SCHEMA_DATA_SYNC state, and it will wait for
> its state to be SUBREL_STATE_DATASYNC.
>
> 2. Applier process will apply DDLs till tablesync lsn, and then
> it will change pg_subscription_rel state to SUBREL_STATE_DATASYNC.
>
> 3. TableSync will continue applying pending DML/DDls till it catch up.
>
> This patch needs DDL replication to apply concurrent DDLs, I have cherry-
> picked this DDL patch [0]
Can you rebase the patch and post the complete set of required changes
for the concurrent DDL, I will have a look at them.
Regards,
Vignesh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2023-10-19 09:41:59 | Re: Initial Schema Sync for Logical Replication |
| Previous Message | Michael Banck | 2023-10-19 09:39:32 | [patch] pg_basebackup: mention that spread checkpoints are the default in --help |