Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit63d2786

Browse files
alvherrepull[bot]
authored andcommitted
Rework <warning> box about column list combining in logical replication
After some copy-edit I made in commit3a06a79, we have a <sect2>that only contains a warning box. This doesn't look good. Rework bymoving the sect2 title to be the warning's title, and put the 'id' to itas well, so that the external reference continues to work.Backpatch to 15.In branch master, I also take the opportunity to add titles to a coupleof other warning boxes elsewhere in the documentation.Discussion:https://postgr.es/m/20221219164713.ccnlvtkyj6lmshqq@alvherre.pgsql
1 parent8e416b3 commit63d2786

File tree

3 files changed

+26
-19
lines changed

3 files changed

+26
-19
lines changed

‎doc/src/sgml/logical-replication.sgml

Lines changed: 20 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1310,26 +1310,30 @@ test_sub=# SELECT * FROM child ORDER BY a;
13101310
ignoring any column lists.
13111311
</para>
13121312

1313-
<sect2 id="logical-replication-col-list-combining">
1314-
<title>Combining Multiple Column Lists</title>
1315-
1316-
<warning>
1313+
<warning id="logical-replication-col-list-combining">
1314+
<title>Warning: Combining Column Lists from Multiple Publications</title>
1315+
<para>
1316+
There's currently no support for subscriptions comprising several
1317+
publications where the same table has been published with different
1318+
column lists. <xref linkend="sql-createsubscription"/> disallows
1319+
creating such subscriptions, but it is still possible to get into
1320+
that situation by adding or altering column lists on the publication
1321+
side after a subscription has been created.
1322+
</para>
13171323
<para>
1318-
It is not supported to have a subscription comprising severalpublications
1319-
where the same table has been published with different column lists.
1320-
This means changing the column lists of the tables being subscribed could
1321-
cause inconsistency of column lists among publications, in which case
1322-
the <xref linkend="sql-alterpublication"/> will be successful but later
1323-
the walsender on the publisher, or the subscriber may throw an error. In
1324-
this scenario, the user needs to recreatethesubscription after adjusting
1325-
the column list or drop the problematic publication using
1326-
<literal>ALTER SUBSCRIPTION ... DROP PUBLICATION</literal>and then add it
1327-
back after adjusting thecolumn list.
1324+
This means changing the column lists of tables onpublications that are
1325+
already subscribed could lead to errors being thrown on the subscriber
1326+
side.
1327+
</para>
1328+
<para>
1329+
If a subscription is affected by this problem, the only way to resume
1330+
replication is to adjust one ofthecolumn lists on the publication
1331+
side so that they all match; and then either recreate the subscription,
1332+
or use<literal>ALTER SUBSCRIPTION ... DROP PUBLICATION</literal>to
1333+
remove one of theoffending publications and add it again.
13281334
</para>
13291335
</warning>
13301336

1331-
</sect2>
1332-
13331337
<sect2 id="logical-replication-col-list-examples">
13341338
<title>Examples</title>
13351339

‎doc/src/sgml/mvcc.sgml

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1676,11 +1676,13 @@ SELECT pg_advisory_lock(q.id) FROM
16761676
</para>
16771677

16781678
<warning>
1679+
<title>Warning: Serializable Transactions and Data Replication</title>
16791680
<para>
16801681
This level of integrity protection using Serializable transactions
1681-
does not yet extend to hot standby mode (<xref linkend="hot-standby"/>).
1682-
Because of that, those using hot standby may want to use Repeatable
1683-
Read and explicit locking on the primary.
1682+
does not yet extend to hot standby mode (<xref linkend="hot-standby"/>)
1683+
or logical replicas.
1684+
Because of that, those using hot standby or logical replication
1685+
may want to use Repeatable Read and explicit locking on the primary.
16841686
</para>
16851687
</warning>
16861688
</sect2>

‎doc/src/sgml/ref/pg_rewind.sgml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -103,6 +103,7 @@ PostgreSQL documentation
103103
</para>
104104

105105
<warning>
106+
<title>Warning: Failures while Rewinding</title>
106107
<para>
107108
If <application>pg_rewind</application> fails while processing, then
108109
the data folder of the target is likely not in a state that can be

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp