Re: Support logical replication of DDLs
Zheng Li <zhengli10@gmail.com>
From: Zheng Li <zhengli10@gmail.com>
To: Peter Smith <smithpb2250@gmail.com>, vignesh C <vignesh21@gmail.com>
Cc: li jie <ggysxcq@gmail.com>, Ajin Cherian <itsajin@gmail.com>, Dilip Kumar <dilipbalaut@gmail.com>,
Alvaro Herrera <alvherre@alvh.no-ip.org>, "houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>,
Amit Kapila <amit.kapila16@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, Japin Li <japinli@hotmail.com>, rajesh singarapu <rajesh.rs0541@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-01-07T15:28:11Z
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
- v60-0004-Introduce-the-test_ddl_deparse_regress-test-module.patch (application/octet-stream) patch v60-0004
- v60-0001-Infrastructure-to-support-DDL-deparsing.patch (application/octet-stream) patch v60-0001
- v60-0002-Functions-to-deparse-Table-DDL-commands.patch (application/octet-stream) patch v60-0002
- v60-0005-DDL-messaging-infrastructure-for-DDL-replication.patch (application/octet-stream) patch v60-0005
- v60-0003-Support-DDL-deparse-of-the-rest-commands.patch (application/octet-stream) patch v60-0003
- v60-0007-Document-DDL-replication-and-DDL-deparser.patch (application/octet-stream) patch v60-0007
- v60-0006-Support-DDL-replication.patch (application/octet-stream) patch v60-0006
Hi, I added documentation and changed user interface design in the attached v60 patch set. The patch set addressed comments from Peter in [1]. The motivation for the user interface change is that we want to manage DDL replication feature in stages with fine grained replication levels. For example, we can focus on reviewing and testing table commands first, then other commands. It also make sense to introduce different DDL replication levels from the user perspective as pointed out in [1]. We can add more replication levels along the way. In this patch DDL replication is disabled by default and it can be enabled at different levels using the new PUBLICATION option 'ddl'. This option currently has two levels and are only allowed to be set if the PUBLICATION is FOR ALL TABLES. all: this option enables replication of all supported DDL commands. table: this option enables replication of Table DDL commands which include: -CREATE/ALTER/DROP TABLE -CREATE TABLE AS Example: Create a new publication with all ddl replication enabled: CREATE PUBLICATION pub1 FOR ALL TABLES with (ddl = 'all'); Enable table ddl replication for an existing Publication: ALTER PUBLICATION pub2 SET (ddl = 'table'); Also I break down ddl_deparse.c into two patches: 1.v60-0002-Functions-to-deparse-Table-DDL-commands.patch 2.v60-0003-Support-DDL-deparse-of-the-rest-commands.patch Regards, Zane [1] https://www.postgresql.org/message-id/CAAD30UKX%3DPbojrjU0webYy7Y9mz1HmDTM3dx_JJXpc%2BdXW-EQQ%40mail.gmail.com