From 25a2cfc4856819cc6c0c17d78abacf2e20855b77 Mon Sep 17 00:00:00 2001 From: sszhao1020 <89435179+sszhao1020@users.noreply.github.com> Date: Mon, 22 Aug 2022 10:13:24 +0800 Subject: [PATCH 01/11] Update 01_understanding_qotas_in_azure.mdx --- .../01_preparing_azure/01_understanding_qotas_in_azure.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/01_understanding_qotas_in_azure.mdx b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/01_understanding_qotas_in_azure.mdx index 0a6cc95f04d..62db8ab269c 100644 --- a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/01_understanding_qotas_in_azure.mdx +++ b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/01_understanding_qotas_in_azure.mdx @@ -67,4 +67,4 @@ BigAnimal recommends the following per region when requesting virtual machine re - Total Regional vCPUs: minimum of 60 per designated region - Standard ESv3 Family vCPUs: minimum of 50 per designated region -- Standard Dv4 Family vCPUs: minimum of 10 per designated region +- Standard Dv4 Family vCPUs: minimum of 14 per designated region From a73a95cf08cc28860eaf7c8cd9388ae52d8cc568 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Wed, 27 Jul 2022 18:03:41 +0530 Subject: [PATCH 02/11] PEM - 8.6 release branch Added initial draft as per PEM-4498 --- .../pem/8/pem_upgrade/upgrading_backend_database.mdx | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx b/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx index d8f1b696b1f..3387da9f629 100644 --- a/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx @@ -10,7 +10,17 @@ redirects: If you're updating PEM components and the PEM backend database, perform PEM component updates on the server and agent before updating the backend database. For more information about updating PEM component software, see [Upgrading a PEM installation](upgrading_pem_installation/). !!! Note - From PEM version 8.0 and later, the PostgreSQL or EDB Postgres version 11 or later are supported only as a backend database server. If your backend database server is earlier than version 11, then first you need to upgrade your backend database server. Then upgrade the PEM components. + - From PEM 8.0 onwards, the PostgreSQL or EPAS version 11 or higher are only supported as backend database server. Hence if + your backend database server is lower than version 11 then first you need to upgrade your backend database server and then upgrade the PEM components. + + - After upgrading the backend database server, here is the solution if you face below error while creating the server in the PEM web interface: + + Error - User does not have enough permission to add new server. + Please contact the administrator to grant 'pem_database_server_registration' role to the 'enterprisedb' user. + + Solution - Update the roles to resolve the error and grant appropriate permissions using following update statement: + + `UPDATE pem.roles SET rolid = pr.oid FROM pg_roles pr WHERE pr.rolname = 'pem_' || component;` The update process uses the pg_upgrade utility to migrate from one version of the backend server to a more recent version. pg_upgrade enables migration between any supported version of Postgres and any subsequent release of Postgres that's supported on the same platform. From 1d60f6e86cb0faa65ff45363190b2cb32060ebdb Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 22 Aug 2022 16:16:00 +0530 Subject: [PATCH 03/11] Added note as per PEM-4498 --- .../docs/pem/8/pem_upgrade/upgrading_backend_database.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx b/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx index 3387da9f629..4ebf67de6f0 100644 --- a/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx @@ -13,7 +13,7 @@ If you're updating PEM components and the PEM backend database, perform PEM comp - From PEM 8.0 onwards, the PostgreSQL or EPAS version 11 or higher are only supported as backend database server. Hence if your backend database server is lower than version 11 then first you need to upgrade your backend database server and then upgrade the PEM components. - - After upgrading the backend database server, here is the solution if you face below error while creating the server in the PEM web interface: + - After upgrading the backend database server, if you face the below error while creating the server in the PEM web interface, then update the roles using the below query: Error - User does not have enough permission to add new server. Please contact the administrator to grant 'pem_database_server_registration' role to the 'enterprisedb' user. From 44174e43506645640349e15e1bd91bdb20e72146 Mon Sep 17 00:00:00 2001 From: Nick Ivanov <103075931+nick-ivanov-edb@users.noreply.github.com> Date: Mon, 22 Aug 2022 12:39:55 -0400 Subject: [PATCH 04/11] Add missing column in bdr.ddl_epoch Also fixed a typo in the description of `bdr.conflict_history.local_lsn`. --- product_docs/docs/pgd/4/overview/bdr/catalogs.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/4/overview/bdr/catalogs.mdx b/product_docs/docs/pgd/4/overview/bdr/catalogs.mdx index fb1d4bacddb..501bcf368a2 100644 --- a/product_docs/docs/pgd/4/overview/bdr/catalogs.mdx +++ b/product_docs/docs/pgd/4/overview/bdr/catalogs.mdx @@ -24,7 +24,7 @@ For details, see [Logging conflicts to a table](conflicts). | ----------------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------ | | sub_id | oid | Which subscription produced this conflict; can be joined to `bdr.subscription` table | | local_xid | xid | Local transaction of the replication process at the time of conflict | -| local_lsn | pg_lsn | Local transaction of the replication process at the time of conflict | +| local_lsn | pg_lsn | Local LSN at the time of conflict | | local_time | timestamp with time zone | Local time of the conflict | | remote_xid | xid | Transaction that produced the conflicting change on the remote node (an origin) | | remote_commit_lsn | pg_lsn | Commit LSN of the transaction which produced the conflicting change on the remote node (an origin) | @@ -1292,6 +1292,8 @@ An internal catalog table holding state per DDL epoch. | origin_node_id | oid | Internal node ID of the node that requested creation of this epoch | | epoch_consume_timeout | timestamptz | Timeout of this epoch | | epoch_consumed | boolean | Switches to true as soon as the local node has fully processed the epoch | +| epoch_consumed_lsn | boolean | LSN at which the local node has processed the epoch | + ### `bdr.internal_node_pre_commit` From c6f5c03d91dba87eaf3986e5af7dff4618a63f58 Mon Sep 17 00:00:00 2001 From: Frank Touserkani <94471063+ftouserkani-edb@users.noreply.github.com> Date: Fri, 19 Aug 2022 11:16:48 -0400 Subject: [PATCH 05/11] Update index.mdx --- .../free_trial/detail/create_an_account/index.mdx | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/biganimal/release/free_trial/detail/create_an_account/index.mdx b/product_docs/docs/biganimal/release/free_trial/detail/create_an_account/index.mdx index c7331608175..0657b9b15a2 100644 --- a/product_docs/docs/biganimal/release/free_trial/detail/create_an_account/index.mdx +++ b/product_docs/docs/biganimal/release/free_trial/detail/create_an_account/index.mdx @@ -4,17 +4,18 @@ description: "Creating an EDB account and signing into the BigAnimal free trial navTitle: "Create an account" --- -Registering an account on [enterprisedb.com](https://www.enterprisedb.com/) gets you access to the BigAnimal trial, as well as EDB's training and software downloads. +You will need to register with EDB in order to access BigAnimal free trial, as well as EDB's training and software downloads. Accounts are free, and registration takes less than a minute. 1. Navigate to . -2. Select the **Try it for free** button. -3. Fill in the form, and agree to the terms and conditions. +2. Select the **Test drive for free** button. +3. Fill in the form, and agree to the **Terms and Conditions** and the **Privacy Policy**. 4. Select **Submit**. 5. Check your email. You should receive an email from EDB containing an activation link. -6. Select the activation link and enter a password for your EDB account. +6. Click the activation link and enter a password for your EDB account. You're then redirected to the BigAnimal portal. !!! Note "Already have an EDB account?" - If you've already signed up for an EDB account, you can navigate to to log in. + If you've already signed up for an EDB account, you can navigate to to log in. + Please continue to use this portal in order to access BigAnimal for the duration of your free trial. From b3d7c215069f5e3c42ded8eb48ebd825d188dc8e Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 25 Aug 2022 06:56:17 -0400 Subject: [PATCH 06/11] copy edits --- .../free_trial/detail/create_an_account/index.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/biganimal/release/free_trial/detail/create_an_account/index.mdx b/product_docs/docs/biganimal/release/free_trial/detail/create_an_account/index.mdx index 0657b9b15a2..9a66c9d4c25 100644 --- a/product_docs/docs/biganimal/release/free_trial/detail/create_an_account/index.mdx +++ b/product_docs/docs/biganimal/release/free_trial/detail/create_an_account/index.mdx @@ -4,18 +4,18 @@ description: "Creating an EDB account and signing into the BigAnimal free trial navTitle: "Create an account" --- -You will need to register with EDB in order to access BigAnimal free trial, as well as EDB's training and software downloads. +You need to register with EDB to access the BigAnimal free trial and EDB's training and software downloads. + Accounts are free, and registration takes less than a minute. 1. Navigate to . 2. Select the **Test drive for free** button. -3. Fill in the form, and agree to the **Terms and Conditions** and the **Privacy Policy**. +3. Fill in the form, and agree to the terms and conditions and privacy policy. 4. Select **Submit**. -5. Check your email. You should receive an email from EDB containing an activation link. -6. Click the activation link and enter a password for your EDB account. +5. Check your email for an email from EDB that contains an activation link. +6. Select the activation link and enter a password for your EDB account. You're then redirected to the BigAnimal portal. !!! Note "Already have an EDB account?" - If you've already signed up for an EDB account, you can navigate to to log in. - Please continue to use this portal in order to access BigAnimal for the duration of your free trial. + If you already signed up for an EDB account, navigate to https://freetrial.biganimal.com/ to log in. Continue to use this portal to access BigAnimal for the rest of your free trial. \ No newline at end of file From 662a17190fca5e161aa62c45d12a7c12d5521ed7 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Thu, 25 Aug 2022 08:30:31 -0400 Subject: [PATCH 07/11] changes --- .../04_mp_migrating_database/01_mp_schema_extraction/index.mdx | 2 +- product_docs/docs/pgd/4/overview/harp/02_overview.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx index acf42d85720..bd4ee2ce47f 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx @@ -84,7 +84,7 @@ Extract dependent object from other schemas?(yes/no) (Default no / Ignored for a After loading the `edb_ddl_extractor.sql` script into SQL Developer and connecting to the source Oracle database, run the script. As the script executes, respond to the prompts. -1. If the the user for the database connection has the required privileges as listed in the **Script Output** tab, select **Yes** to continue running the script. +1. If the user for the database connection has the required privileges as listed in the **Script Output** tab, select **Yes** to continue running the script. 2. Enter a comma-separated list of schemas and select **OK**. diff --git a/product_docs/docs/pgd/4/overview/harp/02_overview.mdx b/product_docs/docs/pgd/4/overview/harp/02_overview.mdx index 7db92e093cd..8d9c0c139fd 100644 --- a/product_docs/docs/pgd/4/overview/harp/02_overview.mdx +++ b/product_docs/docs/pgd/4/overview/harp/02_overview.mdx @@ -33,7 +33,7 @@ target is ambiguous or unknowable. In a standard Postgres cluster, it's important that only a single node is ever writable and sending replication traffic to the remaining nodes. -Even in multi-master-capable approaches such as BDR, it can be help to +Even in multi-master-capable approaches such as BDR, it can be helpful to reduce the amount of necessary conflict management to derive identical data across the cluster. In clusters that consist of multiple BDR nodes per physical location or region, this usually means a single BDR node acts as a "leader" and From 8ad2c4e9185b4a7dd7bb2f89bf0a14d99c373e50 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 25 Aug 2022 09:36:01 -0400 Subject: [PATCH 08/11] copy edit --- .../pem_upgrade/upgrading_backend_database.mdx | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx b/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx index 4ebf67de6f0..0782655dab6 100644 --- a/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx @@ -10,17 +10,22 @@ redirects: If you're updating PEM components and the PEM backend database, perform PEM component updates on the server and agent before updating the backend database. For more information about updating PEM component software, see [Upgrading a PEM installation](upgrading_pem_installation/). !!! Note - - From PEM 8.0 onwards, the PostgreSQL or EPAS version 11 or higher are only supported as backend database server. Hence if - your backend database server is lower than version 11 then first you need to upgrade your backend database server and then upgrade the PEM components. + - From PEM 8.0 onwards, PostgreSQL or EPAS versions 11 or later are only supported as backend database servers. As a result, if + your backend database server is earlier than version 11, you need to first upgrade your backend database server and then upgrade the PEM components. - - After upgrading the backend database server, if you face the below error while creating the server in the PEM web interface, then update the roles using the below query: + - After upgrading the backend database server, if you encounter this error while creating the server in the PEM web interface: + ``` Error - User does not have enough permission to add new server. - Please contact the administrator to grant 'pem_database_server_registration' role to the 'enterprisedb' user. + Please contact the administrator to grant 'pem_database_server_registration' role + to the 'enterprisedb' user. + ``` - Solution - Update the roles to resolve the error and grant appropriate permissions using following update statement: + Resolve the error by updating the roles and granting appropriate permissions: - `UPDATE pem.roles SET rolid = pr.oid FROM pg_roles pr WHERE pr.rolname = 'pem_' || component;` + ```sql + UPDATE pem.roles SET rolid = pr.oid FROM pg_roles pr WHERE pr.rolname = 'pem_' || component;` + ``` The update process uses the pg_upgrade utility to migrate from one version of the backend server to a more recent version. pg_upgrade enables migration between any supported version of Postgres and any subsequent release of Postgres that's supported on the same platform. From d4ab5c069e9551dcdb11df150b740b6791217f02 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Wed, 27 Jul 2022 18:03:41 +0530 Subject: [PATCH 09/11] PEM - 8.6 release branch Added initial draft as per PEM-4498 From f573cd63ef039802670b0de26e70059317d5bf65 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 25 Aug 2022 10:22:37 -0400 Subject: [PATCH 10/11] incorporated Nidhi's comments --- .../docs/pem/8/pem_upgrade/upgrading_backend_database.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx b/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx index 0782655dab6..bdd0dd60192 100644 --- a/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx @@ -15,7 +15,7 @@ If you're updating PEM components and the PEM backend database, perform PEM comp - After upgrading the backend database server, if you encounter this error while creating the server in the PEM web interface: - ``` + ```text Error - User does not have enough permission to add new server. Please contact the administrator to grant 'pem_database_server_registration' role to the 'enterprisedb' user. @@ -24,7 +24,7 @@ If you're updating PEM components and the PEM backend database, perform PEM comp Resolve the error by updating the roles and granting appropriate permissions: ```sql - UPDATE pem.roles SET rolid = pr.oid FROM pg_roles pr WHERE pr.rolname = 'pem_' || component;` + UPDATE pem.roles SET rolid = pr.oid FROM pg_roles pr WHERE pr.rolname = 'pem_' || component; ``` The update process uses the pg_upgrade utility to migrate from one version of the backend server to a more recent version. pg_upgrade enables migration between any supported version of Postgres and any subsequent release of Postgres that's supported on the same platform. From 492691d4299c6da0fa94a1bdc31a77626469f9d7 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 25 Aug 2022 12:14:59 -0400 Subject: [PATCH 11/11] Fixed code block formatting --- .../docs/pem/8/pem_upgrade/upgrading_backend_database.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx b/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx index bdd0dd60192..128f92e20bc 100644 --- a/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/upgrading_backend_database.mdx @@ -31,7 +31,7 @@ The update process uses the pg_upgrade utility to migrate from one version of th If the source PEM server is earlier than the 7.16 version, then you need to replace the following functions before you run pg_upgrade: - - The `abstime`, `reltime`, and `tinterval` datatypes are deprecated from Postgres version 12 or later, hence to replace those dataypes with `timestamptz` data type use this command: +- The `abstime`, `reltime`, and `tinterval` datatypes are deprecated from Postgres version 12 or later, hence to replace those dataypes with `timestamptz` data type use this command: ```sql DO @@ -50,7 +50,7 @@ If the source PEM server is earlier than the 7.16 version, then you need to repl ALTER TABLE pemdata.user_info ALTER COLUMN valuntil SET DATA TYPE timestamptz; ALTER TABLE pemhistory.user_info - ALTER COLUMN valuntil SET DATA TYPE timestamptz; + ALTER COLUMN valuntil SET DATA TYPE timestamptz; -- Now update the pem.probe_column itself UPDATE pem.probe_column SET sql_data_type = ‘timestamptz’