Re: Support logical replication of DDLs
shveta malik <shveta.malik@gmail.com>
From: shveta malik <shveta.malik@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Amit Kapila <amit.kapila16@gmail.com>,
"Wei Wang (Fujitsu)" <wangw.fnst@fujitsu.com>, "Yu Shi (Fujitsu)" <shiy.fnst@fujitsu.com>, vignesh C <vignesh21@gmail.com>, "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>,
Ajin Cherian <itsajin@gmail.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-16T10:31:37Z
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
- 0001-Deparser-for-Table-DDL-commands-and-exten-2023_06_16.patch (application/octet-stream) patch 0001
- 0002-Enhance-the-event-trigger-to-support-DDL--2023_06_16.patch (application/octet-stream) patch 0002
- 0004-Apply-the-DDL-change-as-that-same-user-th-2023_06_16.patch (application/octet-stream) patch 0004
- 0003-DDL-replication-for-Table-DDL-commands-2023_06_16.patch (application/octet-stream) patch 0003
On Wed, Jun 14, 2023 at 3:26 AM Michael Paquier <michael@paquier.xyz> wrote: > > On Tue, Jun 13, 2023 at 06:49:42PM +0530, Amit Kapila wrote: > > We have to choose one of the approaches between 0001 and 0008. I feel > > we don't need an intermediate ObjTree representation as that adds > > overhead and an additional layer which is not required. As mentioned > > in my previous email I think as a first step we should merge 0001 and > > 0008 and avoid having an additional ObjTree layer unless you or others > > feel we need it. I think that will reduce the overall patch size and > > help us to focus on one of the approaches. > > Similar impression here. I found ObjTree actually confusing compared > to the JSON blobs generated. > +1 Please find the new set of patches. It has below changes: Patch-set Structure related changes to make it more organised: 1) Object-tree removal code (patch 0008 earlier) is now merged to patch 0001. Now there is no reference of object-tree in the code. 2) Subscription tap-test for DDL Replication (patch 0006 earlier) is now merged to patch 0003 (DDL Replication one), as it was a single file change and thus seems more apt to be part of the DDL-Rep patch. 3) test_ddl_deparse_regress module (patch 0004 earlier) is now pulled out for the time being. Rest of the changes: 1) CTAS and SELECT INTO support removal. Initial draft aims to support create,drop and alter-table first. 2) Doc compilation issue fix for 'doc/src/sgml/logical-replication.sgml'. 3) Verbose option removal. Current patch now WAL logs only the information needed to construct the original DDL statement. Missing clauses are not part of the final DDL string. I will upload support for 'expanded' on/off in the next version. 4) Some code refactoring and optimization. With these changes, I hope the patch-set is somewhat easier to review. thanks Shveta