Merge pull request #3989 from EnterpriseDB/release/2023-04-26

Release: 2023-04-26

gatsby-config.js

@@ -76,6 +76,7 @@ const sourceToPluginConfig = {
     name: "pg_extensions",
     path: "advocacy_docs/pg_extensions",
   },
+  "CloudNativePG": { name: "CloudNativePG", path:"advocacy_docs/supported-open-source/cloud_native_pg"},
   pgpool: { name: "pgpool", path: "product_docs/docs/pgpool" },
   postgis: { name: "postgis", path: "product_docs/docs/postgis" },
   repmgr: { name: "repmgr", path: "product_docs/docs/repmgr" },

product_docs/docs/bart/2.6/bart_inst/02_installing_bart.mdx

@@ -8,7 +8,7 @@ legacyRedirectsGenerated:
 
 This section will walk you through performing a fresh installation of BART on a host. Installation instructions are organized into the following platform/installer specific sections:
 
--   [Installing BART on a CentOS/Rocky Linux/AlmaLinux Host](#installing-bart-on-a-centos-host)
+-   [Installing BART on a CentOS/Rocky Linux/AlmaLinux Host](#installing-bart-on-a-centosrocky-linuxalmalinux-host)
 -   [Installing BART on a RHEL Host](#installing-bart-on-a-rhel-host)
 -   [Installing BART on a CentOS or RHEL Host](#installing-bart-on-a-rhelcentos-7-ppcle-host)
 -   [Installing BART on a Debian or Ubuntu Host](#installing-bart-on-a-debian-or-ubuntu-host)

product_docs/docs/bart/2.6/bart_inst/index.mdx

@@ -34,7 +34,7 @@ This guide provides information about how to install and configure the EDB Backu
 
 You require the following components to install BART.
 
--   BART Host Components - Use EDB packages to add BART host components; see [Installing BART](02_installing_bart/#installing-bart) for information about how to install these components.
+-   BART Host Components - Use EDB packages to add BART host components; see [Installing BART](02_installing_bart/) for information about how to install these components.
 
 -   Additional Components - In addition to the BART host components, the following components are required:
 

product_docs/docs/bart/2.6/bart_migration/04_executing.mdx

@@ -13,9 +13,9 @@ Execution of the migration can be very straight forward. The steps include:
 
 2.  Installing the new tool on the backup server.
 
-3.  Configuring the configuration file for the new tool. See  [How features are configured](#how-features-are-configured) for more information on changing a configuration file for one tool to another tool.
+3.  Configuring the configuration file for the new tool. See  [How features are configured](02_configuring#how-features-are-configured) for more information on changing a configuration file for one tool to another tool.
 
-4.  Reconfiguring the scheduling. See [Scheduling](#scheduling) for more information on changing the scheduling from one tool to another tool.
+4.  Reconfiguring the scheduling. See [Scheduling](06_scheduling) for more information on changing the scheduling from one tool to another tool.
 
 5.  Checking the configuration:
 

product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx

@@ -53,7 +53,7 @@ You can modify the data groups in your extreme-high-availability cluster by edit
 
 1. Select **Edit** next to the data group. 
 
-1. Edit the cluster settings in the **Data Groups** tab. See the table in [Modify your cluster](#modify-your-cluster).
+1. Edit the cluster settings in the **Data Groups** tab. See the table in [Modify your cluster configuration settings](#modify-your-clusters-configuration-settings).
 
 1. Select **Save**. 
 

product_docs/docs/biganimal/release/using_cluster/04_backup_and_restore.mdx

@@ -60,5 +60,5 @@ You can restore one data group from a PGD cluster into a new PGD cluster. To res
    1. Select the data group you want to restore. You can restore only one data group into a new cluster.
    1. Select **Fully Restore** or **Point in Time Restore**. A point-in-time restore restores the data group as it was at the specified date and time. 
 1. In the **Nodes** section, select **Two Data Nodes** or **Three Data Nodes**. For more information on node architecture, see [Extreme high availability](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-preview).
-1. Follow Steps 3-5 in [Create an extreme-high-availability cluster](../getting_started/creating_a_cluster/creating_an_eha_cluster). 
+1. Follow Steps 3-5 in [Creating an extreme-high-availability cluster](../getting_started/creating_a_cluster/creating_an_eha_cluster/). 
 1. Select **Restore**.

product_docs/docs/eprs/7/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx

@@ -100,7 +100,7 @@ The following table contains a brief description of the parameters in the replic
 Replication Server creates the content of this file as follows:
 
 -   The replication configuration file and some of its initial content are created when you install a publication server or subscription server on a host during the Replication Server installation process.
--   Parameters `admin_user` and `admin_password` are determined during the Replication Server installation process. See [Installation and uninstallation](../../installing/#installation) for how the content of these parameters are determined.
+-   Parameters `admin_user` and `admin_password` are determined during the Replication Server installation process. See [Installation and uninstallation](../../installing/) for how the content of these parameters are determined.
 -   Parameters `database`, `user`, `password`, `port`, `host`, and `type` are set with the connection and authentication information of the first publication database definition you create with the Replication Server console or CLI. This database is designated as the controller database (see [Controller database](#controller-database)). See [Adding a publication database](../../05_smr_operation/02_creating_publication/02_adding_pub_database/#adding_pub_database) for creating a publication database definition for a single-master replication system. See [Adding the primary definition node](../../06_mmr_operation/02_creating_publication_mmr/#adding_pdn) for creating the publication database definition for a multi-master replication system.
 
 The following is an example of the content of an EPRS Replication Configuration file:

product_docs/docs/eprs/7/08_xdb_cli/01_prereq_steps.mdx

@@ -8,7 +8,7 @@ Perform these installation and setup steps before using the Replication Server C
 
 The Replication Server CLI is included if you choose the Replication Server console component when installing Replication Server. The Replication Server CLI is a Java application found in the directory `XDB_HOME/bin`.
 
-1.  Follow the installation steps in [Installation and uninstallation](../installing/#installation) to install Replication Server.
+1.  Follow the installation steps in [Installation and uninstallation](../installing/) to install Replication Server.
 
 1.  Follow the prerequisite steps in [Prerequisite steps](../05_smr_operation/01_prerequisites/) for single-master replication systems or [Prerequisite steps](../05_smr_operation/01_prerequisites/#prerequisites) for multi-master replication systems.
 

product_docs/docs/eprs/7/installing/installation_details.mdx

@@ -11,7 +11,7 @@ On Windows systems, the publication server and subscription server run as servic
 
 ## Linux details
 
-On Linux hosts where you installed Replication Server with the graphical user interface or from the command line, you should now have a publication server daemon and a subscription server daemon running on your computer, assuming you chose to install the publication server and subscription server components. If you installed the Replication Server RPM package, you must start the publication server and the subscription server based on the instructions in [Registering a Publication Server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) for the publication server and [Registering a Subscription Server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server) for the subscription server.
+On Linux hosts where you installed Replication Server with the graphical user interface or from the command line, you should now have a publication server daemon and a subscription server daemon running on your computer, assuming you chose to install the publication server and subscription server components. If you installed the Replication Server RPM package, you must start the publication server and the subscription server based on the instructions in [Registering a Publication Server](../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) for the publication server and [Registering a Subscription Server](../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server) for the subscription server.
 
 !!! Note
     On some Linux systems, you may have to restart the server before you can see the EPRS Replication Console choice in the application menu. If the Replication Console choice is still unavailable in the application menu, it can be started by invoking the script `XDB_HOME/bin/runRepConsole.sh`.

product_docs/docs/pem/9/in_app_help.mdx

@@ -54,6 +54,33 @@ redirects:
 - /pem/latest/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/10_table_dialog/
 - /pem/latest/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/11_trigger_dialog/
 - /pem/latest/pem_online_help/05_toc_pem_management_basics/12_modifying_tables/12_unique_constraint_dialog/
+- /pem/latest/pem_online_help/01_toc_pem_getting_started/05_group_dialog/
+- /pem/latest/pem_online_help/01_toc_pem_getting_started/11_connect_error/
+- /pem/latest/pem_online_help/02_toc_pem_agent/04_pem_agent_ha/
+- /pem/latest/pem_online_help/03_toc_pem_client/02_pem_toolbar/
+- /pem/latest/pem_online_help/03_toc_pem_client/04_preferences/
+- /pem/latest/pem_online_help/03_toc_pem_client/05_keyboard_shortcuts/
+- /pem/latest/pem_online_help/03_toc_pem_client/06_search_objects/
+- /pem/latest/pem_online_help/04_toc_pem_features/
+- /pem/latest/pem_online_help/05_toc_pem_management_basics/10_managing_cluster_objects/
+- /pem/latest/pem_online_help/06_toc_pem_bart_management/07_bart_backup_dialog/
+- /pem/latest/pem_online_help/08_toc_pem_developer_tools/
+- /pem/latest/pem_online_help/08_toc_pem_developer_tools/01_debugger/
+- /pem/latest/pem_online_help/08_toc_pem_developer_tools/03_pem_interpreting_graphical_query/
+- /pem/latest/pem_online_help/08_toc_pem_developer_tools/04_editgrid/
+- /pem/latest/pem_online_help/08_toc_pem_developer_tools/04_editgrid/01_viewdata_filter/
+- /pem/latest/pem_online_help/10_pgagent/
+- /pem/latest/pem_online_help/10_pgagent/01_using_pgagent/
+- /pem/latest/pem_online_help/10_pgagent/02_pgagent_install/
+- /pem/latest/pem_online_help/10_pgagent/03_pgagent_jobs/
+- /pem/latest/pem_online_help/10_pgagent/04_pgagent-steps/
+- /pem/latest/pem_online_help/10_pgagent/05_pgagent-schedules/
+- /pem/latest/pem_online_help/11_appendices/
+- /pem/latest/pem_online_help/11_appendices/01_licence/
+- /pem/latest/pem_online_help/11_appendices/02_kerberos/
+- /pem/latest/pem_online_help/11_appendices/03_openssl/
+- /pem/latest/pem_online_help/11_appendices/04_snmp++/
+- /pem/latest/pem_online_help/11_appendices/05_jquery_table_sort/
 ---
 
 The in-app help provides comprehensive details about the PEM web interface, including the menu items, charts and graphs on the dashboards, and the options on the dialog boxes. The in-app help also includes instructions for creating database objects.

product_docs/docs/pem/9/managing_pem_server.mdx

@@ -27,7 +27,7 @@ Some of the tasks related to managing the PEM server include:
 
 ## Starting and stopping the PEM server and agents
 
-The PEM server starts, stops, and restarts when the Postgres server instance on where it resides starts, stops, or restarts. Use the same commands to control the PEM server that you use to control the Postgres server. On Linux platforms, the command that stops and starts the service script varies by platform and OS version.
+The PEM server starts, stops, and restarts when the Postgres server instance where it resides starts, stops, or restarts. Use the same commands to control the PEM server that you use to control the Postgres server. On Linux platforms, the command that stops and starts the service script varies by platform and OS version.
 
 The PEM agent is controlled by a service named pemagent.
 
@@ -49,7 +49,7 @@ Where `x` indicates the server version number.
 
 You can use the service script to control the service.
 
--   To control a service on RHEL or CentOS version 7.x or 8.x, at the command prompt, assume superuser privileges and issue the command:
+To control a service on RHEL or CentOS version 7.x or 8.x, at the command prompt, assume superuser privileges and issue the command:
 
     ```shell
     systemctl <service_name> <action>
@@ -148,15 +148,15 @@ PEM provides an interface for managing your Postgres roles and servers.
 
 ### Login roles
 
-When you connect to the PEM server, you must provide role credentials that allow access to the database on which the PEM server stores data. By default, the postgres superuser account is used to initially connect to the server, but it is strongly recommended (for both security and auditing purposes) that individual roles are created for each connecting user. You can use the PEM Query tool, the PEM web interface `Create – Login/Group Role` dialog, or a command line client (such as psql) to create a role.
+When you connect to the PEM server, you must provide role credentials that allow access to the database on which the PEM server stores data. By default, the postgres superuser account is used to initially connect to the server, but we strongly recommend (for both security and auditing purposes) creating individual roles for each connecting user. You can use the PEM Query tool, the PEM web interface Create – Login/Group Role dialog box, or a command line client (such as psql) to create a role.
 
 To use the Create – Login/Group Role dialog box to create a role:
 
 1.  In the PEM tree, expand the node for the server where you want to create the role.
 1.  Right-click the **Login/Group Roles** node. 
 1.  From the context menu, select **Create > Login/Group Role**.
 1.  Use the tabs of the Create – Login/Group Role dialog box to define the role. 
-1.  After you finish defining the new role, select **Save** to create the role.
+1.  After you finish defining the new role, to create the role, select **Save**.
 
 To modify the properties of an existing login role, right-click the name of a login role in the tree and select **Properties** from the context menu. To delete a login role, right-click the name of the role and select **Delete/Drop** from the context menu.
 
@@ -172,16 +172,16 @@ Use the **Group Roles** node (located beneath the name of each registered server
 
 You can use the Login/Group Role dialog box to allow a role with limited privileges to access PEM features such as the Audit Manager, Capacity Manager, or SQL Profiler. PEM predefined roles allow access to PEM functionality. Roles that are assigned membership in these roles can access the associated feature.
 
-When defining a user, use the **Membership** tab to specify the roles in which the new user is a member. The new user shares the privileges associated with each role in which it is a member. For a user to have access to PEM extended functionality, the role must be a member of the pem_user role and the predefined role that grants access to the feature. Use the **Roles** field to select predefined role names from a list.
+When defining a user, use the **Membership** tab to specify the roles in which the new user is a member. The new user shares the privileges associated with each role in which it's a member. For a user to have access to PEM extended functionality, the role must be a member of the pem_user role and the predefined role that grants access to the feature. Use the **Roles** field to select predefined role names from a list.
 
 The **SQL** tab displays the SQL command that the server executes when you select **Save**.
 
-This example creates a login role named acctg_clerk that has access to the Audit Manager. The role can make unlimited connections to the server at any given time.
+This example creates a login role named acctg_clerk that has access to Audit Manager. The role can make unlimited connections to the server at any given time.
 
 ![Create Login Role - SQL tab](images/role_sql.png)
 <!--Don't delete this image since its contents are referred to in the text -->
 
-You can use PEM predefined roles to allow access to the functionality listed in the table.
+You can use PEM predefined roles to allow access to the capabilities listed in the table.
 
 | Value                            | Parent role                  | Description                                                                                                                                                                                                                                                                   |
 | -------------------------------- | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -234,6 +234,14 @@ Object permissions are managed with the graphical object editor for each particu
 
 The PEM client also contains a Grant wizard (accessed through the **Tools** menu) that allows you to manage many object permissions at once.
 
+## Server configuration
+
+You can use the Server Configuration dialog box to modify values of user-configurable parameters that control PEM behavior. To access the Server Configuration dialog box, connect to the PEM server, and select **File > Server Configuration**.
+
+Enter a parameter name in the search box in the upper-right corner of the dialog to locate a specific parameter in the list.
+
+To modify a parameter value, edit the content displayed in the **Value** field to the right of a parameter name. To save your changes, select the **Save** icon in the upper-right corner of the dialog box.
+
 ## Server configuration parameters - reference
 
 You can use global configuration options to modify aspects of the PEM Server's behavior. The list of configuration parameters is subject to change.