database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-27 22:56:53 +03:00
Code

Fix grammatical errors and typos in logical replication docs.

Browse Source 
Author: Justin Pryzby
Reviewed By: Masahiko Sawada
Discussion: https://postgr.es/m/20220411020336.GB26620@telsasoft.com
This commit is contained in:
Amit Kapila 2022-04-12 14:14:32 +05:30
parent 3603f7c6e6
commit aeebb8bf23
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/sgml/logical-replication.sgml
View File

@ -363,21 +363,21 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
The LSN of the transaction that contains the change violating the constraint and The LSN of the transaction that contains the change violating the constraint and
the replication origin name can be found from the server log (LSN 0/14C0378 and the replication origin name can be found from the server log (LSN 0/14C0378 and
replication origin <literal>pg_16395</literal> in the above case). The replication origin <literal>pg_16395</literal> in the above case). The
transaction that produces conflict can be skipped by using transaction that produced the conflict can be skipped by using
<command>ALTER SUBSCRIPTION ... SKIP</command> with the finish LSN <command>ALTER SUBSCRIPTION ... SKIP</command> with the finish LSN
(i.e., LSN 0/14C0378). The finish LSN could be an LSN at which the transaction (i.e., LSN 0/14C0378). The finish LSN could be an LSN at which the transaction
is committed or prepared on the publisher. Alternatively, the transaction can is committed or prepared on the publisher. Alternatively, the transaction can
also be skipped by calling the <link linkend="pg-replication-origin-advance"> also be skipped by calling the <link linkend="pg-replication-origin-advance">
<function>pg_replication_origin_advance()</function></link> function <function>pg_replication_origin_advance()</function></link> function.
transaction. Before using this function, the subscription needs to be disabled Before using this function, the subscription needs to be disabled temporarily
temporarily either by <command>ALTER SUBSCRIPTION ... DISABLE</command> or, the either by <command>ALTER SUBSCRIPTION ... DISABLE</command> or, the
subscription can be used with the <literal>disable_on_error</literal> option. subscription can be used with the <literal>disable_on_error</literal> option.
Then, you can use <function>pg_replication_origin_advance()</function> function Then, you can use <function>pg_replication_origin_advance()</function> function
with the <parameter>node_name</parameter> (i.e., <literal>pg_16395</literal>) with the <parameter>node_name</parameter> (i.e., <literal>pg_16395</literal>)
and the next LSN of the finish LSN (i.e., 0/14C0379). The current position of and the next LSN of the finish LSN (i.e., 0/14C0379). The current position of
origins can be seen in the <link linkend="view-pg-replication-origin-status"> origins can be seen in the <link linkend="view-pg-replication-origin-status">
<structname>pg_replication_origin_status</structname></link> system view. <structname>pg_replication_origin_status</structname></link> system view.
Please note that skipping the whole transaction include skipping changes that Please note that skipping the whole transaction includes skipping changes that
might not violate any constraint. This can easily make the subscriber might not violate any constraint. This can easily make the subscriber
inconsistent. inconsistent.
</para> </para>

8
doc/src/sgml/ref/alter_subscription.sgml
View File

@ -219,13 +219,13 @@ ALTER SUBSCRIPTION <replaceable class="parameter">name</replaceable> RENAME TO <
<para> <para>
Skips applying all changes of the remote transaction. If incoming data Skips applying all changes of the remote transaction. If incoming data
violates any constraints, logical replication will stop until it is violates any constraints, logical replication will stop until it is
resolved. By using <command>ALTER SUBSCRIPTION ... SKIP</command> command, resolved. By using the <command>ALTER SUBSCRIPTION ... SKIP</command> command,
the logical replication worker skips all data modification changes within the logical replication worker skips all data modification changes within
the transaction. This option has no effect on the transactions that are the transaction. This option has no effect on the transactions that are
already prepared by enabling <literal>two_phase</literal> on already prepared by enabling <literal>two_phase</literal> on
subscriber. subscriber.
After logical replication worker successfully skips the transaction or After the logical replication worker successfully skips the transaction or
finishes a transaction, LSN (stored in finishes a transaction, the LSN (stored in
<structname>pg_subscription</structname>.<structfield>subskiplsn</structfield>) <structname>pg_subscription</structname>.<structfield>subskiplsn</structfield>)
is cleared. See <xref linkend="logical-replication-conflicts"/> for is cleared. See <xref linkend="logical-replication-conflicts"/> for
the details of logical replication conflicts. Using this command requires the details of logical replication conflicts. Using this command requires
@ -244,7 +244,7 @@ ALTER SUBSCRIPTION <replaceable class="parameter">name</replaceable> RENAME TO <
Specifies the finish LSN of the remote transaction whose changes Specifies the finish LSN of the remote transaction whose changes
are to be skipped by the logical replication worker. The finish LSN are to be skipped by the logical replication worker. The finish LSN
is the LSN at which the transaction is either committed or prepared. is the LSN at which the transaction is either committed or prepared.
Skipping individual subtransaction is not supported. Setting Skipping individual subtransactions is not supported. Setting
<literal>NONE</literal> resets the LSN. <literal>NONE</literal> resets the LSN.
</para> </para>
</listitem> </listitem>