Support structured PostgreSQL publication and subscription DDL - #2554
Open
minleejae wants to merge 2 commits into
Open
Support structured PostgreSQL publication and subscription DDL#2554minleejae wants to merge 2 commits into
minleejae wants to merge 2 commits into
Conversation
Contributor
|
Please resolve conflicts. |
minleejae
force-pushed
the
feat/postgresql-replication-ddl
branch
from
September 6, 2026 13:52
e51c8c0 to
cd47a3c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add structured PostgreSQL CREATE/ALTER PUBLICATION and CREATE/ALTER SUBSCRIPTION statements, independently based on master.
Only explicitly named publication tables are reported as relations. Schema names, publication names, subscription names and connection strings are not table references. Subscription operations that can initiate asynchronous data copying are classified as possible data modifications. New StatementVisitor methods have compatibility defaults.
The capability flags cover statement families, not every server-version-specific option or catalog-dependent restriction. Usage documentation explains these boundaries and warns that serialized subscription SQL can contain connection credentials.
Validation
References: CREATE PUBLICATION, ALTER PUBLICATION, CREATE SUBSCRIPTION, ALTER SUBSCRIPTION.