Re: Support logical replication of DDLs
shveta malik <shveta.malik@gmail.com>
From: shveta malik <shveta.malik@gmail.com>
To: "Yu Shi (Fujitsu)" <shiy.fnst@fujitsu.com>
Cc: vignesh C <vignesh21@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>,
Ajin Cherian <itsajin@gmail.com>, "Wei Wang (Fujitsu)" <wangw.fnst@fujitsu.com>,
Runqi Tian <runqidev@gmail.com>, Peter Smith <smithpb2250@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
li jie <ggysxcq@gmail.com>, Dilip Kumar <dilipbalaut@gmail.com>,
Alvaro Herrera <alvherre@alvh.no-ip.org>, Masahiko Sawada <sawada.mshk@gmail.com>, Japin Li <japinli@hotmail.com>, rajesh singarapu <rajesh.rs0541@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Zheng Li <zhengli10@gmail.com>, shveta malik <shveta.malik@gmail.com>
Date: 2023-06-05T09:30:01Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add a run_as_owner option to subscriptions.
- 482675987bcd 16.0 cited
-
Refactor pgoutput_change().
- da324d6cd45b 16.0 cited
-
Print the correct aliases for DML target tables in ruleutils.
- df931e9ab35b 11.20 landed
- c8a5f1685fb7 15.3 landed
- 4efb4f0d4878 13.11 landed
- 3dd287c14fac 12.15 landed
- 393430f57544 16.0 landed
- 14345f3c6a7b 14.8 landed
-
Fix object identity string for transforms
- 9a312562314a 16.0 landed
-
Add grantable MAINTAIN privilege and pg_maintain role.
- 60684dd834a2 16.0 cited
-
Get rid of recursion-marker values in enum AlterTableType
- 840ff5f451cd 16.0 cited
-
Release cache tuple when no longer needed
- ed0fbc8e5ac9 15.0 cited
-
Empty search_path in logical replication apply worker and walsender.
- 11da97024abb 14.0 cited
-
Refactor format_type APIs to be more modular
- a26116c6cbf4 11.0 cited
-
Use wrappers of PG_DETOAST_DATUM_PACKED() more.
- 3a0d473192b2 10.0 cited
Attachments
- 0003-Add-verbose-option-for-ddl-deparse-module-2023_06_05.patch (application/octet-stream) patch 0003
- 0001-Deparser-for-Table-DDL-commands-and-exten-2023_06_05.patch (application/octet-stream) patch 0001
- 0002-Enhance-the-event-trigger-to-support-DDL--2023_06_05.patch (application/octet-stream) patch 0002
- 0005-DDL-replication-for-Table-DDL-commands-2023_06_05.patch (application/octet-stream) patch 0005
- 0004-Introduce-the-test_ddl_deparse_regress-te-2023_06_05.patch (application/octet-stream) patch 0004
- 0006-Add-subscription-tap-test-for-DDL-replica-2023_06_05.patch (application/octet-stream) patch 0006
- 0007-Apply-the-DDL-change-as-that-same-user-th-2023_06_05.patch (application/octet-stream) patch 0007
- 0008-ObjTree-Removal-for-multiple-commands-2023_06_05.patch (application/octet-stream) patch 0008
On Thu, Jun 1, 2023 at 1:10 PM Yu Shi (Fujitsu) <shiy.fnst@fujitsu.com> wrote: > > On Wed, May 31, 2023 5:41 PM shveta malik <shveta.malik@gmail.com> wrote: > > > > On Mon, May 29, 2023 at 11:45 AM Yu Shi (Fujitsu) <shiy.fnst@fujitsu.com> > > wrote: > > > > > > 0008 patch > > > ----- > > > 4. > > > case AT_AddColumn: > > > /* XXX need to set the "recurse" bit somewhere? */ > > > Assert(IsA(subcmd->def, ColumnDef)); > > > - tree = deparse_ColumnDef(rel, dpcontext, false, > > > - (ColumnDef *) subcmd->def, true, > > &expr); > > > > > > mark_function_volatile(context, expr); > > > > > > After this change, `expr` is not assigned a value when mark_function_volatile is > > called. > > > > > > > Corrected. > > > > It looks the call to mark_function_volatile() is removed in this case. I think > we still need it, otherwise we won't know if the command contains a volatile > function. (see check_command_publishable().) > Modified this. Thanks for pointing this out. > > > 5. > > > create table p1(f1 int); > > > create table p1_c1() inherits(p1); > > > alter table p1 add constraint inh_check_constraint1 check (f1 > 0); > > > alter table p1_c1 add constraint inh_check_constraint1 check (f1 > 0); > > > > > > The re-formed command of the last command is "ALTER TABLE public.p1_c1", > > which > > > seems to be wrong. > > > > > > > Fixed, second alter-table should actually be no-op in terms of > > deparsing. But when it is run without running the first alter-table > > command, it should generate the reformed command. > > > > If the second alter-table is no-op in terms of deparsing, the dumped result of > origin command and that of re-formed command will be different. This seems to be > because `conislocal` column of pg_constraint has different values. (After the > second alter-table, its value is changed from false to true.) > Okay, I see. I am analyzing it to figure out if we really need the second call to be replicated on sub. It needs more review around the impact of 'conislocal'. I will respond once concluded. Please find the new set of patches attached. The changes are in 0008 only. New changes are majorly for: --comments given by Shi-san. Thanks Vignesh for working on this. --addition of more test-cases to cover missing scenarios. Thanks Shi-san for working on this. thanks Shveta