252
252
additional columns not provided by the published table. Any such columns
253
253
will be filled with the default value as specified in the definition of the
254
254
target table. However, logical replication in binary format is more
255
- restrictive. See the <link linkend="sql-createsubscription-binary"><literal>binary</literal>
256
- option</link> of <command>CREATE SUBSCRIPTION</command> for details.
255
+ restrictive. See the
256
+ <link linkend="sql-createsubscription-with-binary"><literal>binary</literal></link>
257
+ option of <command>CREATE SUBSCRIPTION</command> for details.
257
258
</para>
258
259
259
260
<sect2 id="logical-replication-subscription-slot">
@@ -587,7 +588,9 @@ ALTER SUBSCRIPTION
587
588
588
589
<para>
589
590
Example 2: Where the subscription says <literal>connect = false</literal>,
590
- but also specifies the <literal>slot_name</literal>
591
+ but also specifies the
592
+ <link linkend="sql-createsubscription-with-slot-name"><literal>slot_name</literal></link>
593
+ option.
591
594
<itemizedlist>
592
595
<listitem>
593
596
<para>
@@ -704,9 +707,10 @@ ALTER SUBSCRIPTION
704
707
If the row filter evaluates to <literal>false</literal> or <literal>NULL</literal>
705
708
then the row is not replicated. The <literal>WHERE</literal> clause expression
706
709
is evaluated with the same role used for the replication connection (i.e.
707
- the role specified in the <literal>CONNECTION</literal> clause of the
708
- <xref linkend="sql-createsubscription"/>). Row filters have no effect for
709
- <command>TRUNCATE</command> command.
710
+ the role specified in the
711
+ <link linkend="sql-createsubscription-connection"><literal>CONNECTION</literal></link>
712
+ clause of the <xref linkend="sql-createsubscription"/>). Row filters have
713
+ no effect for <command>TRUNCATE</command> command.
710
714
</para>
711
715
712
716
</sect2>
@@ -1500,9 +1504,10 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
1500
1504
<function>pg_replication_origin_advance()</function></link> function.
1501
1505
Before using this function, the subscription needs to be disabled temporarily
1502
1506
either by <command>ALTER SUBSCRIPTION ... DISABLE</command> or, the
1503
- subscription can be used with the <literal>disable_on_error</literal> option.
1504
- Then, you can use <function>pg_replication_origin_advance()</function> function
1505
- with the <parameter>node_name</parameter> (i.e., <literal>pg_16395</literal>)
1507
+ subscription can be used with the
1508
+ <link linkend="sql-createsubscription-with-disable-on-error"><literal>disable_on_error</literal></link>
1509
+ option. Then, you can use <function>pg_replication_origin_advance()</function>
1510
+ function with the <parameter>node_name</parameter> (i.e., <literal>pg_16395</literal>)
1506
1511
and the next LSN of the finish LSN (i.e., 0/14C0379). The current position of
1507
1512
origins can be seen in the <link linkend="view-pg-replication-origin-status">
1508
1513
<structname>pg_replication_origin_status</structname></link> system view.
@@ -1512,11 +1517,13 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
1512
1517
</para>
1513
1518
1514
1519
<para>
1515
- When the streaming mode is <literal>parallel</literal>, the finish LSN of
1516
- failed transactions may not be logged. In that case, it may be necessary to
1517
- change the streaming mode to <literal>on</literal> or <literal>off</literal> and
1518
- cause the same conflicts again so the finish LSN of the failed transaction will
1519
- be written to the server log. For the usage of finish LSN, please refer to <link
1520
+ When the
1521
+ <link linkend="sql-createsubscription-with-streaming"><literal>streaming</literal></link>
1522
+ mode is <literal>parallel</literal>, the finish LSN of failed transactions
1523
+ may not be logged. In that case, it may be necessary to change the streaming
1524
+ mode to <literal>on</literal> or <literal>off</literal> and cause the same
1525
+ conflicts again so the finish LSN of the failed transaction will be written
1526
+ to the server log. For the usage of finish LSN, please refer to <link
1520
1527
linkend="sql-altersubscription"><command>ALTER SUBSCRIPTION ...
1521
1528
SKIP</command></link>.
1522
1529
</para>
@@ -1701,8 +1708,10 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
1701
1708
subscription. A disabled subscription or a crashed subscription will have
1702
1709
zero rows in this view. If the initial data synchronization of any
1703
1710
table is in progress, there will be additional workers for the tables
1704
- being synchronized. Moreover, if the streaming transaction is applied in
1705
- parallel, there may be additional parallel apply workers.
1711
+ being synchronized. Moreover, if the
1712
+ <link linkend="sql-createsubscription-with-streaming"><literal>streaming</literal></link>
1713
+ transaction is applied in parallel, there may be additional parallel apply
1714
+ workers.
1706
1715
</para>
1707
1716
</sect1>
1708
1717
0 commit comments