Merge pull request #3964 from EnterpriseDB/release/2023-04-21

Release: 2023-04-21
EnterpriseDB · Apr 21, 2023 · cb3aa1b · cb3aa1b · github-actions · Apr 21, 2023
2 parents 443b2df + 77afccc
commit cb3aa1b
Show file tree

Hide file tree

Showing 9 changed files with 34 additions and 10 deletions.
diff --git a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx
@@ -152,7 +152,7 @@ When enabling read-only workloads, keep in mind the following:
 
 - Advisory locks aren't replicated between Postgres nodes, so advisory locks taken on a standby replica don't conflict with advisory locks taken on the primary or another standby replica. We recommend that applications that rely on advisory locking avoid using read-only workloads for those transactions.
 
-For information on replication lag while using read-only workloads, see [Synchronous replication](/biganimal/latest/overview/02_high_availability/#synchronous-replication). 
+For information on replication lag while using read-only workloads, see [Standby replicas](/biganimal/latest/overview/02_high_availability/#standby-replicas). 
 
 ### Authentication
 

diff --git a/product_docs/docs/biganimal/release/using_cluster/01_postgres_access.mdx b/product_docs/docs/biganimal/release/using_cluster/01_postgres_access.mdx
@@ -100,7 +100,7 @@ Provision your cluster before configuring IAM for Postgres.
     1. On the **Additional Settings** tab, under **Authentication**, select **Identity and Access Management (IAM) Authentication**. 
     1. Select **Create Cluster** or **Save**.
     !!!note
-    To turn on IAM authentication using the CLI, see the [Using IAM authentication on AWS](/biganimal/latest/reference/cli/#using-iam-authentication-on-aws) section in the Using the BigAnimal CLI topic.
+    To turn on IAM authentication using the CLI, see the [Using IAM authentication on AWS](/biganimal/latest/reference/cli/using_features/#iam-authentication-cli-commands) section in the Using the BigAnimal CLI topic.
 1. In AWS, get the ARN of each IAM user requiring database access. In the AWS account connected to BigAnimal, use AWS Identity and Access Management (IAM) to perform user management. See the [AWS documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_manage.html). 
 
 1. In Postgres, if the IAM role doesn’t exist yet, run this Postgres command:

diff --git a/...t_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx b/...t_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx
@@ -21,7 +21,7 @@ You can also modify your cluster by installing Postgres extensions. See [Postgre
 4. You can modify the following settings on the corresponding tab of the Edit Cluster page:
 
    !!! Note
-       Any changes made to the cluster's instance type, volume type, or volume properties are not automatically applied to its replicas' settings. To avoid lag during replication, ensure that your replicas' instance and storage types are at least as large as the source cluster's instance and storage types. See [Modify a faraway replica](/biganimal/latest/using_cluster/managing_replicas/#modify-a-faraway-replica/).
+       Any changes made to the cluster's instance type, volume type, or volume properties are not automatically applied to its replicas' settings. To avoid lag during replication, ensure that your replicas' instance and storage types are at least as large as the source cluster's instance and storage types. See [Modify a faraway replica](/biganimal/latest/using_cluster/managing_replicas/#modify-a-faraway-replica).
 
    |                       Settings                       |         Tab         |                                                                                                                                                                                Notes                                                                                                                                                                                 |
    | ---------------------------------------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -33,7 +33,7 @@ You can also modify your cluster by installing Postgres extensions. See [Postgre
    | Volume properties                                    | Cluster Settings    | It can take up to six hours to tune IOPS or resize the disks of your cluster because AWS requires a cool down period after volume modifications as explained in the [Limitations](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/modify-volume-requirements.html) section. The volume properties are disabled and cannot be modified while this is in progress. |
    | Networking type (public or private)                  | Cluster Settings    | If you are using Azure and previously setup a private link and want to  change to a public network, you must remove the private link resources  before making the change.                                                                                                                                                                                            |
    | Nodes (for an extreme-high-availability cluster)     | Data Groups         | &mdash;                                                                                                                                                                                                                                                                                                                                                                     |
-   | Database configuration parameters                    | DB Configuration    | If you are using faraway replicas, only a small subset of parameters are editable. These parameters need to modified in the replica when increased in the replica's source cluster. See [Modify a faraway replica](/biganimal/latest/using_cluster/managing_replicas/#modify-a-faraway-replica/) for details.                                                        |
+   | Database configuration parameters                    | DB Configuration    | If you are using faraway replicas, only a small subset of parameters are editable. These parameters need to modified in the replica when increased in the replica's source cluster. See [Modify a faraway replica](/biganimal/latest/using_cluster/managing_replicas/#modify-a-faraway-replica) for details.                                                        |
    | Retention period for backups                         | Additional Settings | &mdash;                                                                                                                                                                                                                                                                                                                                                                   |
    | Read-only workloads                                  | Additional Settings | Enabling read-only workloads can incur higher cloud infrastructure charges.                                                                                                                                                                                                                                                                                          |
    | Custom maintenance window                            | Additional Settings | Set or modify a maintenance window in which maintenance upgrades occur for the cluster. See [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). |

diff --git a/product_docs/docs/biganimal/release/using_cluster/04_backup_and_restore.mdx b/product_docs/docs/biganimal/release/using_cluster/04_backup_and_restore.mdx
@@ -50,7 +50,7 @@ The restore operation is available for any cluster that has at least one availab
 
 ### Perform an extreme-high-availability cluster restore
 
-You can restore one data group from a PGD cluster into a new PGD cluster. To restore a two data groups, restore one data group into a new cluster, and add the second data group manually.  
+You can restore one data group from a PGD cluster into a new PGD cluster. To restore two data groups, restore one data group into a new cluster, and add the second data group manually.  
 
 1.  On the [Clusters](https://portal.biganimal.com/clusters) page in the [BigAnimal](https://portal.biganimal.com) portal, select the cluster you want to restore.
 1.  Select **Quick Actions > Restore**.
@@ -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 9-18 in [Create a data group](#create-a-data-group). 
+1. Follow Steps 3-5 in [Create an extreme-high-availability cluster](../getting_started/creating_a_cluster/creating_an_eha_cluster). 
 1. Select **Restore**.
diff --git a/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx b/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx
@@ -136,4 +136,4 @@ You can restore a replica backup to a standalone cluster. A new stand alone clus
 
 ## Using the CLI to manage faraway replicas
 
-See [Faraway replicas CLI commands](/biganimal/latest/reference/cli/using_features/#managing-faraway-replicas-using-the-cli) for information on CLI commands for managing faraway replicas.
+See [Faraway replicas CLI commands](/biganimal/latest/reference/cli/using_features/#faraway-replicas-cli-commands) for information on CLI commands for managing faraway replicas.
diff --git a/product_docs/docs/epas/15/epas_compat_ora_dev_guide/index.mdx b/product_docs/docs/epas/15/epas_compat_ora_dev_guide/index.mdx
@@ -10,9 +10,9 @@ legacyRedirectsGenerated:
 
 <div id="introduction" class="registered_link"></div>
 
-EDB Postgres Advanced Server makes Postgres look, feel, and operate more like Oracle, so when you migrate, there is less code to rewrite and you can be up and running quickly. 
+EDB Postgres Advanced Server makes Postgres look, feel, and operate more like Oracle, so when you migrate, there is less code to rewrite, and you can be up and running quickly. The Oracle compatibility features allow you to run many applications written for Oracle in EDB Postgres Advanced Server with minimal to no changes. 
 
-You use EDB Postgres Advanced Server features to design an application compatible with Oracle databases. For example, creating a compatible application entails selecting compatible:
+EDB Postgres Advanced Server provides Oracle compatible:
 
 -   System and built-in functions for use in SQL statements and procedural logic
 -   Stored procedure language (SPL) when creating database server-side application logic for stored procedures, functions, triggers, and packages

diff --git a/product_docs/docs/pem/9/index.mdx b/product_docs/docs/pem/9/index.mdx
@@ -1,7 +1,7 @@
 ---
 title: "Postgres Enterprise Manager"
 directoryDefaults:
-  description: "EDB Postgres Enterprise Manager (PEM) Version 8 Documentation and release notes. PostgreSQL GUI tool for monitoring and performance optimization."
+  description: "EDB Postgres Enterprise Manager (PEM) Version 9 documentation and release notes. Postgres GUI tool for monitoring and performance optimization."
 navigation:
   - pem_rel_notes
   - supported_platforms

diff --git a/src/pages/access-denied.js b/src/pages/access-denied.js
@@ -0,0 +1,21 @@
+import React from "react";
+import { Container } from "react-bootstrap";
+import { Footer, Layout, MainContent } from "../components";
+
+const AccessDenied = (data) => {
+  return (
+    <Layout pageMeta={{ title: "Access Denied" }}>
+      <Container fluid className="p-0 d-flex bg-white">
+        <div className="d-flex align-items-center flex-column">
+          <div className="mb-5">
+            <div className="mb-3">
+              The requested page cannot be served to your location.
+            </div>
+          </div>
+        </div>
+      </Container>
+    </Layout>
+  );
+};
+
+export default AccessDenied;
diff --git a/static/_redirects b/static/_redirects
@@ -23,6 +23,9 @@
 #
 # See also: https://docs.netlify.com/routing/redirects/redirect-options/
 
+# Sanctioned countries
+/* /access-denied 403! Country=cu,ir,kp,sd,ss,sy,by,ru
+
 # Docs 2.0 Redirects
 /docs/kubernetes/cloud_native_postgresql/* /docs/postgres_for_kubernetes/latest/:splat  302
 /docs/pgbouncer/1.0/*   /docs/pgbouncer/latest/:splat 301
Original file line number	Diff line number	Diff line change
Expand Up		@@ -136,4 +136,4 @@ You can restore a replica backup to a standalone cluster. A new stand alone clus

		## Using the CLI to manage faraway replicas

		See [Faraway replicas CLI commands](/biganimal/latest/reference/cli/using_features/#managing-faraway-replicas-using-the-cli) for information on CLI commands for managing faraway replicas.
		See [Faraway replicas CLI commands](/biganimal/latest/reference/cli/using_features/#faraway-replicas-cli-commands) for information on CLI commands for managing faraway replicas.