Merge pull request #4803 from EnterpriseDB/release/2023-09-08a

Release: 2023-09-08a
EnterpriseDB · Sep 8, 2023 · 3ee32d8 · 3ee32d8 · github-actions · Sep 8, 2023
2 parents f7a08d1 + 4a0d444
commit 3ee32d8
Show file tree

Hide file tree

Showing 16 changed files with 64 additions and 53 deletions.
diff --git a/advocacy_docs/supported-open-source/postgresql/overview.mdx b/advocacy_docs/supported-open-source/postgresql/overview.mdx
@@ -18,7 +18,7 @@ EDB also makes PostgreSQL Early Experience distributions available. For details,
 
 ## EDB Language Pack installer
 
-You can use the EDB Language Pack installer with PostgreSQL installations and EDB Postgres Advanced Server installations. For details, see the [Language Pack documentation](/epas/latest/language_pack/).
+You can use the EDB Language Pack installer with PostgreSQL installations and EDB Postgres Advanced Server installations. For details, see the [Language Pack documentation](/language_pack/latest/).
 
 
 

diff --git a/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx b/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx
@@ -1,5 +1,6 @@
 ---
 title: "Uninstalling PostgreSQL"
+navTitle: "Uninstalling"
 legacyRedirects:
   - "/edb-docs/d/postgresql/installation-getting-started/installation-guide/13.0/uninstalling_postgresql.html"
   - "/edb-docs/d/postgresql/installation-getting-started/installation-guide-installers/11/PostgreSQL_Installation_Guide.1.10.html"
@@ -51,17 +52,15 @@ These instructions apply if you used EDB's interactive Mac installer to install
 
 To uninstall PostgreSQL on a Mac system:
 
-1.  Assume the identity of an operating system superuser, and navigate into the folder where the uninstaller resides:
-
-  `/Library/PostgreSQL/<version>`
-
-  Where `version` is the version of PostgreSQL you installed.
-
 1.  Invoke the uninstaller:
 
-  `open uninstall-postgresql.app`
+    ```
+    open /Library/PostgreSQL/<version>/uninstall-postgresql.app
+    ```
+
+    Where `<version>` is the version of PostgreSQL you installed.
 
-1.  If prompted, provide a password that allows the uninstaller to make changes to your system. 
+1.  You're prompted for a password. If your user has admin rights on macOS, enter your password. Otherwise, enter the user name and password of a user with admin rights. 
 
   The uninstaller opens and asks if you want to uninstall the entire application or individual components.
 

diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx
@@ -121,7 +121,7 @@ To create the cluster using the sample configuration file `config_file.yaml`:
 biganimal cluster create --config-file "./config_file.yaml"
 ```
 
-To view valid values you can use in the configuration file for BigAnimal and cloud service provider-related properties, the CLI provides a series of cluster subcommands. For example, you can use `cluster show-architectures` to list all BigAnimal database architectures available within your cloud service provider account:
+To enable you to view valid values to use in the configuration file for BigAnimal and cloud service provider-related properties, the CLI provides a series of cluster subcommands. For example, you can use `cluster show-architectures` to list all BigAnimal database architectures available in your cloud service provider account:
 
 ```shell
 biganimal cluster show-architectures

diff --git a/product_docs/docs/efm/4/05_using_efm.mdx b/product_docs/docs/efm/4/05_using_efm.mdx
@@ -81,7 +81,7 @@ When the new node joins the cluster, Failover Manager sends a notification to th
 
 If your Failover Manager cluster includes more than one standby server, you can use the `efm set-priority` command to influence the promotion priority of a standby node. Invoke the command on any existing member of the Failover Manager cluster, and specify a priority value after the IP address of the member.
 
-For example, the following command instructs Failover Manager that the `acctg` cluster member that is monitoring `10.0.1.9` is the primary standby `(1)`:
+For example, the following command instructs Failover Manager that the `acctg` cluster member that's monitoring `10.0.1.9` is the primary standby `(1)`:
 
 ```shell
 efm set-priority acctg 10.0.1.9 1
@@ -184,7 +184,7 @@ The command causes all Failover Manager agents to exit. Terminating the Failover
 
 ### Removing a node from a cluster
 
-The `efm disallow-node` command removes the IP address of a node from the Failover Manager Allowed Node host list. Assume the identity of efm or the OS superuser on any existing node that is currently part of the running cluster. Then invoke the `efm disallow-node` command, specifying the cluster name and the IP address of the node:
+The `efm disallow-node` command removes the IP address of a node from the Failover Manager Allowed Node host list. Assume the identity of efm or the OS superuser on any existing node that's currently part of the running cluster. Then invoke the `efm disallow-node` command, specifying the cluster name and the IP address of the node:
 
 `efm disallow-node <cluster_name> <address>`
 
@@ -265,9 +265,9 @@ After creating the `acctg.properties` and `sales.properties` files, create a ser
 
 ### RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
 
-If you're using RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, copy the service file `/usr/lib/systemd/system/edb-efm-4.<x>.service` to `/etc/systemd/system` with a new name that is unique for each cluster.
+If you're using RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, copy the service file `/usr/lib/systemd/system/edb-efm-4.<x>.service` to `/etc/systemd/system` with a new name that's unique for each cluster.
 
-For example, if you have two clusters named `acctg` and `sales` managed by Failover Manager 4.7, the unit file names might be `efm-acctg.service` and `efm-sales.service`, and they can be created with:
+For example, if you have two clusters named `acctg` and `sales` managed by Failover Manager 4.7, the unit file names might be `efm-acctg.service` and `efm-sales.service`. You can create them with:
 
 ```shell
 cp /usr/lib/systemd/system/edb-efm-4.7.service /etc/systemd/system/efm-acctg.service
@@ -277,15 +277,15 @@ cp /usr/lib/systemd/system/edb-efm-4.7.service /etc/systemd/system/efm-sales.ser
 Then use `systemctl edit` to edit the `CLUSTER` variable in each unit file, changing the specified cluster name from `efm` to the new cluster name.
 Also update the value of the `PIDfile` parameter to match the new cluster name.
 
-In our example, edit the `acctg` cluster by running `systemctl edit efm-acctg.service` and write:
+In this example, edit the `acctg` cluster by running `systemctl edit efm-acctg.service` and write:
 
 ```ini
 [Service]
 Environment=CLUSTER=acctg
 PIDFile=/run/efm-4.7/acctg.pid
 ```
 
-And edit the `sales` cluster by running `systemctl edit efm-sales.service` and write:
+Edit the `sales` cluster by running `systemctl edit efm-sales.service` and write:
 
 ```ini
 [Service]
@@ -294,7 +294,7 @@ PIDFile=/run/efm-4.7/sales.pid
 ```
 
 !!!Note
-You could also have edited the files in `/etc/systemd/system` directly, but then you'll have to run `systemctl daemon-reload`, which is unecessary when using `systemd edit` to change the override files.
+You can also edit the files in `/etc/systemd/system` directly, but then you have to run `systemctl daemon-reload`. This step is unecessary when using `systemd edit` to change the override files.
 !!!
 
 After saving the changes, enable the services:

diff --git a/product_docs/docs/efm/4/13_troubleshooting.mdx b/product_docs/docs/efm/4/13_troubleshooting.mdx
@@ -48,8 +48,8 @@ OpenJDK Runtime Environment (build 1.8.0_191-b12)
 OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)
 ```
 !!! Note
-    There is a temporary issue with OpenJDK version 11 on RHEL and its derivatives. When starting Failover Manager, you may see an error like the following:
+    There's a temporary issue with OpenJDK version 11 on RHEL and its derivatives. When starting Failover Manager, you might see an error like the following:
 
     `java.lang.Error: java.io.FileNotFoundException: /usr/lib/jvm/java-11-openjdk-11.0.20.0.8-2.el8.x86_64/lib/tzdb.dat (No such file or directory)`
 
-    If so, the workaround is to manually install the missing package using the command `sudo dnf install tzdata-java`
+    If you see this message, the workaround is to manually install the missing package using the command `sudo dnf install tzdata-java`.
diff --git a/product_docs/docs/efm/4/installing/prerequisites.mdx b/product_docs/docs/efm/4/installing/prerequisites.mdx
@@ -18,11 +18,11 @@ Before configuring a Failover Manager cluster, you must satisfy the prerequisite
 Before using Failover Manager, you must first install Java (version 1.8 or later). Failover Manager is tested with OpenJDK, and we strongly recommend installing that version of Java. [Installation instructions for Java](https://openjdk.java.net/install/) are platform specific.
 
 !!! Note
-    There is a temporary issue with OpenJDK version 11 on RHEL and its derivatives. When starting Failover Manager, you may see an error like the following:
+    There's a temporary issue with OpenJDK version 11 on RHEL and its derivatives. When starting Failover Manager, you might see an error like the following:
 
     `java.lang.Error: java.io.FileNotFoundException: /usr/lib/jvm/java-11-openjdk-11.0.20.0.8-2.el8.x86_64/lib/tzdb.dat (No such file or directory)`
 
-    If so, the workaround is to manually install the missing package using the command `sudo dnf install tzdata-java`
+    If you see this message, the workaround is to manually install the missing package using the command `sudo dnf install tzdata-java`.
 
 ## Provide an SMTP server
 

diff --git a/product_docs/docs/eprs/7/01_introduction/03_certified_supported_versions.mdx b/product_docs/docs/eprs/7/01_introduction/03_certified_supported_versions.mdx
@@ -13,7 +13,7 @@ You can use the following database product versions with Replication Server:
 -   SQL Server 2014 version 12.0.5000.0 is explicitly certified. Newer minor versions in the 12.0 line are supported as well.
 
 !!!Note
-   All PostgreSQL and EDB Postgres Advanced Server versions available as BigAnimal single-node and primary/standby high availability cluster types are also supported for SMR configurations. Consult the BigAnimal (EDB’s managed database cloud service) [documentation](/biganimal/latest) for more information about BigAnimal’s [supported cluster types](/biganimal/latest/overview/02_high_availability/) and [database version policy](/biganimal/latest/overview/05_database_version_policy/) for the versions of PostgreSQL and EDB Postgres Advanced Server available in BigAnimal.
+   All PostgreSQL and EDB Postgres Advanced Server versions available as BigAnimal single-node and primary/standby high-availability cluster types are also supported for SMR configurations. See the BigAnimal (EDB’s managed database cloud service) [documentation](/biganimal/latest) for more information about BigAnimal’s [supported cluster types](/biganimal/latest/overview/02_high_availability/). See the [database version policy documentation](/biganimal/latest/overview/05_database_version_policy/) for the versions of PostgreSQL and EDB Postgres Advanced Server available in BigAnimal.
 
 
 As of Replication Server 7.1.0:

diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/52_reload_conf_file.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/52_reload_conf_file.mdx
@@ -86,7 +86,7 @@ The table shows whether a configuration property can be reloaded.
 This example reloads the configuration file.
 
 !!! Note Note
-When you execute the reloadconf command, if any configuration options have been changed from their default values, the output includes the configuration option and its new value. 
+When you execute the `reloadconf` command, if any configuration options were changed from their default values, the output includes the configuration option and its new value. 
 
 ```shell
 java -jar edb-repcli.jar -reloadconf -repsvrfile subsvr.prop

diff --git a/...ications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx b/...ications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx
@@ -67,7 +67,7 @@ Set the `logging.default.locale` option to use either the current system locale
 The default value is `system`.
 
 !!!Note
-This option is only applicable for publication and subscription logs and isn't supported for mtk.log.
+This option is applicable only for publication and subscription logs and isn't supported for `mtk.log`.
 
 The RepCLI and RepConsole logs continue showing text in the default locale.
 !!!

diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.6.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.6.0.mdx
@@ -9,14 +9,14 @@ New features, enhancements, bug fixes, and other changes in Replication Server 7
 
 | Type    | Description |
 | ------- |------------ |
-| Enhancement | EDB Replication Server now supports logging Publication and Subscription server logs in the English language, overriding the default locale, using the `logging.default.locale` configuration parameter. [Support ticket #89877]                                                                                                                                                                                   |   
-| Enhancement | The snapshot operation now uses the table-level parallel loading capability, which reduces overhead on the source database by using range-based criterion for loading each individual table data chunk instead of a fetch-offset approach. This optimization is applicable when the table primary key/unique constraint is based on a non-composite numeric type attribute. [Support ticket # 93360] |   
+| Enhancement | EDB Replication Server now supports logging publication and subscription server logs in the English language, overriding the default locale, by way of the `logging.default.locale` configuration parameter. [Support ticket #89877]                                                                                                                                                                                   |   
+| Enhancement | The snapshot operation now uses the table-level parallel loading capability. This capability reduces overhead on the source database by using range-based criterion for loading each individual table data chunk instead of a fetch-offset approach. This optimization applies when the table primary key/unique constraint is based on a noncomposite numeric type attribute. [Support ticket # 93360] |   
 | Enhancement | To help investigate data synchronization gaps, Replication Server’s logging now logs when rows are skipped due to filter criteria.  [Support ticket #91296]                                                                                                                                                                                                                                      |   
 | Bug fix     | Fixed an issue where metadata from the primary controller database wasn't replicated when a SQL Server or an Oracle publication database is added as a standby controller database.  [Support ticket #82050 and #91884]                                                                                                                                                                                        |   
-| Bug fix     | Fixed the issues related to foreign key violations in the standby controller database that prevented upgrading from version 6.2.x to 7.x. [Support ticket #93129, #92056 and #91588]                                                                                                                                                                                                                           |   
+| Bug fix     | Fixed the issues related to foreign key violations in the standby controller database that prevented upgrading from version 6.2.x to 7.x. [Support ticket #93129, #92056, and #91588]                                                                                                                                                                                                                           |   
 | Bug fix     | Corrected a few code paths to release unused resources for timely garbage collection and optimized memory utilization. [Support ticket #91588]                                                                                                                                                                                                                                                                  |   
-| Bug fix     | Fixed a Data Validator Oracle edge case resulting in a `String index out of range` error for an Oracle to EDB Postgres Advanced Server validation.                                                                                                                                                                                                                                                                                          |   
-| Bug fix     | Fixed an issue resulting in a synchronization failure for `nchar`, `nvarchar`, `xml`, and `sqlvariant` when using the mssql-jdbc-10.2.1.jre8.jar file for a SQL Server to EDB Postgres Advanced Server cluster setup.                                                                                                                                                                                                                             |   
-| Bug fix     | Updated database type name references of “Postgres Plus Advanced Server” in the Replication Console and Replication CLI to “EDB Postgres Advanced Server”.                                                                                                                                                                                                                                                        |   
-| Bug fix     | Fixed an issue that prevented logging of changed configuration parameters at Publication and Subscription server start or when the `reloadconf` command is executed.                                                                                                                                                                                                                                                |   
-| Bug fix     | Fixed a regression that led to an `Invalid custom column type mapping` error being observed for Publication tables with no column mapping.                                                                                                                                                                                                                                                                          |   
+| Bug fix     | Fixed a data validator Oracle edge case resulting in a `String index out of range` error for an Oracle-to-EDB Postgres Advanced Server validation.                                                                                                                                                                                                                                                                                          |   
+| Bug fix     | Fixed an issue resulting in a synchronization failure for `nchar`, `nvarchar`, `xml`, and `sqlvariant` when using the `mssql-jdbc-10.2.1.jre8.jar` file for a SQL Server-to-EDB Postgres Advanced Server cluster setup.                                                                                                                                                                                                                             |   
+| Bug fix     | Updated database type name references of “Postgres Plus Advanced Server” in the Replication Console and Replication CLI to “EDB Postgres Advanced Server.”                                                                                                                                                                                                                                                        |   
+| Bug fix     | Fixed an issue that prevented logging of changed configuration parameters at publication and subscription server start or when the `reloadconf` command is executed.                                                                                                                                                                                                                                                |   
+| Bug fix     | Fixed a regression that led to an `Invalid custom column type mapping` error being observed for publication tables with no column mapping.                                                                                                                                                                                                                                                                          |
Original file line number	Diff line number	Diff line change
Expand Up		@@ -18,7 +18,7 @@ EDB also makes PostgreSQL Early Experience distributions available. For details,

		## EDB Language Pack installer

		You can use the EDB Language Pack installer with PostgreSQL installations and EDB Postgres Advanced Server installations. For details, see the [Language Pack documentation](/epas/latest/language_pack/).
		You can use the EDB Language Pack installer with PostgreSQL installations and EDB Postgres Advanced Server installations. For details, see the [Language Pack documentation](/language_pack/latest/).



Expand Down