diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2024-06-30 14:24:14 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2024-06-30 14:24:14 -0400 |
| commit | 917754557cc0002bb042341720a7ce18fe5b0a09 (patch) | |
| tree | add6e56289d799bf85cea6059a589a9fa64ef000 /doc/src | |
| parent | b3f5ccebd79d9c7b73f4e04611cdf31fdf87420b (diff) | |
| download | postgresql-917754557cc0002bb042341720a7ce18fe5b0a09.tar.gz postgresql-917754557cc0002bb042341720a7ce18fe5b0a09.zip | |
Make pg_createsubscriber warn if publisher has two-phase commit enabled.
pg_createsubscriber currently always sets up logical replication
with two-phase commit disabled. Improving that is not going to
happen for v17. In the meantime, document the deficiency, and
adjust pg_createsubscriber so that it will emit a warning if
the source installation has max_prepared_transactions > 0.
Hayato Kuroda (some mods by Amit Kapila and me), per complaint from
Noah Misch
Discussion: https://postgr.es/m/20240623062157.97.nmisch@google.com
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/ref/pg_createsubscriber.sgml | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/src/sgml/ref/pg_createsubscriber.sgml b/doc/src/sgml/ref/pg_createsubscriber.sgml index 2ee6eee9e35..87a9d3db28e 100644 --- a/doc/src/sgml/ref/pg_createsubscriber.sgml +++ b/doc/src/sgml/ref/pg_createsubscriber.sgml @@ -354,6 +354,17 @@ PostgreSQL documentation </para> <para> + <application>pg_createsubscriber</application> sets up logical + replication with two-phase commit disabled. This means that any + prepared transactions will be replicated at the time + of <command>COMMIT PREPARED</command>, without advance preparation. + Once setup is complete, you can manually drop and re-create the + subscription(s) with + the <link linkend="sql-createsubscription-params-with-two-phase"><literal>two_phase</literal></link> + option enabled. + </para> + + <para> <application>pg_createsubscriber</application> changes the system identifier using <application>pg_resetwal</application>. It would avoid situations in which the target server might use WAL files from the source |