Merge pull request #5669 from EnterpriseDB/docs/edits_to_eprs_pr5607

Edits to EPRS PR5607
EnterpriseDB · May 22, 2024 · 6a01dcd · 6a01dcd · github-actions · May 22, 2024
2 parents 6061db7 + e0989db
commit 6a01dcd
Show file tree

Hide file tree

Showing 5 changed files with 33 additions and 34 deletions.
diff --git a/...04_design_replication_system/03_restrictions_on_replicated_database_objects.mdx b/...04_design_replication_system/03_restrictions_on_replicated_database_objects.mdx
@@ -37,7 +37,7 @@ The following are the restrictions on Oracle database objects:
 
 - You can use Oracle tables with the `RAW` data type in snapshot-only publications but not in synchronization replications.
 
-- You can include Oracle materialised views in snapshot-only publications but not in synchronization replications.
+- You can include Oracle materialized views in snapshot-only publications but not in synchronization replications.
 
 - You can't replicate Oracle tables that include the following data types:
     -   `BFILE`
@@ -179,7 +179,7 @@ HINT:  Use DROP ... CASCADE to drop the dependent objects too.
 Since Replication Server drops the constraints using the `CASCADE` option, the above error would not occur; however, the result of using this option means that the view will also be dropped.
 
 !!! Important
-    When replicating to a target PGD instance, source `ALTER TABLE` statements will not be replicated due to a documented PGD limitation.
-    For example, if you use the `ALTER TABLE` command to change a column's type, this operation won't be replicated if the command causes the whole table to be rewritten. 
+    When replicating to a target PGD instance, source `ALTER TABLE` statements aren't replicated due to a documented PGD limitation.
+    For example, if you use the `ALTER TABLE` command to change a column's type, this operation isn't replicated if the command causes the whole table to be rewritten. 
 
-    For more details, see the [PGD ALTER TABLE documentation](https://www.enterprisedb.com/docs/pgd/latest/ddl/ddl-command-handling/#alter-table).
+    For more details, see the [PGD ALTER TABLE documentation](/pgd/latest/ddl/ddl-command-handling/#alter-table).
diff --git a/...01_publications_and_subscriptions_server_conf_options/single_quote_unescape.mdx b/...01_publications_and_subscriptions_server_conf_options/single_quote_unescape.mdx
@@ -2,21 +2,21 @@
 title: "Unescaping single-quote characters"
 ---
 
-In the [Batch Update Using Prepared Statement (BUP)](/eprs/latest/05_smr_operation/08_optimizing_performance/02_optimize_sync_replication/01_using_sql_statements/) 
-mode, Replication Server adds an extra single quote character (') when it recognizes text data with single quotes during the wal-based replication.
+In [Batch Update Using Prepared Statement (BUP)](/eprs/latest/05_smr_operation/08_optimizing_performance/02_optimize_sync_replication/01_using_sql_statements/) 
+mode, Replication Server adds an extra single quote character (') when it recognizes text data with single quotes during the WAL-based replication.
 This results in an additional single quote on the target database.
 
-If there is a possibility that a source database table column contains a single quote character, 
-and you don't want the target database to contain an _additional_ single quote character, set the parameter `unescapeSingeQuote` to `true`.
+If there's a possibility that a source database table column contains a single quote character, 
+and you don't want the target database to contain an additional single quote character, set the parameter `unescapeSingeQuote` to `true`.
 
 By default, this option is disabled (`unescapeSingeQuote=false`).  
 
 ```
 unescapeSingeQuote=true
 ```
 
-When set to `true`, the option removes the single quote character that was added during the wal-based replication operation in BUP mode.
+When set to `true`, the option removes the single quote character that was added during the WAL-based replication operation in BUP mode.
 
 !!!note Note
    Enabling the `unescapeSingeQuote` option adds extra processing for each column, which can increase the replication time.
-   Therefore, enable this option only if there is a possibility that the source data contains single quotes and you configured Replication Server to use wal-based replication in BUP mode. 
+   Therefore, enable this option only if there's a possibility that the source data contains single quotes and you configured Replication Server to use WAL-based replication in BUP mode. 
diff --git a/...s/01_publications_and_subscriptions_server_conf_options/skip_default_column.mdx b/...s/01_publications_and_subscriptions_server_conf_options/skip_default_column.mdx
@@ -4,17 +4,17 @@ title: "Skipping migration of column DEFAULT clause"
 
 ## Use cases
 
-- The suscription database is in read-only mode. Therefore, DEFAULT clause columns serve no purpose as 
+- The subscription database is in read-only mode. Therefore, DEFAULT clause columns serve no purpose as 
   they are already applied on the publication database. 
   You can skip migrating DEFAULT columns for faster processing.
 
-- Sequences are not migrated during replication operations. 
-  If a DEFAULT clause depends on a Sequence, the DEFAULT clause migration will fail.
+- Sequences aren't migrated during replication operations. 
+  If a DEFAULT clause depends on a sequence, the DEFAULT clause migration will fail.
   You can skip migrating DEFAULT columns to avoid migration failures.
 
 ## Configuration
 
-To skip the replication of a DEFAULT clause, update the below option to true:  
+To skip the replication of a DEFAULT clause, set the following option to true:  
 
 ```
 skipColDefaultClause=true

diff --git a/...ublications_and_subscriptions_server_conf_options/snapshot_connection_retry.mdx b/...ublications_and_subscriptions_server_conf_options/snapshot_connection_retry.mdx
@@ -3,42 +3,41 @@ title: "Snapshot replication connection retry"
 ---
 
 When a connection failure with the subscription database occurs during a snapshot replication, 
-the Replication Server automatically attempts to reconnect to it. 
-The goal is that the snapshot replication completes without skipping any tables. When the connection is reestablished, 
-Replication Server restarts or resumes the snapshot replication procedure for the table that was being migrated when the connection was lost and then performs the data copy for the remaining tables.
+Replication Server attempts to reconnect to it. 
+The goal is for the snapshot replication to complete without skipping any tables. When the connection is reestablished, 
+Replication Server restarts or resumes the snapshot replication procedure for the table that was being migrated when the connection was lost. It then performs the data copy for the remaining tables.
 
 !!!note Scope and limitations
 
    Database scope: The connection retry capability allows Replication Server to reconnect to the target/subscription database. 
-   Retry attempts for connection issues with the source/publication database are not supported.
+   Retry attempts for connection issues with the source/publication database aren't supported.
 
    Replication scope: This capability allows Replication Server to retry replicating data. 
-   Issues with schema replication are not supported.
+   Issues with schema replication aren't supported.
 !!!   
 
 You can specify several connection retry options:
 
 - `-snapshotConnRetryCount [<connection_attempts>]`
 
-Use the `-snapshotConnRetryCount` option to specify the number of retry attempts to perform in case the subscription database connection fails in a Snapshot session. 
-The `[<connection_attempts>]` value must be a number between 0 and 50, the default is 3 retry attempts. 
+Use the `-snapshotConnRetryCount` option to specify the number of retry attempts to perform if the subscription database connection fails in a snapshot session. 
+The `[<connection_attempts>]` value must be a number between 0 and 50. The default is 3 retry attempts. 
 
 - `-snapshotConnRetryInterval [<seconds>]`
 
 Use the `-snapshotConnRetryInterval` option to specify the seconds to wait before each subsequent reconnection attempt 
-in case the connection to the subscription database fails in a Snapshot session. 
-The `[<seconds>]` value must be a number between 0 and 900, the default is 30 seconds. 
+if the connection to the subscription database fails in a snapshot session. 
+The `[<seconds>]` value must be a number between 0 and 900. The default is 30 seconds. 
 
 - `-snapshotAbortOnConnFailure [true/false]`
 
-Specify if to abort the Snapshot replication if all the reconnection attempts fail. 
+Specify whether to abort the snapshot replication if all the reconnection attempts fail. 
 
-Set the `-snapshotAbortOnConnFailure` to `false`, to skip replicating the failed table and proceed to the next table. 
-The default is `true`, which aborts the Snapshot session if the connection fails after the specified `-snapshotConnRetryCount` threshold.
+To skip replicating the failed table and proceed to the next table, set `-snapshotAbortOnConnFailure` to `false`. 
+The default is `true`, which aborts the snapshot session if the connection fails after the specified `-snapshotConnRetryCount` threshold.
 
 - `-snapshotPGIdleTxSessionTimeOut [<seconds>]`
 
-Specify the `idle_in_transaction_session_timeout`, which defines the time after which
+Specify `idle_in_transaction_session_timeout`, which defines the time after which
 the subscription database terminates the session when a snapshot replication transaction is in idle state. 
-The `[<seconds>]` value should be greater than 0, and the default is 180 seconds.
-
+The `[<seconds>]` value must be greater than 0. The default is 180 seconds.
diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.8.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.8.0.mdx
@@ -13,14 +13,14 @@ New features, enhancements, bug fixes, and other changes in Replication Server 7
 | Enhancement | Added the `skipColDefaultClause` subscription server configuration option to skip the column DEFAULT value for the subscription database.                                                                                                   | #100987/32874              |
 | Enhancement | EDB Postgres Replication Server now provides packages and support for installations on SLES15 SP5.                                                                                                                                          |                            |
 | Bug Fix     | Fixed an issue where the synchronization cycle gets stuck for a case when a transaction is rolled back with SQL Server as the publication database.                                                                                         | #96964/29244               |
-| Bug Fix     | Fixed an issue where columns containing single quotes are not replicated properly for wal-based replication when Batch Update Using Prepared Statement mode is used. Introduced the `unescapeSingeQuote` option to control this processing. | #94921/27387, #95823/28200 |
-| Bug Fix     | Fixed an issue where some of the views' owners are changed after a snapshot.                                                                                                                                                                | #102472/34206              |
+| Bug Fix     | Fixed an issue where columns containing single quotes aren't replicated properly for WAl-based replication when Batch Update Using Prepared Statement mode is used. Introduced the `unescapeSingeQuote` option to control this processing. | #94921/27387, #95823/28200 |
+| Bug Fix     | Fixed an issue where some of the views' owners were changed after a snapshot.                                                                                                                                                                | #102472/34206              |
 | Bug Fix     | Fixed an error observed during the removal of a SQL Server publication database.                                                                                                                                                            |                            |
 
 ## End-of-support notice
 
-We recommend you update to the most recent software version. 
-*If you have not yet updated to the most current version, please see the end-of-support notes below*: 
+We recommend that you update to the most recent software version. 
+*If you haven't yet updated to the most current version, see the end-of-support notes that follow*: 
 
 **Software:** Replication Server 
 
@@ -31,4 +31,4 @@ We recommend you update to the most recent software version.
 Additional details can be found at [EDB Platform Compatibility](https://www.enterprisedb.com/resources/platform-compatibility).
 
 !!! Note
-    Version 7.x provides a non-breaking upgrade path for existing 6.2.x-based cluster deployments; however, we strongly recommend that the upgrade be verified in a staging or non-production environment before applying the upgrade in a production environment.
+    Version 7.x provides a non-breaking upgrade path for existing 6.2.x-based cluster deployments. However, we strongly recommend that the upgrade be verified in a staging or non-production environment before applying the upgrade in a production environment.