From 14d3d1e0739a3b1aa77b3217f01fe89d4733f639 Mon Sep 17 00:00:00 2001 From: Bobby Bissett Date: Thu, 27 Jul 2023 11:37:19 -0400 Subject: [PATCH 001/255] Adding warning message about openjdk 11 issue on redhat Pushing this first and will correct formatting after I see the generated pages. --- product_docs/docs/efm/4/13_troubleshooting.mdx | 6 +++++- product_docs/docs/efm/4/installing/prerequisites.mdx | 7 ++++++- 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/efm/4/13_troubleshooting.mdx b/product_docs/docs/efm/4/13_troubleshooting.mdx index 62749d37f2e..96c3d93de75 100644 --- a/product_docs/docs/efm/4/13_troubleshooting.mdx +++ b/product_docs/docs/efm/4/13_troubleshooting.mdx @@ -1,6 +1,6 @@ --- title: "Troubleshooting" -redirects: +redirects: - ../efm_user/13_troubleshooting legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. @@ -47,3 +47,7 @@ openjdk version "1.8.0_191" 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: + `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, e.g. `dnf install tzdata-java` diff --git a/product_docs/docs/efm/4/installing/prerequisites.mdx b/product_docs/docs/efm/4/installing/prerequisites.mdx index 24e2b64e048..7a55ea3e34a 100644 --- a/product_docs/docs/efm/4/installing/prerequisites.mdx +++ b/product_docs/docs/efm/4/installing/prerequisites.mdx @@ -1,6 +1,6 @@ --- title: "Prerequisites" -redirects: +redirects: - ../efm_user/02_failover_manager_overview/01_prerequisites - /efm/latest/01_prerequisites/ legacyRedirectsGenerated: @@ -17,6 +17,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: + `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, e.g. `dnf install tzdata-java` + ## Provide an SMTP server You can receive notifications from Failover Manager as specified by a user-defined notification script, by email, or both. From e15922d3ed9e017567c407a541206797dbd3edaa Mon Sep 17 00:00:00 2001 From: Bobby Bissett Date: Thu, 27 Jul 2023 13:16:01 -0400 Subject: [PATCH 002/255] Trying to add newlines. --- product_docs/docs/efm/4/13_troubleshooting.mdx | 2 ++ product_docs/docs/efm/4/installing/prerequisites.mdx | 2 ++ 2 files changed, 4 insertions(+) diff --git a/product_docs/docs/efm/4/13_troubleshooting.mdx b/product_docs/docs/efm/4/13_troubleshooting.mdx index 96c3d93de75..44da9ff6493 100644 --- a/product_docs/docs/efm/4/13_troubleshooting.mdx +++ b/product_docs/docs/efm/4/13_troubleshooting.mdx @@ -49,5 +49,7 @@ 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: + `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, e.g. `dnf install tzdata-java` diff --git a/product_docs/docs/efm/4/installing/prerequisites.mdx b/product_docs/docs/efm/4/installing/prerequisites.mdx index 7a55ea3e34a..83a7845f59c 100644 --- a/product_docs/docs/efm/4/installing/prerequisites.mdx +++ b/product_docs/docs/efm/4/installing/prerequisites.mdx @@ -19,7 +19,9 @@ Before using Failover Manager, you must first install Java (version 1.8 or later !!! 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: + `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, e.g. `dnf install tzdata-java` ## Provide an SMTP server From 40ed6bbd43906002918af9e86823368846a7e588 Mon Sep 17 00:00:00 2001 From: Bobby Bissett Date: Thu, 27 Jul 2023 13:54:07 -0400 Subject: [PATCH 003/255] Somehow "Note" was lost. Trying it like other examples in the doc but can't find one with multiple lines yet. --- product_docs/docs/efm/4/13_troubleshooting.mdx | 2 +- product_docs/docs/efm/4/installing/prerequisites.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/efm/4/13_troubleshooting.mdx b/product_docs/docs/efm/4/13_troubleshooting.mdx index 44da9ff6493..ff558cdb8bc 100644 --- a/product_docs/docs/efm/4/13_troubleshooting.mdx +++ b/product_docs/docs/efm/4/13_troubleshooting.mdx @@ -47,7 +47,7 @@ openjdk version "1.8.0_191" OpenJDK Runtime Environment (build 1.8.0_191-b12) OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode) ``` -!!! Note: +!!! 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: `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)` diff --git a/product_docs/docs/efm/4/installing/prerequisites.mdx b/product_docs/docs/efm/4/installing/prerequisites.mdx index 83a7845f59c..7c221116dc5 100644 --- a/product_docs/docs/efm/4/installing/prerequisites.mdx +++ b/product_docs/docs/efm/4/installing/prerequisites.mdx @@ -17,7 +17,7 @@ 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: +!!! 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: `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)` From 5d7421fa7fc2ebb20363d5fba32ed93123f9dfa0 Mon Sep 17 00:00:00 2001 From: michaelwilleredb Date: Thu, 17 Aug 2023 10:09:22 +0200 Subject: [PATCH 004/255] Adding Server sizing considerations --- .../migrating/oracle/factors_to_consider.mdx | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/advocacy_docs/migrating/oracle/factors_to_consider.mdx b/advocacy_docs/migrating/oracle/factors_to_consider.mdx index d74965ef80b..ea5e60507aa 100644 --- a/advocacy_docs/migrating/oracle/factors_to_consider.mdx +++ b/advocacy_docs/migrating/oracle/factors_to_consider.mdx @@ -9,6 +9,7 @@ You'll want to think about these factors when analyzing and planning for your mi - Infrastructure - Applications - Operations +- Server sizing ## Schema migration considerations @@ -68,6 +69,20 @@ Migrating a legacy database to new database technology results in the need to up Also, when legacy databases are running on older specialized hardware and operating systems, a database migration might also require migrating the underlying host systems to modern platforms and operating systems. For on-premises migrations, this can result in the need to change your operations and maintenance procedures and tools to work with the new server platforms and operating systems. For migrations to the cloud, some of the operations and maintenance activities will be handled by the cloud service provider but others will still be your responsibility. Likely, those activities will require different tools and procedures from the ones you're currently using. +## Sizing and configuration considerations + +"How big a server will I need?" + +This question comes up quite often when considering Oracle to Postgres migrations. The shortest answer is "It depends...", which is not a good answer. A better one is: "Start with a 1:1 (i.e. same number of cores, RAM, ...) and go from there". + +Why is that? + +Postgres and Oracle are very different under the hood with different SQL planning, different storage and access patterns .. even the version control and transaction isolation is implemented in a different way. So, it's no surprise that is difficult to set up a simple formular, that covers all possible permutations of Oracle configurations and architectures. And the truth is that all databases respond differently to the workload being run. So, the same workload will + +EDB has performed a large number of benchmarks on different CPU/RAM configuration that show that Postgres (and EPAS) are both slightly faster than Oracle ... on on a TPC-C workload. These results might not apply to your application(s), but it's a good starting point. + +If the hardware on the new server differs from the existing Oracle server(s), then using a tool like [HammerDB](http://hammerdb.com) would allow you compare the performance. Please refer to the [HammerDB documentation(https://www.hammerdb.com/docs/ch03s04.html) when comparing results. + ## Some best practice considerations The following are some best practices to consider when planning for your Oracle-to-Postgres database application migration: From 179670da4dcacec3bb4da63971e406a4f05d1bba Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 17 Aug 2023 11:26:32 -0400 Subject: [PATCH 005/255] Update factors_to_consider.mdx --- advocacy_docs/migrating/oracle/factors_to_consider.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/advocacy_docs/migrating/oracle/factors_to_consider.mdx b/advocacy_docs/migrating/oracle/factors_to_consider.mdx index ea5e60507aa..c778f609d78 100644 --- a/advocacy_docs/migrating/oracle/factors_to_consider.mdx +++ b/advocacy_docs/migrating/oracle/factors_to_consider.mdx @@ -73,15 +73,15 @@ Also, when legacy databases are running on older specialized hardware and operat "How big a server will I need?" -This question comes up quite often when considering Oracle to Postgres migrations. The shortest answer is "It depends...", which is not a good answer. A better one is: "Start with a 1:1 (i.e. same number of cores, RAM, ...) and go from there". +This question comes up often when considering Oracle-to-Postgres migrations. The shortest answer is, "It depends," which isn't a good answer. A better one is, "Start with a 1:1 correspondence (that is, same number of cores, RAM, and so on), and go from there." -Why is that? +Why is that? -Postgres and Oracle are very different under the hood with different SQL planning, different storage and access patterns .. even the version control and transaction isolation is implemented in a different way. So, it's no surprise that is difficult to set up a simple formular, that covers all possible permutations of Oracle configurations and architectures. And the truth is that all databases respond differently to the workload being run. So, the same workload will +Postgres and Oracle are very different under the hood, with different SQL planning and different storage and access patterns. Even the version control and transaction isolation are implemented in a different way. That makes it difficult to set up a simple formula that covers all possible permutations of Oracle configurations and architectures. All databases respond differently to the workload being run. -EDB has performed a large number of benchmarks on different CPU/RAM configuration that show that Postgres (and EPAS) are both slightly faster than Oracle ... on on a TPC-C workload. These results might not apply to your application(s), but it's a good starting point. +EDB has performed many benchmarks on different CPU/RAM configurations that show that Postgres and EDB Postgres Advanced Server are both slightly faster than Oracle on a TPC-C workload. These results might not apply to your applications, but thye offer a good starting point. -If the hardware on the new server differs from the existing Oracle server(s), then using a tool like [HammerDB](http://hammerdb.com) would allow you compare the performance. Please refer to the [HammerDB documentation(https://www.hammerdb.com/docs/ch03s04.html) when comparing results. +If the hardware on the new server differs from the existing Oracle servers, then you can use a tool like [HammerDB](http://hammerdb.com) to compare the performance. Refer to the [HammerDB documentation(https://www.hammerdb.com/docs/ch03s04.html) when comparing results. ## Some best practice considerations From 5492501aa90a3e7393aefbd99f4160ed59495521 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Thu, 24 Aug 2023 12:05:52 +0100 Subject: [PATCH 006/255] Fixes shell space Signed-off-by: Dj Walker-Morgan --- .../products/hadoop-foreign-data-wrapper/rhel-8-or-ol-8.njk | 2 +- .../products/hadoop-foreign-data-wrapper/rhel-9-or-ol-9.njk | 2 +- .../products/mysql-foreign-data-wrapper/debian-10.njk | 2 +- .../02_connecting_from_aws/02_vpc_peering.mdx | 4 ++-- .../eprs/7/07_common_operations/11_using_ssl_connections.mdx | 2 +- .../docs/pgd/5/quickstart/connecting_applications.mdx | 2 +- 6 files changed, 7 insertions(+), 7 deletions(-) diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8-or-ol-8.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8-or-ol-8.njk index 638eb914d0a..e88a7769cfd 100644 --- a/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8-or-ol-8.njk +++ b/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8-or-ol-8.njk @@ -3,7 +3,7 @@ {% block prerequisites %} {{ super() }} - Enable additional repositories to resolve dependencies: - ```shell + ```shell sudo dnf config-manager --set-enabled PowerTools ``` {% endblock prerequisites %} \ No newline at end of file diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-9-or-ol-9.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-9-or-ol-9.njk index 32cd6baa6e2..11d9017285f 100644 --- a/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-9-or-ol-9.njk +++ b/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-9-or-ol-9.njk @@ -3,7 +3,7 @@ {% block prerequisites %} {{ super() }} - Enable additional repositories to resolve dependencies: - ```shell + ```shell sudo dnf config-manager --set-enabled PowerTools ``` {% endblock prerequisites %} \ No newline at end of file diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk b/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk index 953a63f94af..904b8c82152 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk @@ -3,7 +3,7 @@ {% block prerequisites %} {{ super() }} - Download the GPG key to your APT keyring directly using the apt-key utility - ```shell + ```shell sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 3A79BD29 ``` - Install and configure the MySQL repo diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/02_vpc_peering.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/02_vpc_peering.mdx index 34682bdda81..f80ffd39c6b 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/02_vpc_peering.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/02_vpc_peering.mdx @@ -97,7 +97,7 @@ You can create a VPC peering connection with a VPC in the same region or a diffe 1. Access the cluster with its domain name from your cluster's connection string. It's accessible from `vpc-client` after peering. - ```shell + ```shell psql -h vpce-XXXXXXXXXXXXXXXXXXXX.eu-west-1.vpce.amazonaws.com -U edb_admin __OUTPUT__ Password for user edb_admin: @@ -139,7 +139,7 @@ You can create a VPC peering connection with a VPC in the same region or a diffe 1. Access the cluster with its domain name from your cluster's connection string. It's accessible from `vpc-client` after peering. - ```shell + ```shell psql -h vpce-XXXXXXXXXXXXXXXXXXXX.eu-west-1.vpce.amazonaws.com -U edb_admin __OUTPUT__ Password for user edb_admin: diff --git a/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx b/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx index 54992a92987..d781b3ca390 100644 --- a/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx @@ -274,7 +274,7 @@ Before you begin, configure the client for SSL with trigger mode. For this example, assume file `xdb.crt` is a copy of `server.crt` and `xdb.key` is a copy of `server.key`. If you generated the server certificate with `CN=hostname/ip-address`, create xdb.keystore/xdb_pkcs.p12 with the `postgresql.crt` and `postgresql.ke`y client files as created with `CN=username` using the following commands : - ```shell + ```shell $ cp postgresql.crt xdb.crt $ cp postgresql.key xdb.key ``` diff --git a/product_docs/docs/pgd/5/quickstart/connecting_applications.mdx b/product_docs/docs/pgd/5/quickstart/connecting_applications.mdx index e1c71bb63e4..af13cf1f1e1 100644 --- a/product_docs/docs/pgd/5/quickstart/connecting_applications.mdx +++ b/product_docs/docs/pgd/5/quickstart/connecting_applications.mdx @@ -158,7 +158,7 @@ bdrdb=# By listing all the addresses of proxies as the host, you can ensure that the client will always failover and connect to the first available proxy in the event of a proxy failing. -```shell +```shell psql -h ,, -U enterprisedb -p 6432 bdrdb __OUTPUT__ psql (15.2, server 15.2.0 (Debian 15.2.0-2.buster)) From 29168d574fdffc1dfe9fd382b268ecf87f3ad93c Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Thu, 24 Aug 2023 15:25:59 +0100 Subject: [PATCH 007/255] Removed non-breaking-space Signed-off-by: Dj Walker-Morgan --- product_docs/docs/postgres_for_kubernetes/1/benchmarking.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/postgres_for_kubernetes/1/benchmarking.mdx b/product_docs/docs/postgres_for_kubernetes/1/benchmarking.mdx index cb90ac72b44..0884e13a29e 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/benchmarking.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/benchmarking.mdx @@ -55,7 +55,7 @@ kubectl cnp pgbench \ You can see the progress of the job with: -```shell  +```shell kubectl logs jobs/pgbench-run ``` From ec1b3f1de5491fe5b536c2fa8b4bd072979f54df Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Thu, 24 Aug 2023 15:21:41 -0700 Subject: [PATCH 008/255] Update architectures.mdx --- product_docs/docs/pgd/5/architectures.mdx | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/pgd/5/architectures.mdx b/product_docs/docs/pgd/5/architectures.mdx index aee575d6b11..210ac0bcf2f 100644 --- a/product_docs/docs/pgd/5/architectures.mdx +++ b/product_docs/docs/pgd/5/architectures.mdx @@ -94,12 +94,14 @@ they aren't part of the standard Always On architectures. * Can be 3 data nodes (recommended) * Can be 2 data nodes and 1 witness that doesn't hold data (not depicted) * A PGD Proxy for each data node with affinity to the applications - * Can be colocated with data node + * Can be colocated with data node (recommended) + * Can be located on a separate node + * Configuration and infrastructure symmetry of data nodes is expected to ensure proper resources are available to handle application workload when rerouted * Barman for backup and recovery (not depicted) * Offsite is optional but recommended - * Can be shared by multiple clusters + * Can be shared by multiple PGD clusters * Postgres Enterprise Manager (PEM) for monitoring (not depicted) - * Can be shared by multiple clusters + * Can be shared by multiple PGD clusters ### Always On multi-location @@ -112,14 +114,17 @@ they aren't part of the standard Always On architectures. * Can be 3 data nodes (recommended) * Can be 2 data nodes and 1 witness which does not hold data (not depicted) * A PGD-Proxy for each data node with affinity to the applications - * can be co-located with data node + * can be co-located with data node (recommended) + * can be located on a separate node + * Configuration and infrastructure symmetry of data nodes and locations is expected to ensure proper resources are available to handle application workload when rerouted * Barman for backup and recovery (not depicted). - * Can be shared by multiple clusters + * Can be shared by multiple PGD clusters * Postgres Enterprise Manager (PEM) for monitoring (not depicted). - * Can be shared by multiple clusters + * Can be shared by multiple PGD clusters * An optional witness node must be placed in a third region to increase tolerance for location failure. * Otherwise, when a location fails, actions requiring global consensus are blocked, such as adding new nodes and distributed DDL. + ## Choosing your architecture All architectures provide the following: From 0e78882ae54a32f776cacba070a20b5f85278e2f Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 25 Aug 2023 16:20:26 -0400 Subject: [PATCH 009/255] Light edits to this content Mostly removing emphasis. --- .../sql_reference/01_sql_syntax/01_lexical_structure.mdx | 8 ++++---- .../02_enhanced_compatibility_features.mdx | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/epas/15/reference/sql_reference/01_sql_syntax/01_lexical_structure.mdx b/product_docs/docs/epas/15/reference/sql_reference/01_sql_syntax/01_lexical_structure.mdx index efa81536f45..e40a474410f 100644 --- a/product_docs/docs/epas/15/reference/sql_reference/01_sql_syntax/01_lexical_structure.mdx +++ b/product_docs/docs/epas/15/reference/sql_reference/01_sql_syntax/01_lexical_structure.mdx @@ -10,17 +10,17 @@ redirects: -There are several aspects to the lexical structure of SQL: +The lexical structure of SQL has several aspects: - SQL input consists of a sequence of commands. -- A *command* is composed of a sequence of *tokens*, terminated by a semicolon (;). The end of the input stream also terminates a command. +- A command is composed of a sequence of tokens, terminated by a semicolon (;). The end of the input stream also terminates a command. - The valid tokens depend on the syntax of the command. -- A token can be a *key word*, an *identifier*, a *quoted identifier*, a *literal* (or *constant*), or a special character symbol. Tokens are normally separated by *whitespace* (space, tab, new line) but don't need to be if there's no ambiguity (which is generally the case only if a special character is adjacent to some other token type). +- A token can be a key word, an identifier, a quoted identifier, a literal or constant, or a special character symbol. Tokens are normally separated by whitespace (space, tab, new line) but don't need to be if there's no ambiguity. This is generally the case only if a special character is adjacent to some other token type. -- *Comments* can occur in SQL input. They aren't tokens; they are equivalent to whitespace. +- Comments can occur in SQL input. They aren't tokens. They are equivalent to whitespace. For example, the following is syntactically valid SQL input: diff --git a/product_docs/docs/epas/15/working_with_oracle_data/02_enhanced_compatibility_features.mdx b/product_docs/docs/epas/15/working_with_oracle_data/02_enhanced_compatibility_features.mdx index f8f8a938d72..e22b9e455dc 100644 --- a/product_docs/docs/epas/15/working_with_oracle_data/02_enhanced_compatibility_features.mdx +++ b/product_docs/docs/epas/15/working_with_oracle_data/02_enhanced_compatibility_features.mdx @@ -28,7 +28,7 @@ EDB Postgres Advanced Server includes extended functionality that provides compa You can install EDB Postgres Advanced Server in several ways to enable compatibility features: -- Use the `INITDBOPTS` variable in the EDB Postgres Advanced Server service configuration file to specify `--redwood-like` **before initializing your cluster**. +- Before initializing your cluster, use the `INITDBOPTS` variable in the EDB Postgres Advanced Server service configuration file to specify `--redwood-like`. - Include the `--redwood-like` parameter when using `initdb` to initialize your cluster. See [Configuration parameters compatible with Oracle databases](../reference/database_administrator_reference/02_summary_of_configuration_parameters/) and [Managing an EDB Postgres Advanced Server installation](../installing/linux_install_details/managing_an_advanced_server_installation/) for more information about the installation options supported by the EDB Postgres Advanced Server installers. From cec0313cfbf321a812eba00b91b698f0c979de9c Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 29 Aug 2023 06:56:14 -0400 Subject: [PATCH 010/255] EPAS: link in install topics --- .../templates/products/edb-postgres-advanced-server/base.njk | 2 +- .../docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx | 2 +- .../docs/epas/15/installing/linux_ppc64le/epas_rhel_8.mdx | 2 +- .../docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx | 2 +- .../docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx | 2 +- .../docs/epas/15/installing/linux_ppc64le/epas_sles_15.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_other_linux_8.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_other_linux_9.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_rhel_8.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_sles_15.mdx | 2 +- 14 files changed, 14 insertions(+), 14 deletions(-) diff --git a/install_template/templates/products/edb-postgres-advanced-server/base.njk b/install_template/templates/products/edb-postgres-advanced-server/base.njk index 8969a17d503..c04b8572d23 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/base.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/base.njk @@ -32,7 +32,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. {# this is kinda awful, but gotta deal with the reorg somehow... --jh #} -{% set init_cluster_url = "../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/" if product.version >= 15 else "../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode" %} +{% set init_cluster_url = "../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode" if product.version >= 15 else "../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode" %} First you need to initialize and start the database cluster. The `edb-as-{{ product.version | replace(".", "") }}-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode]({{ init_cluster_url }}). ```shell diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx index b7c03db8d12..fadb9f01f04 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx @@ -69,7 +69,7 @@ Installing the server package creates an operating system user named enterprised This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/). +First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_8.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_8.mdx index 41c4b5182a9..b9d8718e83a 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_8.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_8.mdx @@ -71,7 +71,7 @@ Installing the server package creates an operating system user named enterprised This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/). +First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx index c7414e4ab9f..0be46476011 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx @@ -71,7 +71,7 @@ Installing the server package creates an operating system user named enterprised This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/). +First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx index 85a4b80c4dd..f497ac63eb0 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx @@ -65,7 +65,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/). +First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_15.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_15.mdx index 6547ac9e69c..9205ac4472c 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_15.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_15.mdx @@ -66,7 +66,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/). +First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx index 2bef50e67ad..ab0da72c2da 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx @@ -61,7 +61,7 @@ Installing the server package creates an operating system user named enterprised This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/). +First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_8.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_8.mdx index 259dbf6f6f7..9ffbe1028fd 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_8.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_8.mdx @@ -67,7 +67,7 @@ Installing the server package creates an operating system user named enterprised This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/). +First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_9.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_9.mdx index 468292b80af..f8acd3ad53f 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_9.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_9.mdx @@ -67,7 +67,7 @@ Installing the server package creates an operating system user named enterprised This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/). +First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx index e1c87b26fc0..b6effda2dcc 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx @@ -67,7 +67,7 @@ Installing the server package creates an operating system user named enterprised This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/). +First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_8.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_8.mdx index 26c8c4cf628..41177790cb4 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_8.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_8.mdx @@ -69,7 +69,7 @@ Installing the server package creates an operating system user named enterprised This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/). +First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx index 47fd7bf352f..39e9d81371e 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx @@ -69,7 +69,7 @@ Installing the server package creates an operating system user named enterprised This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/). +First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx index 729f4b289f8..e9b510cb09a 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx @@ -65,7 +65,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/). +First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_15.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_15.mdx index 1f125a35ea3..6946d889b00 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_15.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_15.mdx @@ -66,7 +66,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/). +First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb From 5b3fce25232adeeefd370da164d08298770fdb64 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 31 Aug 2023 13:11:37 -0400 Subject: [PATCH 011/255] copy edits to new upgrade info --- product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx b/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx index fffac6f1323..5f34826027f 100644 --- a/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx +++ b/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx @@ -27,19 +27,19 @@ Upgrades from PGD 4 to PGD 5 are supported from version 4.3.0. For older version ## Upgrading from version 3.7 to version 5 -At this time, TPA has only enabled upgrades from PGD 3.7 to 4 and PGD 4 to 5. -Customers moving from 3.7 to 5 and desiring automation would need to use this -two-step upgrade path and will potentially have their proxy architecture changed -multiple times from HA Proxy to HARP and finally to PGD Proxy. +At this time, TPA has enabled upgrades only from PGD 3.7 to 4 and PGD 4 to 5. +If you're moving from 3.7 to 5 and want automation, you need to use this +two-step upgrade path. Using this process, it's possible your proxy architecture will change +multiple times: from HA Proxy to HARP and then to PGD Proxy. -Significant development has been done to make upgrading directly from 3.7 to 5 +Significant development was done to make upgrading directly from 3.7 to 5 possible and easier. We've expanded the database versions supported with PGD 5 and enabled the upgradeability of the BDR extension across multiple PGD -versions. Previously, we only supported upgrades from the previous major +versions. Previously, we supported upgrades only from the previous major version. Often, a database upgrade was also required because only one database major version was supported by both PGD versions. Development is currently ongoing to provide a direct upgrade path from 3.7 to 5 -using TPA by Q4. In the interim, customers may reach out to EDB Professional +using TPA by Q4. In the interim, you can reach out to EDB Professional Services or Support for assistance and guidance. From d2c694fbeee99ad790432f94da69b3634b47435c Mon Sep 17 00:00:00 2001 From: michaelwilleredb Date: Fri, 1 Sep 2023 10:06:10 +0200 Subject: [PATCH 012/255] Update factors_to_consider.mdx Updated with Vibhor's suggestions. Removed mentioning of HammerDB. --- advocacy_docs/migrating/oracle/factors_to_consider.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/advocacy_docs/migrating/oracle/factors_to_consider.mdx b/advocacy_docs/migrating/oracle/factors_to_consider.mdx index c778f609d78..68bf5e9d171 100644 --- a/advocacy_docs/migrating/oracle/factors_to_consider.mdx +++ b/advocacy_docs/migrating/oracle/factors_to_consider.mdx @@ -79,9 +79,7 @@ Why is that? Postgres and Oracle are very different under the hood, with different SQL planning and different storage and access patterns. Even the version control and transaction isolation are implemented in a different way. That makes it difficult to set up a simple formula that covers all possible permutations of Oracle configurations and architectures. All databases respond differently to the workload being run. -EDB has performed many benchmarks on different CPU/RAM configurations that show that Postgres and EDB Postgres Advanced Server are both slightly faster than Oracle on a TPC-C workload. These results might not apply to your applications, but thye offer a good starting point. - -If the hardware on the new server differs from the existing Oracle servers, then you can use a tool like [HammerDB](http://hammerdb.com) to compare the performance. Refer to the [HammerDB documentation(https://www.hammerdb.com/docs/ch03s04.html) when comparing results. +Customers of EDB who have migrated to EPAS have found performance on par with Oracle when using similar hardware. In some instances, depending on their workload, they even outperform Oracle. All our customers who migrated aimed to at least match Oracle's performance and, if feasible, to exceed it either on comparable hardware or by adding resources as needed. We (EDB) also suggest conducting a benchmark using your specific workload to ensure the system meets performance expectations and to plan production accordingly. ## Some best practice considerations From 53c1b764a6f6f114015e54eafc9f81e6362311ba Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 31 Aug 2023 14:35:09 -0400 Subject: [PATCH 013/255] small edits to epas release notes --- .../15/epas_rel_notes/epas15_4_0_rel_notes.mdx | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx b/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx index b00a9db8df3..c7ba3885282 100644 --- a/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx +++ b/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx @@ -9,7 +9,7 @@ Released: 21 Aug 2023 Updated: 30 Aug 2023 !!! Important Upgrading -Once you have upgraded to this version of EDB Postgres Advanced Server, you will need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application will check that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool. +After you upgrade to this version of EDB Postgres Advanced Server, you need to run edb_sqlpatch on all your databases to complete the upgrade. This application checks that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool. !!! !!! Note After applying patches @@ -23,14 +23,14 @@ EDB Postgres Advanced Server 15.4.0 includes the following enhancements and bug | Type | Description | Addresses                | | | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | --- | | Upstream merge | Merged with community PostgreSQL 15.4. See the [PostgreSQL 15 Release Notes](https://www.postgresql.org/docs/15/release-15-4.html) for more information. | | | -| Security fix | EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path. | [CVE-2023-XXXXX-1](/security/advisories/cve2023xxxxx1/) | 11+ | -| Security fix | EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser. | [CVE-2023-XXXXX-2](/security/advisories/cve2023xxxxx2/) | 11+ | -| Security fix | EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory() | [CVE-2023-XXXXX-3](/security/advisories/cve2023xxxxx3/) | 11+ | -| Security fix | EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass | [CVE-2023-XXXXX-4](/security/advisories/cve2023xxxxx4/) | 11+ | -| Security fix | EDB Postgres Advanced Server (EPAS) permission bypass for materialized views | [CVE-2023-XXXXX-5](/security/advisories/cve2023xxxxx5/) | 11+ | -| Security fix | EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL | [CVE-2023-XXXXX-6](/security/advisories/cve2023xxxxx6/) | 11+ | -| Security fix | EDB Postgres Advanced Server (EPAS) permission bypass for large objects | [CVE-2023-XXXXX-7](/security/advisories/cve2023xxxxx7/) | 11+ | -| Security fix | EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission | [CVE-2023-XXXXX-8](/security/advisories/cve2023xxxxx8/) | 11+ | +| Security fix | EDB Postgres Advanced Server SECURITY DEFINER functions and procedures might be hijacked by way of search_path. | [CVE-2023-XXXXX-1](/security/advisories/cve2023xxxxx1/) | 11+ | +| Security fix | EDB Postgres Advanced Server dbms_aq helper function might run arbitrary SQL as a superuser. | [CVE-2023-XXXXX-2](/security/advisories/cve2023xxxxx2/) | 11+ | +| Security fix | EDB Postgres Advanced Server permissions bypass by way of accesshistory() | [CVE-2023-XXXXX-3](/security/advisories/cve2023xxxxx3/) | 11+ | +| Security fix | EDB Postgres Advanced Server UTL_FILE permission bypass | [CVE-2023-XXXXX-4](/security/advisories/cve2023xxxxx4/) | 11+ | +| Security fix | EDB Postgres Advanced Server permission bypass for materialized views | [CVE-2023-XXXXX-5](/security/advisories/cve2023xxxxx5/) | 11+ | +| Security fix | EDB Postgres Advanced Server authenticated users can fetch any URL | [CVE-2023-XXXXX-6](/security/advisories/cve2023xxxxx6/) | 11+ | +| Security fix | EDB Postgres Advanced Server permission bypass for large objects | [CVE-2023-XXXXX-7](/security/advisories/cve2023xxxxx7/) | 11+ | +| Security fix | EDB Postgres Advanced Server DBMS_PROFILER data might be removed without permission | [CVE-2023-XXXXX-8](/security/advisories/cve2023xxxxx8/) | 11+ | | Bug fix | Allowed subtypes in INDEX BY clause of the packaged collection. | #1371 | 11+ | | Bug fix | Fixed %type resolution when pointing to a packaged type field. | #1243 | 11+ | | Bug fix | Profile: Fixed upgrade when `REUSE` constraints were `ENABLED`/`DISABLED`. | #92739 | 11+ | From bf4bcb251089d8751be8ce7c868a278ed8902d3a Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 31 Aug 2023 14:37:14 -0400 Subject: [PATCH 014/255] Update epas15_4_0_rel_notes.mdx --- .../docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx b/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx index c7ba3885282..097a670e896 100644 --- a/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx +++ b/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx @@ -9,7 +9,7 @@ Released: 21 Aug 2023 Updated: 30 Aug 2023 !!! Important Upgrading -After you upgrade to this version of EDB Postgres Advanced Server, you need to run edb_sqlpatch on all your databases to complete the upgrade. This application checks that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool. +Once you upgrade to this version of EDB Postgres Advanced Server, you need to run edb_sqlpatch on all your databases to complete the upgrade. This application checks that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool. !!! !!! Note After applying patches From 92be23f4a84f11dcaa3344094b0fdca605179893 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Tue, 6 Jun 2023 09:59:07 -0400 Subject: [PATCH 015/255] Tech Partner Veeam Kasten Guide --- .../VeeamKasten/02-PartnerInformation.mdx | 12 +++++++ .../VeeamKasten/03-SolutionSummary.mdx | 8 +++++ .../VeeamKasten/04-ConfiguringVeeamKasten.mdx | 0 .../VeeamKasten/05-UsingVeeamKasten.mdx | 0 .../06-CertificationEnvironment.mdx | 10 ++++++ .../VeeamKasten/07-SupportandLogging.mdx | 31 +++++++++++++++++++ .../VeeamKasten/Images/PartnerProgram.jpg.png | 3 ++ .../partner_docs/VeeamKasten/index.mdx | 14 +++++++++ 8 files changed, 78 insertions(+) create mode 100644 advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx create mode 100644 advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx create mode 100644 advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx create mode 100644 advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx create mode 100644 advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx create mode 100644 advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx create mode 100644 advocacy_docs/partner_docs/VeeamKasten/Images/PartnerProgram.jpg.png create mode 100644 advocacy_docs/partner_docs/VeeamKasten/index.mdx diff --git a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx new file mode 100644 index 00000000000..5b80ceb0dcc --- /dev/null +++ b/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx @@ -0,0 +1,12 @@ +--- +title: 'Partner Information' +description: 'Details of the Partner' + +--- +|   |   | +| ----------- | ----------- | +| **Partner Name** | Veeam Kasten | +| **Web Site** | https://www.kasten.io/ | +| **Partner Product** | Kasten | +| **Version** | Kasten K10 | +| **Product Description** | | \ No newline at end of file diff --git a/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx b/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx new file mode 100644 index 00000000000..b074c1304f8 --- /dev/null +++ b/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx @@ -0,0 +1,8 @@ +--- +title: 'Solution Summary' +description: 'Explanation of the solution and its purpose' +--- + +Veeam Kasten is a data management platform built for Kubernetes that can provide enterprise operations teams with an easy-to-use and secure system for backup and restore of Kubernetes applications. Veeam Kasten can be used in conjunction with EDB Postgres for Kubernetes and the + +![](Images/.png) \ No newline at end of file diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx new file mode 100644 index 00000000000..e69de29bb2d diff --git a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx new file mode 100644 index 00000000000..e69de29bb2d diff --git a/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx new file mode 100644 index 00000000000..2e4eae2d28f --- /dev/null +++ b/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx @@ -0,0 +1,10 @@ +--- +title: 'Certification Environment' +description: 'Overview of the certification environment' +--- + +|   |   | +| ----------- | ----------- | +| **Certification Test Date** | , 2023 | +| **EDB Postgres Advanced Server** | | +| **Veeam Kasten** | | \ No newline at end of file diff --git a/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx new file mode 100644 index 00000000000..c3e84bfe4ee --- /dev/null +++ b/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx @@ -0,0 +1,31 @@ +--- +title: 'Support and Logging Details' +description: 'Details of the support process and logging information' +--- + +## Support + +Technical support for the use of these products is provided by both EDB and Veeam. A proper support contract is required to be in place at both EDB and Veeam. A support ticket can be opened on either side to start the process. If it is determined through the support ticket that resources from the other vendor is required, the customer should open a support ticket with that vendor through normal support channels. This will allow both companies to work together to help the customer as needed. + +## Logging + +**EDB Postgres Advanced Server Logs** + +Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance and from here you can navigate to `log`, `current_logfiles` or you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs. An example of the full path to view EDB Postgres Advanced Server logs: `/var/lib/edb/as15/data/log`. + +**EDB Postgres Extended Server Logs** + +Navigate to the `Data` directory in your chosen EDB Postgres Extended Server instance and from here you can navigate to `log`, or you can navigate to the `postgresql.conf` file where you can customize logging options. An example of the full path to view EDB Postgres Extended logs: `/var/lib/edb-pge/15/data/log`. + +**PostgreSQL Server Logs** + +The default log directories for PostgreSQL logs vary depending on the operating system: + +- Debian-based system: `/var/log/postgresql/postgresql-x.x.main.log. X.x.` + +- Red Hat-based system: `/var/lib/pgsql/data/pg_log` + +- Windows: `C:\Program Files\PostgreSQL\9.3\data\pg_log` + +**Veeam Logs** + diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/PartnerProgram.jpg.png b/advocacy_docs/partner_docs/VeeamKasten/Images/PartnerProgram.jpg.png new file mode 100644 index 00000000000..93e0514710b --- /dev/null +++ b/advocacy_docs/partner_docs/VeeamKasten/Images/PartnerProgram.jpg.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1953f3a5526ab37279a598f1c370c5acbf9f6d18f7902cb538161182fbed3b1f +size 57295 diff --git a/advocacy_docs/partner_docs/VeeamKasten/index.mdx b/advocacy_docs/partner_docs/VeeamKasten/index.mdx new file mode 100644 index 00000000000..a054806aef1 --- /dev/null +++ b/advocacy_docs/partner_docs/VeeamKasten/index.mdx @@ -0,0 +1,14 @@ +--- +title: 'Veeam Kasten Implementation Guide' +indexCards: simple +directoryDefaults: + iconName: handshake +--- + +

+ +

+

EDB GlobalConnect Technology Partner Implementation Guide

+

Veeam Kasten

+ +

This document is intended to augment each vendor’s product documentation in order to guide the reader in getting the products working together. It is not intended to show the optimal configuration for the certified integration.

\ No newline at end of file From 8df9cca3a0006ec264de03f7d43aaf5fc3e86805 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Wed, 7 Jun 2023 15:59:35 -0400 Subject: [PATCH 016/255] Index Change and Added Information --- .../VeeamKasten/03-SolutionSummary.mdx | 6 +- .../VeeamKasten/04-ConfiguringVeeamKasten.mdx | 316 ++++++++++++++++++ .../Images/KastenSolutionSummaryImage.png | 3 + src/pages/index.js | 3 + 4 files changed, 326 insertions(+), 2 deletions(-) create mode 100644 advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage.png diff --git a/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx b/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx index b074c1304f8..26a071ded35 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx @@ -3,6 +3,8 @@ title: 'Solution Summary' description: 'Explanation of the solution and its purpose' --- -Veeam Kasten is a data management platform built for Kubernetes that can provide enterprise operations teams with an easy-to-use and secure system for backup and restore of Kubernetes applications. Veeam Kasten can be used in conjunction with EDB Postgres for Kubernetes and the +Veeam Kasten is a data management platform built for Kubernetes that can provide enterprise operations teams with an easy-to-use and secure system for backup and restore of Kubernetes applications. Veeam Kasten can be used in conjunction with EDB Postgres for Kubernetes and the EDB external backup adapter to successfully backup and restore data with Veeam Kasten. -![](Images/.png) \ No newline at end of file +The EDB Postgres for Kubernetes [external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) allows for a third party tool such as Veeam Kasten to discover an API that is needed in order to create a successful backup. + +![Kasten K10 Architecture](Images/KastenSolutionSummaryImage.png) \ No newline at end of file diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index e69de29bb2d..747d230799e 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -0,0 +1,316 @@ +title: 'Configuration' +description: 'Walkthrough on configuring the integration' +--- + +Implementing EDB Postgres for Kubernetes with Veeam Kasten requires the following components: + +- EDB Postgres for Kubernetes +- EDB Postgres for Kubernetes external backup adapter +- Veeam Kasten K10 + +## Prerequisites + +- EDB Postgres for Kubernetes configured and running +- EDB Postgres for Kubernetes external backup adapter configured per your system requirements +- Veeam Kasten K10 installed on your system + + +## Install the Operator + +If you already have the EDB operator installed on Kubernetes you may skip this step. + +```bash +kubectl apply -f https://get.enterprisedb.io/cnp/postgresql-operator-1.19.1.yaml +``` + +Running this command will create the operator namespace where the controller will be running. + +## Create an EDB Cluster, Client and Add Data + +If, in your environment, you already have an EDB cluster configured you may skip this step. + +1. Initiate the below lines of code in your Kubernetes environment. + +```bash +kubctl create ns edb +kubectl apply -f cluster-example.yaml -n edb +``` +2. Wait until the cluster is completely ready. + +3. Install the cnp plugin, if you have already installed this you may skip this. + +```bash +curl -sSfL \ + https://github.com/EnterpriseDB/kubectl-cnp/raw/main/install.sh | \ + sudo sh -s -- -b /usr/local/bin +``` + +4. Create a client certificate to the database. + +```bash +kubectl cnp certificate cluster-app \ + --cnp-cluster cluster-example \ + --cnp-user app \ + -n edb +``` + +**cluster-example** Example: +``bash +# Example of PostgreSQL cluster +apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: Cluster +metadata: + name: cluster-example + annotations: + "k8s.enterprisedb.io/addons": '["external-backup-adapter-cluster"]' + "k8s.enterprisedb.io/externalBackupAdapterClusterConfig": |- + electedResourcesDecorators: + - key: "kasten-enterprisedb.io/elected" + metadataType: "label" + value: "true" + excludedResourcesDecorators: + - key: "kasten-enterprisedb.io/excluded" + metadataType: "label" + value: "true" + - key: "kasten-enterprisedb.io/excluded-reason" + metadataType: "annotation" + value: "Not necessary for backup" + backupInstanceDecorators: + - key: "kasten-enterprisedb.io/hasHooks" + metadataType: "label" + value: "true" + - key: "kanister.kasten.io/blueprint" + metadataType: "annotation" + value: "edb-hooks" + preBackupHookConfiguration: + container: + key: "kasten-enterprisedb.io/pre-backup-container" + command: + key: "kasten-enterprisedb.io/pre-backup-command" + onError: + key: "kasten-enterprisedb.io/pre-backup-on-error" + postBackupHookConfiguration: + container: + key: "kasten-enterprisedb.io/post-backup-container" + command: + key: "kasten-enterprisedb.io/post-backup-command" +spec: + instances: 3 + # Example of rolling update strategy: + # - unsupervised: automated update of the primary once all + # replicas have been upgraded (default) + # - supervised: requires manual supervision to perform + # the switchover of the primary + primaryUpdateStrategy: unsupervised + # Require 1Gi of space + storage: + size: 1Gi +``` + +5. Create the client. + +```bash +kubectl create -f client.yaml -n edb +``` +**client.yaml** Example: +```bash +apiVersion: apps/v1 +kind: Deployment +metadata: + name: cert-test +spec: + replicas: 1 + selector: + matchLabels: + app: webtest + template: + metadata: + labels: + app: webtest + spec: + containers: + - image: ghcr.io/cloudnative-pg/webtest:1.6.0 + name: cert-test + volumeMounts: + - name: secret-volume-root-ca + mountPath: /etc/secrets/ca + - name: secret-volume-app + mountPath: /etc/secrets/app + ports: + - containerPort: 8080 + env: + - name: PGPASSWORD + valueFrom: + secretKeyRef: + name: cluster-example-app + key: password + - name: DATABASE_URL + value: > + sslkey=/etc/secrets/app/tls.key + sslcert=/etc/secrets/app/tls.crt + sslrootcert=/etc/secrets/ca/ca.crt + host=cluster-example-rw.default.svc + dbname=app + user=app + sslmode=verify-full + - name: SQL_QUERY + value: SELECT 1 + volumes: + - name: secret-volume-root-ca + secret: + secretName: cluster-example-ca + defaultMode: 0600 + - name: secret-volume-app + secret: + secretName: cluster-app + defaultMode: 0600 +``` + +6. Add some data. + +```bash +kubectl exec -it deploy/cert-test -- bash +psql 'sslkey=/etc/secrets/app/tls.key sslcert=/etc/secrets/app/tls.crt sslrootcert=/etc/secrets/ca/ca.crt host=cluster-example-rw dbname=app user=app sslmode=verify-full' +\c app +DROP TABLE IF EXISTS links; +CREATE TABLE links ( + id SERIAL PRIMARY KEY, + url VARCHAR(255) NOT NULL, + name VARCHAR(255) NOT NULL, + description VARCHAR (255), + last_update DATE +); +INSERT INTO links (url, name, description, last_update) VALUES('https://kasten.io','Kasten','Backup on kubernetes',NOW()); +select * from links; +\q +exit +``` + +## Add the Backup Decorator Annotations to the Cluster + +If you created your cluster with the pieces from the previous section the **cluster-example** already includes the backup decorator, so you will not need to do this step again. If you are working with your own cluster you will need to add the backup decorator. + +1. Add the following annotations to your cluster: + +```bash +"k8s.enterprisedb.io/addons": '["external-backup-adapter-cluster"]' + "k8s.enterprisedb.io/externalBackupAdapterClusterConfig": |- + electedResourcesDecorators: + - key: "kasten-enterprisedb.io/elected" + metadataType: "label" + value: "true" + excludedResourcesDecorators: + - key: "kasten-enterprisedb.io/excluded" + metadataType: "label" + value: "true" + - key: "kasten-enterprisedb.io/excluded-reason" + metadataType: "annotation" + value: "Not necessary for backup" + backupInstanceDecorators: + - key: "kasten-enterprisedb.io/hasHooks" + metadataType: "label" + value: "true" + - key: "kanister.kasten.io/blueprint" + metadataType: "annotation" + value: "edb-hooks" + preBackupHookConfiguration: + container: + key: "kasten-enterprisedb.io/pre-backup-container" + command: + key: "kasten-enterprisedb.io/pre-backup-command" + onError: + key: "kasten-enterprisedb.io/pre-backup-on-error" + postBackupHookConfiguration: + container: + key: "kasten-enterprisedb.io/post-backup-container" + command: + key: "kasten-enterprisedb.io/post-backup-command" +``` + +## Install the EDB blueprint + +1. Enter the follwing command in your environment: + +```bash +kubectl create -f edb-hooks.yaml +``` + +**edb-hooks.yaml** Example: + +```bash +apiVersion: cr.kanister.io/v1alpha1 +kind: Blueprint +metadata: + name: edb-hooks + namespace: kasten-io +actions: + backupPrehook: + phases: + - func: KubeTask + name: edbPreBackupHook + args: + image: ghcr.io/kanisterio/kanister-kubectl-1.18:0.91.0 + command: + - bash + - -x + - -o + - errexit + - -o + - pipefail + - -c + - | + namespace={{ .Namespace.Name }} + selector='kasten-enterprisedb.io/hasHooks=true' + for pod in $(kubectl get po --no-headers -n $namespace -l $selector|awk '{print $1}') + do + preCommand=$(kubectl get po -n $namespace $pod -o jsonpath='{.metadata.annotations.kasten-enterprisedb\.io/pre-backup-command}') + preOnErrorCommand=$(kubectl get po -n $namespace $pod -o jsonpath='{.metadata.annotations.kasten-enterprisedb\.io/pre-backup-on-error}') + container=$(kubectl get po -n $namespace $pod -o jsonpath='{.metadata.annotations.kasten-enterprisedb\.io/pre-backup-container}') + command=${preCommand//[\[\]\"\,]/' '} + result=$(kubectl exec -it $pod -c $container -n $namespace $pod -- bash -c "if $command; then echo success; else echo failure; fi" | tail -1) + if [[ $result == "failure" ]] + then + echo "Error after running $preCommand in $pod/$container" + echo "Executing $preOnErrorCommand" + command=${preOnErrorCommand//[\[\]\"\,]/' '} + kubectl exec -it $pod -c $container -n $namespace $pod -- bash -c $command + exit 1 + fi + done + exit 0 + backupPosthook: + phases: + - func: KubeTask + name: edbPostBackupHook + args: + image: ghcr.io/kanisterio/kanister-kubectl-1.18:0.91.0 + command: + - bash + - -x + - -o + - errexit + - -o + - pipefail + - -c + - | + namespace={{ .Namespace.Name }} + selector='kasten-enterprisedb.io/hasHooks=true' + for pod in $(kubectl get po --no-headers -n $namespace -l $selector|awk '{print $1}') + do + postCommand=$(kubectl get po -n $namespace $pod -o jsonpath='{.metadata.annotations.kasten-enterprisedb\.io/post-backup-command}') + container=$(kubectl get po -n $namespace $pod -o jsonpath='{.metadata.annotations.kasten-enterprisedb\.io/post-backup-container}') + command=${postCommand//[\[\]\"\,]/' '} + result=$(kubectl exec -it $pod -c $container -n $namespace $pod -- bash -c "if $command; then echo success; else echo failure; fi" | tail -1) + if [[ $result == "failure" ]] + then + echo "Error after running $postCommand in $pod/$container" + exit 1 + fi + done + exit 0 +``` + + + + + diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage.png b/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage.png new file mode 100644 index 00000000000..024e1f828e8 --- /dev/null +++ b/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b91718c7283f21b6004f1a0503d2bc2d39b0ac44643aa57338311a066382b395 +size 314038 diff --git a/src/pages/index.js b/src/pages/index.js index 89f663535ac..82d40c8787c 100644 --- a/src/pages/index.js +++ b/src/pages/index.js @@ -343,6 +343,9 @@ const Page = () => ( Repostor Data Protector for PostgresSQL + + Veeam Kasten + Veritas NetBackup for PostgreSQL From 6de0541fad63c4f45599e62d8c69f9f12c52678a Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 8 Jun 2023 13:36:50 -0400 Subject: [PATCH 017/255] Guide info updates --- .../VeeamKasten/05-UsingVeeamKasten.mdx | 35 +++++++++++++++++++ .../Images/KastenBackupPolicywithHooks.png | 3 ++ 2 files changed, 38 insertions(+) create mode 100644 advocacy_docs/partner_docs/VeeamKasten/Images/KastenBackupPolicywithHooks.png diff --git a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx index e69de29bb2d..a00e995f898 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx @@ -0,0 +1,35 @@ +--- +title: 'Using' +description: 'Walkthrough of example usage scenarios' +--- + +When you have configured your Kubernetes environment per the Configuring section you will then be able to start taking backups and completing restores. + +## Create a Backup Policy with the EDB hooks + +In the `Configuring` section, you installed the EDB Blueprint with the edb-hooks.yaml file. You will now be able to create a backup policy with those hooks. + +1. Create a policy for the EDB namespace, you will need to set up a location profile for the export and kanister actions. + +Add the hooks example: + ![Kasten Backup Policy with EDB Hooks](Images/KastenBackupPolicywithHooks.png) + +## Launch a Backup + +1. Using Veeam Kasten K10 launch a backup that creates two restore points, a local and a remote. + +2. Delete the namespace `EDB`. + +```bash +kubectl delete ns edb +``` + +## Restore Database + +1. Go to your remote restore point. + +2. On the remote restore point select `restore`. + +3. After you have restored all of your data should be present. + + diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/KastenBackupPolicywithHooks.png b/advocacy_docs/partner_docs/VeeamKasten/Images/KastenBackupPolicywithHooks.png new file mode 100644 index 00000000000..b1982e965f4 --- /dev/null +++ b/advocacy_docs/partner_docs/VeeamKasten/Images/KastenBackupPolicywithHooks.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:356a3883638fa3a8cd847a04ec87c8e4e2dc6cb5398e1ba9c55a18df60e812ec +size 132778 From fd9b10e6ea6dfb0e4c6ee7669950e4dcfdbd9b07 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 8 Jun 2023 14:55:53 -0400 Subject: [PATCH 018/255] Configuring Update --- .../partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index 747d230799e..af2230d0ff7 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -1,3 +1,4 @@ +--- title: 'Configuration' description: 'Walkthrough on configuring the integration' --- From 0db50ea88a117089717979701d9b2d40eb99ef9e Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 8 Jun 2023 15:34:23 -0400 Subject: [PATCH 019/255] Syntax Updates --- .../partner_docs/VeeamKasten/02-PartnerInformation.mdx | 4 ++-- .../partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx | 3 ++- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx index 5b80ceb0dcc..d45ed1a6199 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx @@ -7,6 +7,6 @@ description: 'Details of the Partner' | ----------- | ----------- | | **Partner Name** | Veeam Kasten | | **Web Site** | https://www.kasten.io/ | -| **Partner Product** | Kasten | -| **Version** | Kasten K10 | +| **Partner Product** | Kasten K10 | +| **Version** | | | **Product Description** | | \ No newline at end of file diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index af2230d0ff7..a25d2611c33 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -56,7 +56,8 @@ kubectl cnp certificate cluster-app \ ``` **cluster-example** Example: -``bash + +```bash # Example of PostgreSQL cluster apiVersion: postgresql.k8s.enterprisedb.io/v1 kind: Cluster From 2c4243e2d5ecc54fc66bc142e4f7fff03e9f58b1 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 8 Jun 2023 19:11:32 -0400 Subject: [PATCH 020/255] Edits per Kasten Team --- .../VeeamKasten/02-PartnerInformation.mdx | 4 ++-- .../VeeamKasten/04-ConfiguringVeeamKasten.mdx | 5 +++++ .../VeeamKasten/05-UsingVeeamKasten.mdx | 22 ++++++++++--------- .../06-CertificationEnvironment.mdx | 4 ++-- .../VeeamKasten/07-SupportandLogging.mdx | 2 ++ 5 files changed, 23 insertions(+), 14 deletions(-) diff --git a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx index d45ed1a6199..7563a70c1ec 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx @@ -8,5 +8,5 @@ description: 'Details of the Partner' | **Partner Name** | Veeam Kasten | | **Web Site** | https://www.kasten.io/ | | **Partner Product** | Kasten K10 | -| **Version** | | -| **Product Description** | | \ No newline at end of file +| **Version** | Kasten 6.0 | +| **Product Description** | Kasten K10 is a Cloud Native data management platform for Day 2 operations. Purpose built for Kubernetes, Kasten backups and restores your applications, handles disaster recovery and manages application migration. Kasten can implement with EDB Postgres for Kubernetes to create fast backups and restores. | \ No newline at end of file diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index a25d2611c33..5054ca7a06b 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -311,7 +311,12 @@ actions: done exit 0 ``` +## Create a Backup Policy with the EDB hooks +1. Create a policy for the EDB namespace, you will need to set up a location profile for the export and kanister actions. + +Add the hooks example: + ![Kasten Backup Policy with EDB Hooks](Images/KastenBackupPolicywithHooks.png) diff --git a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx index a00e995f898..c53b1c0854a 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx @@ -3,21 +3,23 @@ title: 'Using' description: 'Walkthrough of example usage scenarios' --- -When you have configured your Kubernetes environment per the Configuring section you will then be able to start taking backups and completing restores. - -## Create a Backup Policy with the EDB hooks - -In the `Configuring` section, you installed the EDB Blueprint with the edb-hooks.yaml file. You will now be able to create a backup policy with those hooks. - -1. Create a policy for the EDB namespace, you will need to set up a location profile for the export and kanister actions. - -Add the hooks example: - ![Kasten Backup Policy with EDB Hooks](Images/KastenBackupPolicywithHooks.png) +When you have configured your Kubernetes environment per the `Configuring` section you will then be able to start taking backups and completing restores. ## Launch a Backup 1. Using Veeam Kasten K10 launch a backup that creates two restore points, a local and a remote. +!!! Note + The Veeam backup process is explained below: + 1. EDB elects a replica for the backup. + . Kasten will discover the replica. + 3. Kasten calls the EDB pre-backup command on the discovered replica. + 4. The replica becomes ready for the backup. + 5. Kasten takes the backup. + 6. Kasten calls the EDB post backup command on the replica. + 7. The replica leaves the backup mode. + 8. The backup is then over and is consistent for a restore. + 2. Delete the namespace `EDB`. ```bash diff --git a/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx index 2e4eae2d28f..27d56981acb 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx @@ -6,5 +6,5 @@ description: 'Overview of the certification environment' |   |   | | ----------- | ----------- | | **Certification Test Date** | , 2023 | -| **EDB Postgres Advanced Server** | | -| **Veeam Kasten** | | \ No newline at end of file +| **EDB Postgres for Kubernetes** | 1.19.1 | +| **Veeam Kasten** | 6.0 | \ No newline at end of file diff --git a/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx index c3e84bfe4ee..fd9cdeebcb0 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx @@ -29,3 +29,5 @@ The default log directories for PostgreSQL logs vary depending on the operating **Veeam Logs** +On the Kasten UI you need to navigate to `Settings` then `Support` then you will click `Download Logs`. + From e0f5421a11c718a6b1a8451e4b7f50c8bdc871ec Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Fri, 9 Jun 2023 09:31:07 -0400 Subject: [PATCH 021/255] Logging Image Added --- .../partner_docs/VeeamKasten/07-SupportandLogging.mdx | 2 +- .../partner_docs/VeeamKasten/Images/VeeamKastenLogging.png | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) create mode 100644 advocacy_docs/partner_docs/VeeamKasten/Images/VeeamKastenLogging.png diff --git a/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx index fd9cdeebcb0..fa5287e1f82 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx @@ -30,4 +30,4 @@ The default log directories for PostgreSQL logs vary depending on the operating **Veeam Logs** On the Kasten UI you need to navigate to `Settings` then `Support` then you will click `Download Logs`. - + ![Veeam Kasten Logs](Images/VeeamKastenLogging.png) diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/VeeamKastenLogging.png b/advocacy_docs/partner_docs/VeeamKasten/Images/VeeamKastenLogging.png new file mode 100644 index 00000000000..a55d3875599 --- /dev/null +++ b/advocacy_docs/partner_docs/VeeamKasten/Images/VeeamKastenLogging.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e37ff91381e9c042ec63d7777030b8005171660a0d6b15e67f7269fef85a9d90 +size 129377 From c2bdac815a8786050e8961091523f22c921b6c15 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Tue, 6 Jun 2023 09:59:07 -0400 Subject: [PATCH 022/255] Tech Partner Veeam Kasten Guide --- .../partner_docs/VeeamKasten/02-PartnerInformation.mdx | 2 +- advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx | 2 +- .../partner_docs/VeeamKasten/06-CertificationEnvironment.mdx | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx index 7563a70c1ec..642d0c0ce36 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx @@ -9,4 +9,4 @@ description: 'Details of the Partner' | **Web Site** | https://www.kasten.io/ | | **Partner Product** | Kasten K10 | | **Version** | Kasten 6.0 | -| **Product Description** | Kasten K10 is a Cloud Native data management platform for Day 2 operations. Purpose built for Kubernetes, Kasten backups and restores your applications, handles disaster recovery and manages application migration. Kasten can implement with EDB Postgres for Kubernetes to create fast backups and restores. | \ No newline at end of file +| **Product Description** | Kasten K10 is a Cloud Native data management platform for Day 2 operations. Purpose built for Kubernetes, Kasten backups and restores your applications, handles disaster recovery and manages application migration. Kasten can implement with EDB Postgres for Kubernetes to create fast backups and restores. | diff --git a/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx b/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx index 26a071ded35..bfb5f5857ae 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx @@ -7,4 +7,4 @@ Veeam Kasten is a data management platform built for Kubernetes that can provide The EDB Postgres for Kubernetes [external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) allows for a third party tool such as Veeam Kasten to discover an API that is needed in order to create a successful backup. -![Kasten K10 Architecture](Images/KastenSolutionSummaryImage.png) \ No newline at end of file +![Kasten K10 Architecture](Images/KastenSolutionSummaryImage.png) diff --git a/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx index 27d56981acb..5d33117b4d9 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx @@ -7,4 +7,4 @@ description: 'Overview of the certification environment' | ----------- | ----------- | | **Certification Test Date** | , 2023 | | **EDB Postgres for Kubernetes** | 1.19.1 | -| **Veeam Kasten** | 6.0 | \ No newline at end of file +| **Veeam Kasten** | 6.0 | From 3524c40778ca87f6f660a843ce31c8031971d734 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Wed, 7 Jun 2023 15:59:35 -0400 Subject: [PATCH 023/255] Index Change and Added Information --- .../VeeamKasten/04-ConfiguringVeeamKasten.mdx | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index 5054ca7a06b..bae596f2fc0 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -1,4 +1,3 @@ ---- title: 'Configuration' description: 'Walkthrough on configuring the integration' --- @@ -56,8 +55,7 @@ kubectl cnp certificate cluster-app \ ``` **cluster-example** Example: - -```bash +``bash # Example of PostgreSQL cluster apiVersion: postgresql.k8s.enterprisedb.io/v1 kind: Cluster @@ -311,12 +309,6 @@ actions: done exit 0 ``` -## Create a Backup Policy with the EDB hooks - -1. Create a policy for the EDB namespace, you will need to set up a location profile for the export and kanister actions. - -Add the hooks example: - ![Kasten Backup Policy with EDB Hooks](Images/KastenBackupPolicywithHooks.png) From a1b94b25587ddd7b57ff221d3580e6ba201e158d Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 8 Jun 2023 13:36:50 -0400 Subject: [PATCH 024/255] Guide info updates --- .../partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx index c53b1c0854a..9d368d70026 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx @@ -3,7 +3,16 @@ title: 'Using' description: 'Walkthrough of example usage scenarios' --- -When you have configured your Kubernetes environment per the `Configuring` section you will then be able to start taking backups and completing restores. +When you have configured your Kubernetes environment per the Configuring section you will then be able to start taking backups and completing restores. + +## Create a Backup Policy with the EDB hooks + +In the `Configuring` section, you installed the EDB Blueprint with the edb-hooks.yaml file. You will now be able to create a backup policy with those hooks. + +1. Create a policy for the EDB namespace, you will need to set up a location profile for the export and kanister actions. + +Add the hooks example: + ![Kasten Backup Policy with EDB Hooks](Images/KastenBackupPolicywithHooks.png) ## Launch a Backup From 0d5c5e8ae4985436d0887bab8f972c08d8b84d9b Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 8 Jun 2023 14:55:53 -0400 Subject: [PATCH 025/255] Configuring Update --- .../partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index bae596f2fc0..ec1dcd74f1a 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -1,3 +1,4 @@ +--- title: 'Configuration' description: 'Walkthrough on configuring the integration' --- From 469b085b10233c598d3b15abcced982c7f8c5207 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 8 Jun 2023 15:34:23 -0400 Subject: [PATCH 026/255] Syntax Updates --- .../partner_docs/VeeamKasten/02-PartnerInformation.mdx | 4 ++-- .../partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx | 3 ++- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx index 642d0c0ce36..a3cd807fcec 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx @@ -8,5 +8,5 @@ description: 'Details of the Partner' | **Partner Name** | Veeam Kasten | | **Web Site** | https://www.kasten.io/ | | **Partner Product** | Kasten K10 | -| **Version** | Kasten 6.0 | -| **Product Description** | Kasten K10 is a Cloud Native data management platform for Day 2 operations. Purpose built for Kubernetes, Kasten backups and restores your applications, handles disaster recovery and manages application migration. Kasten can implement with EDB Postgres for Kubernetes to create fast backups and restores. | +| **Version** | | +| **Product Description** | | diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index ec1dcd74f1a..37d05336b5b 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -56,7 +56,8 @@ kubectl cnp certificate cluster-app \ ``` **cluster-example** Example: -``bash + +```bash # Example of PostgreSQL cluster apiVersion: postgresql.k8s.enterprisedb.io/v1 kind: Cluster From 66eb62e657dba3e908f2e406aedcbbd56d034ff8 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 8 Jun 2023 19:11:32 -0400 Subject: [PATCH 027/255] Edits per Kasten Team --- .../VeeamKasten/02-PartnerInformation.mdx | 4 ++-- .../VeeamKasten/04-ConfiguringVeeamKasten.mdx | 5 +++++ .../partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx | 11 +---------- .../partner_docs/VeeamKasten/07-SupportandLogging.mdx | 1 - 4 files changed, 8 insertions(+), 13 deletions(-) diff --git a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx index a3cd807fcec..642d0c0ce36 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx @@ -8,5 +8,5 @@ description: 'Details of the Partner' | **Partner Name** | Veeam Kasten | | **Web Site** | https://www.kasten.io/ | | **Partner Product** | Kasten K10 | -| **Version** | | -| **Product Description** | | +| **Version** | Kasten 6.0 | +| **Product Description** | Kasten K10 is a Cloud Native data management platform for Day 2 operations. Purpose built for Kubernetes, Kasten backups and restores your applications, handles disaster recovery and manages application migration. Kasten can implement with EDB Postgres for Kubernetes to create fast backups and restores. | diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index 37d05336b5b..534ba58c6c2 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -311,7 +311,12 @@ actions: done exit 0 ``` +## Create a Backup Policy with the EDB hooks +1. Create a policy for the EDB namespace, you will need to set up a location profile for the export and kanister actions. + +Add the hooks example: + ![Kasten Backup Policy with EDB Hooks](Images/KastenBackupPolicywithHooks.png) diff --git a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx index 9d368d70026..c53b1c0854a 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx @@ -3,16 +3,7 @@ title: 'Using' description: 'Walkthrough of example usage scenarios' --- -When you have configured your Kubernetes environment per the Configuring section you will then be able to start taking backups and completing restores. - -## Create a Backup Policy with the EDB hooks - -In the `Configuring` section, you installed the EDB Blueprint with the edb-hooks.yaml file. You will now be able to create a backup policy with those hooks. - -1. Create a policy for the EDB namespace, you will need to set up a location profile for the export and kanister actions. - -Add the hooks example: - ![Kasten Backup Policy with EDB Hooks](Images/KastenBackupPolicywithHooks.png) +When you have configured your Kubernetes environment per the `Configuring` section you will then be able to start taking backups and completing restores. ## Launch a Backup diff --git a/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx index fa5287e1f82..76fa1e74817 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx @@ -30,4 +30,3 @@ The default log directories for PostgreSQL logs vary depending on the operating **Veeam Logs** On the Kasten UI you need to navigate to `Settings` then `Support` then you will click `Download Logs`. - ![Veeam Kasten Logs](Images/VeeamKastenLogging.png) From 2427086afe9c62a4b4722d06dfe54ae5ccb96842 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Fri, 9 Jun 2023 09:31:07 -0400 Subject: [PATCH 028/255] Logging Image Added --- advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx index 76fa1e74817..fa5287e1f82 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx @@ -30,3 +30,4 @@ The default log directories for PostgreSQL logs vary depending on the operating **Veeam Logs** On the Kasten UI you need to navigate to `Settings` then `Support` then you will click `Download Logs`. + ![Veeam Kasten Logs](Images/VeeamKastenLogging.png) From 13f25d1d9e74d570123b54069a2f4ed4e1c8103a Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Mon, 28 Aug 2023 09:29:48 -0400 Subject: [PATCH 029/255] Guide updates per testing --- .../VeeamKasten/04-ConfiguringVeeamKasten.mdx | 43 ++++--------------- .../VeeamKasten/05-UsingVeeamKasten.mdx | 2 +- .../06-CertificationEnvironment.mdx | 2 +- 3 files changed, 11 insertions(+), 36 deletions(-) diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index 534ba58c6c2..a98a3db9963 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -21,7 +21,7 @@ Implementing EDB Postgres for Kubernetes with Veeam Kasten requires the followin If you already have the EDB operator installed on Kubernetes you may skip this step. ```bash -kubectl apply -f https://get.enterprisedb.io/cnp/postgresql-operator-1.19.1.yaml +kubectl apply -f https://get.enterprisedb.io/cnp/postgresql-operator-1.20.2.yaml ``` Running this command will create the operator namespace where the controller will be running. @@ -38,6 +38,12 @@ kubectl apply -f cluster-example.yaml -n edb ``` 2. Wait until the cluster is completely ready. +```bash +kubectl get clusters.postgresql.k8s.enterprisedb.io -n edb +NAME AGE INSTANCES READY STATUS PRIMARY +cluster-example 19m 3 3 Cluster in healthy state cluster-example-1 +``` + 3. Install the cnp plugin, if you have already installed this you may skip this. ```bash @@ -64,38 +70,7 @@ kind: Cluster metadata: name: cluster-example annotations: - "k8s.enterprisedb.io/addons": '["external-backup-adapter-cluster"]' - "k8s.enterprisedb.io/externalBackupAdapterClusterConfig": |- - electedResourcesDecorators: - - key: "kasten-enterprisedb.io/elected" - metadataType: "label" - value: "true" - excludedResourcesDecorators: - - key: "kasten-enterprisedb.io/excluded" - metadataType: "label" - value: "true" - - key: "kasten-enterprisedb.io/excluded-reason" - metadataType: "annotation" - value: "Not necessary for backup" - backupInstanceDecorators: - - key: "kasten-enterprisedb.io/hasHooks" - metadataType: "label" - value: "true" - - key: "kanister.kasten.io/blueprint" - metadataType: "annotation" - value: "edb-hooks" - preBackupHookConfiguration: - container: - key: "kasten-enterprisedb.io/pre-backup-container" - command: - key: "kasten-enterprisedb.io/pre-backup-command" - onError: - key: "kasten-enterprisedb.io/pre-backup-on-error" - postBackupHookConfiguration: - container: - key: "kasten-enterprisedb.io/post-backup-container" - command: - key: "kasten-enterprisedb.io/post-backup-command" + "k8s.enterprisedb.io/addons": '["kasten"]' spec: instances: 3 # Example of rolling update strategy: @@ -190,7 +165,7 @@ exit ## Add the Backup Decorator Annotations to the Cluster -If you created your cluster with the pieces from the previous section the **cluster-example** already includes the backup decorator, so you will not need to do this step again. If you are working with your own cluster you will need to add the backup decorator. +If you create the cluter from the previous section the ***cluster-example*** already includes the Kasten addon therefore you can skip this part. If you are working with your own cluster you will need to add the Kasten addon. 1. Add the following annotations to your cluster: diff --git a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx index c53b1c0854a..bd2f0483e62 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx @@ -12,7 +12,7 @@ When you have configured your Kubernetes environment per the `Configuring` secti !!! Note The Veeam backup process is explained below: 1. EDB elects a replica for the backup. - . Kasten will discover the replica. + 2. Kasten will discover the replica. 3. Kasten calls the EDB pre-backup command on the discovered replica. 4. The replica becomes ready for the backup. 5. Kasten takes the backup. diff --git a/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx index 5d33117b4d9..6cf41fdedae 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx @@ -6,5 +6,5 @@ description: 'Overview of the certification environment' |   |   | | ----------- | ----------- | | **Certification Test Date** | , 2023 | -| **EDB Postgres for Kubernetes** | 1.19.1 | +| **EDB Postgres for Kubernetes** | 1.20.2 | | **Veeam Kasten** | 6.0 | From e66d59fa34d60c465c8768685c5fb2ccac8b9e95 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Mon, 28 Aug 2023 09:36:32 -0400 Subject: [PATCH 030/255] Date Edits and Image Add --- advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx | 3 ++- .../partner_docs/VeeamKasten/06-CertificationEnvironment.mdx | 2 +- .../partner_docs/VeeamKasten/Images/KastenRestorePoint.png | 3 +++ 3 files changed, 6 insertions(+), 2 deletions(-) create mode 100644 advocacy_docs/partner_docs/VeeamKasten/Images/KastenRestorePoint.png diff --git a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx index bd2f0483e62..75334c99a2e 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx @@ -32,6 +32,7 @@ kubectl delete ns edb 2. On the remote restore point select `restore`. -3. After you have restored all of your data should be present. +3. After you have restored all of your data will be present. + ![Kasten Data Restore Point](Images/KastenRestorePoint.png) diff --git a/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx index 6cf41fdedae..719c2a6a515 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx @@ -5,6 +5,6 @@ description: 'Overview of the certification environment' |   |   | | ----------- | ----------- | -| **Certification Test Date** | , 2023 | +| **Certification Test Date** | August 28, 2023 | | **EDB Postgres for Kubernetes** | 1.20.2 | | **Veeam Kasten** | 6.0 | diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/KastenRestorePoint.png b/advocacy_docs/partner_docs/VeeamKasten/Images/KastenRestorePoint.png new file mode 100644 index 00000000000..5c5f531b693 --- /dev/null +++ b/advocacy_docs/partner_docs/VeeamKasten/Images/KastenRestorePoint.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea7affcee5b936ae73b56f332769c77d9d77c6e6daa2a622f9326d3325889ec9 +size 158082 From 4ae744077e4f1dba6e02531e386031485d3bfbd7 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Wed, 30 Aug 2023 08:41:19 -0400 Subject: [PATCH 031/255] Edit from Kasten Suggestions --- .../VeeamKasten/04-ConfiguringVeeamKasten.mdx | 39 ++----------------- 1 file changed, 4 insertions(+), 35 deletions(-) diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index a98a3db9963..ac54b2051a1 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -61,7 +61,7 @@ kubectl cnp certificate cluster-app \ -n edb ``` -**cluster-example** Example: +**cluster-example.yaml** Example: ```bash # Example of PostgreSQL cluster @@ -165,43 +165,12 @@ exit ## Add the Backup Decorator Annotations to the Cluster -If you create the cluter from the previous section the ***cluster-example*** already includes the Kasten addon therefore you can skip this part. If you are working with your own cluster you will need to add the Kasten addon. +If you create the cluter from the previous section the ***cluster-example.yaml*** already includes the Kasten addon therefore you can skip this part. If you are working with your own cluster you will need to add the Kasten addon. -1. Add the following annotations to your cluster: +1. Add the following annotations to your cluster, in the above ***cluster-example.yaml*** there is an example of where to add the annotation. ```bash -"k8s.enterprisedb.io/addons": '["external-backup-adapter-cluster"]' - "k8s.enterprisedb.io/externalBackupAdapterClusterConfig": |- - electedResourcesDecorators: - - key: "kasten-enterprisedb.io/elected" - metadataType: "label" - value: "true" - excludedResourcesDecorators: - - key: "kasten-enterprisedb.io/excluded" - metadataType: "label" - value: "true" - - key: "kasten-enterprisedb.io/excluded-reason" - metadataType: "annotation" - value: "Not necessary for backup" - backupInstanceDecorators: - - key: "kasten-enterprisedb.io/hasHooks" - metadataType: "label" - value: "true" - - key: "kanister.kasten.io/blueprint" - metadataType: "annotation" - value: "edb-hooks" - preBackupHookConfiguration: - container: - key: "kasten-enterprisedb.io/pre-backup-container" - command: - key: "kasten-enterprisedb.io/pre-backup-command" - onError: - key: "kasten-enterprisedb.io/pre-backup-on-error" - postBackupHookConfiguration: - container: - key: "kasten-enterprisedb.io/post-backup-container" - command: - key: "kasten-enterprisedb.io/post-backup-command" +"k8s.enterprisedb.io/addons": '["kasten"]' ``` ## Install the EDB blueprint From b63a2d09277c1f1786ab547e49c2b9aa828dd2be Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Wed, 30 Aug 2023 09:53:37 -0400 Subject: [PATCH 032/255] Syntax Edit --- .../partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index ac54b2051a1..25a1e10882b 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -165,9 +165,9 @@ exit ## Add the Backup Decorator Annotations to the Cluster -If you create the cluter from the previous section the ***cluster-example.yaml*** already includes the Kasten addon therefore you can skip this part. If you are working with your own cluster you will need to add the Kasten addon. +If you create the cluter from the previous section the **cluster-example.yaml** already includes the Kasten addon therefore you can skip this part. If you are working with your own cluster you will need to add the Kasten addon. -1. Add the following annotations to your cluster, in the above ***cluster-example.yaml*** there is an example of where to add the annotation. +1. Add the following annotations to your cluster, in the above **cluster-example.yaml** there is an example of where to add the annotation. ```bash "k8s.enterprisedb.io/addons": '["kasten"]' From b4d783f89a3bf47c7f287bbd54c9e95abf3212b0 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 31 Aug 2023 14:42:26 -0400 Subject: [PATCH 033/255] First round of review edits --- .../partner_docs/VeeamKasten/02-PartnerInformation.mdx | 2 +- .../partner_docs/VeeamKasten/03-SolutionSummary.mdx | 2 +- .../partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx | 6 +++--- .../partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx | 2 +- .../partner_docs/VeeamKasten/07-SupportandLogging.mdx | 4 ---- .../VeeamKasten/Images/KastenSolutionSummaryImage.png | 4 ++-- .../VeeamKasten/Images/KastenSolutionSummaryImage2.png | 3 +++ 7 files changed, 11 insertions(+), 12 deletions(-) create mode 100644 advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage2.png diff --git a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx index 642d0c0ce36..c6deb89af54 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx @@ -9,4 +9,4 @@ description: 'Details of the Partner' | **Web Site** | https://www.kasten.io/ | | **Partner Product** | Kasten K10 | | **Version** | Kasten 6.0 | -| **Product Description** | Kasten K10 is a Cloud Native data management platform for Day 2 operations. Purpose built for Kubernetes, Kasten backups and restores your applications, handles disaster recovery and manages application migration. Kasten can implement with EDB Postgres for Kubernetes to create fast backups and restores. | +| **Product Description** | Kasten K10 is a Cloud Native data management platform for Day 2 operations. Purpose built for Kubernetes, Kasten backups and restores your applications, handles disaster recovery and manages application migration. Kasten can be implemented with EDB Postgres for Kubernetes to create fast backups and restores. | diff --git a/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx b/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx index bfb5f5857ae..079c65bd4e7 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx @@ -3,7 +3,7 @@ title: 'Solution Summary' description: 'Explanation of the solution and its purpose' --- -Veeam Kasten is a data management platform built for Kubernetes that can provide enterprise operations teams with an easy-to-use and secure system for backup and restore of Kubernetes applications. Veeam Kasten can be used in conjunction with EDB Postgres for Kubernetes and the EDB external backup adapter to successfully backup and restore data with Veeam Kasten. +Veeam Kasten is a data management platform built for Kubernetes that can provide enterprise operations teams with an easy-to-use and secure system for backup and restore of Kubernetes applications. Veeam Kasten can be used in conjunction with EDB Postgres for Kubernetes and the EDB external backup adapter to successfully backup and restore data. The EDB Postgres for Kubernetes [external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) allows for a third party tool such as Veeam Kasten to discover an API that is needed in order to create a successful backup. diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index 25a1e10882b..898e300809e 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -5,9 +5,9 @@ description: 'Walkthrough on configuring the integration' Implementing EDB Postgres for Kubernetes with Veeam Kasten requires the following components: -- EDB Postgres for Kubernetes -- EDB Postgres for Kubernetes external backup adapter -- Veeam Kasten K10 +- [EDB Postgres for Kubernetes](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/) +- [EDB Postgres for Kubernetes external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) +- [Veeam Kasten K10](https://docs.kasten.io/latest/index.html) ## Prerequisites diff --git a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx index 75334c99a2e..a0adc3d398d 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx @@ -7,7 +7,7 @@ When you have configured your Kubernetes environment per the `Configuring` secti ## Launch a Backup -1. Using Veeam Kasten K10 launch a backup that creates two restore points, a local and a remote. +1. Use Veeam Kasten K10 launch a backup that creates two restore points, a local and a remote. !!! Note The Veeam backup process is explained below: diff --git a/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx index fa5287e1f82..4ba382d07b7 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx @@ -13,10 +13,6 @@ Technical support for the use of these products is provided by both EDB and Veea Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance and from here you can navigate to `log`, `current_logfiles` or you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs. An example of the full path to view EDB Postgres Advanced Server logs: `/var/lib/edb/as15/data/log`. -**EDB Postgres Extended Server Logs** - -Navigate to the `Data` directory in your chosen EDB Postgres Extended Server instance and from here you can navigate to `log`, or you can navigate to the `postgresql.conf` file where you can customize logging options. An example of the full path to view EDB Postgres Extended logs: `/var/lib/edb-pge/15/data/log`. - **PostgreSQL Server Logs** The default log directories for PostgreSQL logs vary depending on the operating system: diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage.png b/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage.png index 024e1f828e8..ad2ac426c49 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage.png +++ b/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b91718c7283f21b6004f1a0503d2bc2d39b0ac44643aa57338311a066382b395 -size 314038 +oid sha256:a89f021a8af1b3054ec7906ed7b4fc67071ddba05858aad34d7301a60fab7d1b +size 434992 diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage2.png b/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage2.png new file mode 100644 index 00000000000..024e1f828e8 --- /dev/null +++ b/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage2.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b91718c7283f21b6004f1a0503d2bc2d39b0ac44643aa57338311a066382b395 +size 314038 From f412a67f67b695276047441d4ec8e7fda5746575 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 31 Aug 2023 16:27:54 -0400 Subject: [PATCH 034/255] Guide Review Meeting Edits 1 --- .../VeeamKasten/04-ConfiguringVeeamKasten.mdx | 64 ++++++++++--------- .../VeeamKasten/05-UsingVeeamKasten.mdx | 6 +- 2 files changed, 38 insertions(+), 32 deletions(-) diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index 898e300809e..631eb026cbf 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -15,10 +15,13 @@ Implementing EDB Postgres for Kubernetes with Veeam Kasten requires the followin - EDB Postgres for Kubernetes external backup adapter configured per your system requirements - Veeam Kasten K10 installed on your system +!!! Note + The following steps will walk through a sample deployment from start to finish. You may already have some of these steps implemented in your environment, and if so you can skip that particular step. + The **Add the Backup Decorator Annotations to the Cluster** section is the important section for the Kasten addon integration. ## Install the Operator -If you already have the EDB operator installed on Kubernetes you may skip this step. +1. Install the EDB Postgres for Kubernetes operator. ```bash kubectl apply -f https://get.enterprisedb.io/cnp/postgresql-operator-1.20.2.yaml @@ -28,14 +31,36 @@ Running this command will create the operator namespace where the controller wil ## Create an EDB Cluster, Client and Add Data -If, in your environment, you already have an EDB cluster configured you may skip this step. - -1. Initiate the below lines of code in your Kubernetes environment. +1. Initiate the below lines of code in your Kubernetes environment to create a specific namespace and apply your .yaml file. ```bash kubctl create ns edb kubectl apply -f cluster-example.yaml -n edb ``` + +###Example **cluster-example.yaml** file: + +```bash +# Example of PostgreSQL cluster +apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: Cluster +metadata: + name: cluster-example + annotations: + "k8s.enterprisedb.io/addons": '["kasten"]' +spec: + instances: 3 + # Example of rolling update strategy: + # - unsupervised: automated update of the primary once all + # replicas have been upgraded (default) + # - supervised: requires manual supervision to perform + # the switchover of the primary + primaryUpdateStrategy: unsupervised + # Require 1Gi of space + storage: + size: 1Gi +``` + 2. Wait until the cluster is completely ready. ```bash @@ -44,7 +69,7 @@ NAME AGE INSTANCES READY STATUS PRIMARY cluster-example 19m 3 3 Cluster in healthy state cluster-example-1 ``` -3. Install the cnp plugin, if you have already installed this you may skip this. +3. Install the cnp plugin. ```bash curl -sSfL \ @@ -61,29 +86,6 @@ kubectl cnp certificate cluster-app \ -n edb ``` -**cluster-example.yaml** Example: - -```bash -# Example of PostgreSQL cluster -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example - annotations: - "k8s.enterprisedb.io/addons": '["kasten"]' -spec: - instances: 3 - # Example of rolling update strategy: - # - unsupervised: automated update of the primary once all - # replicas have been upgraded (default) - # - supervised: requires manual supervision to perform - # the switchover of the primary - primaryUpdateStrategy: unsupervised - # Require 1Gi of space - storage: - size: 1Gi -``` - 5. Create the client. ```bash @@ -143,7 +145,7 @@ spec: defaultMode: 0600 ``` -6. Add some data. +6. Add some data into the cluster to test the backup and restore, the following is sample data that was used for this example. ```bash kubectl exec -it deploy/cert-test -- bash @@ -257,7 +259,9 @@ actions: ``` ## Create a Backup Policy with the EDB hooks -1. Create a policy for the EDB namespace, you will need to set up a location profile for the export and kanister actions. +1. Launch your Kasten K10 interface. + +2. Create a policy for the EDB namespace, you will need to set up a location profile for the export and kanister actions. Add the hooks example: ![Kasten Backup Policy with EDB Hooks](Images/KastenBackupPolicywithHooks.png) diff --git a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx index a0adc3d398d..9c6bf425591 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx @@ -7,7 +7,9 @@ When you have configured your Kubernetes environment per the `Configuring` secti ## Launch a Backup -1. Use Veeam Kasten K10 launch a backup that creates two restore points, a local and a remote. +1. Launch your Kasten K10 interface. + +2. Use Veeam Kasten K10 launch a backup that creates two restore points, a local and a remote. !!! Note The Veeam backup process is explained below: @@ -20,7 +22,7 @@ When you have configured your Kubernetes environment per the `Configuring` secti 7. The replica leaves the backup mode. 8. The backup is then over and is consistent for a restore. -2. Delete the namespace `EDB`. +3. To get ready for a Kasten K10 to complete a restore, this example deleted the namespace `EDB`. ```bash kubectl delete ns edb From 6465c00f661d156b52f9f6766295ebdf4635f559 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Fri, 1 Sep 2023 09:10:46 -0400 Subject: [PATCH 035/255] Guide Review Edits 2 --- .../partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx | 6 +++--- .../VeeamKasten/06-CertificationEnvironment.mdx | 1 + 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index 631eb026cbf..093fe8bebc8 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -38,7 +38,7 @@ kubctl create ns edb kubectl apply -f cluster-example.yaml -n edb ``` -###Example **cluster-example.yaml** file: +### Example **cluster-example.yaml** file: ```bash # Example of PostgreSQL cluster @@ -91,7 +91,7 @@ kubectl cnp certificate cluster-app \ ```bash kubectl create -f client.yaml -n edb ``` -**client.yaml** Example: +### Example **client.yaml** file: ```bash apiVersion: apps/v1 kind: Deployment @@ -183,7 +183,7 @@ If you create the cluter from the previous section the **cluster-example.yaml** kubectl create -f edb-hooks.yaml ``` -**edb-hooks.yaml** Example: +### Example **edb-hooks.yaml** file: ```bash apiVersion: cr.kanister.io/v1alpha1 diff --git a/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx index 719c2a6a515..8dac87a7df8 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx @@ -7,4 +7,5 @@ description: 'Overview of the certification environment' | ----------- | ----------- | | **Certification Test Date** | August 28, 2023 | | **EDB Postgres for Kubernetes** | 1.20.2 | +| **EDB Postgres for Kubernetes External Backup Adapter** | | **Veeam Kasten** | 6.0 | From f426c3dba2b5711c0c684d722e7dd4827f0664cd Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Fri, 1 Sep 2023 16:27:03 -0400 Subject: [PATCH 036/255] Review Round 2 Edits --- .../VeeamKasten/05-UsingVeeamKasten.mdx | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx index 9c6bf425591..2275b542b5a 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx @@ -11,6 +11,8 @@ When you have configured your Kubernetes environment per the `Configuring` secti 2. Use Veeam Kasten K10 launch a backup that creates two restore points, a local and a remote. +3. You now have a backup we can use to validate a restore in the next section + !!! Note The Veeam backup process is explained below: 1. EDB elects a replica for the backup. @@ -22,19 +24,20 @@ When you have configured your Kubernetes environment per the `Configuring` secti 7. The replica leaves the backup mode. 8. The backup is then over and is consistent for a restore. -3. To get ready for a Kasten K10 to complete a restore, this example deleted the namespace `EDB`. + +## Restore Database + +1. To get ready for a Kasten K10 to complete a restore, we will remove the EDB namespace in this example. ```bash kubectl delete ns edb ``` -## Restore Database - -1. Go to your remote restore point. +2. In the Kasten interface go to your remote restore point. -2. On the remote restore point select `restore`. +3. On the remote restore point select `restore`. -3. After you have restored all of your data will be present. +4. After you have restored all of your data will be present. ![Kasten Data Restore Point](Images/KastenRestorePoint.png) From 2e267d26d3d16505e9fc492a5593154928423b6a Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Tue, 5 Sep 2023 12:19:21 -0400 Subject: [PATCH 037/255] Further Review Edits --- .../partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx | 4 ++-- .../VeeamKasten/Images/KastenSolutionSummaryImage.png | 4 ++-- .../VeeamKasten/Images/KastenSolutionSummaryImage2.png | 3 --- 3 files changed, 4 insertions(+), 7 deletions(-) delete mode 100644 advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage2.png diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index 093fe8bebc8..af0953cd93a 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -16,7 +16,7 @@ Implementing EDB Postgres for Kubernetes with Veeam Kasten requires the followin - Veeam Kasten K10 installed on your system !!! Note - The following steps will walk through a sample deployment from start to finish. You may already have some of these steps implemented in your environment, and if so you can skip that particular step. + For this integration, use the **example.yaml** files provided in each section for the appropriate Kasten configuration pieces, and change any environment variables per your specific needs. The **Add the Backup Decorator Annotations to the Cluster** section is the important section for the Kasten addon integration. ## Install the Operator @@ -167,7 +167,7 @@ exit ## Add the Backup Decorator Annotations to the Cluster -If you create the cluter from the previous section the **cluster-example.yaml** already includes the Kasten addon therefore you can skip this part. If you are working with your own cluster you will need to add the Kasten addon. +If you create the cluster from the previous section the **cluster-example.yaml** already includes the Kasten addon therefore you can skip this part. If you are working with your own cluster you will need to add the Kasten addon. 1. Add the following annotations to your cluster, in the above **cluster-example.yaml** there is an example of where to add the annotation. diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage.png b/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage.png index ad2ac426c49..a4f9cdbdaeb 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage.png +++ b/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a89f021a8af1b3054ec7906ed7b4fc67071ddba05858aad34d7301a60fab7d1b -size 434992 +oid sha256:35b6cf294303cd3c7c034684ea4d4be063df7b5f3db30037003ba51f3c5563c6 +size 120393 diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage2.png b/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage2.png deleted file mode 100644 index 024e1f828e8..00000000000 --- a/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage2.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b91718c7283f21b6004f1a0503d2bc2d39b0ac44643aa57338311a066382b395 -size 314038 From 2a8e35475d92ade1bd767ea96296607a07be38b1 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Tue, 5 Sep 2023 13:21:05 -0400 Subject: [PATCH 038/255] Spelling Edits --- .../partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx index af0953cd93a..4b092088874 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx @@ -31,7 +31,7 @@ Running this command will create the operator namespace where the controller wil ## Create an EDB Cluster, Client and Add Data -1. Initiate the below lines of code in your Kubernetes environment to create a specific namespace and apply your .yaml file. +1. Initiate the below lines of code in your Kubernetes environment to create a specific namespace and apply your `.yaml` file. ```bash kubctl create ns edb @@ -177,7 +177,7 @@ If you create the cluster from the previous section the **cluster-example.yaml** ## Install the EDB blueprint -1. Enter the follwing command in your environment: +1. Enter the following command in your environment: ```bash kubectl create -f edb-hooks.yaml From 8e03e8fe2105aea089e6ae1146929e9aeb29be97 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Tue, 5 Sep 2023 13:28:22 -0400 Subject: [PATCH 039/255] Name Change --- advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx | 2 +- ...lutionSummaryImage.png => KastenSolutionSummaryImagenew.png} | 0 2 files changed, 1 insertion(+), 1 deletion(-) rename advocacy_docs/partner_docs/VeeamKasten/Images/{KastenSolutionSummaryImage.png => KastenSolutionSummaryImagenew.png} (100%) diff --git a/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx b/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx index 079c65bd4e7..0d079d0a6c3 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx @@ -7,4 +7,4 @@ Veeam Kasten is a data management platform built for Kubernetes that can provide The EDB Postgres for Kubernetes [external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) allows for a third party tool such as Veeam Kasten to discover an API that is needed in order to create a successful backup. -![Kasten K10 Architecture](Images/KastenSolutionSummaryImage.png) +![Kasten K10 Architecture](Images/KastenSolutionSummaryImagenew.png) diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage.png b/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImagenew.png similarity index 100% rename from advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImage.png rename to advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImagenew.png From 7728ba4547771c796043bf5bec602c6223e0c2c9 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 27 Aug 2023 07:00:29 -0400 Subject: [PATCH 040/255] Replication Server 7.6 release https://enterprisedb.atlassian.net/browse/XDB-2094 --- .../03_xdb_cli_commands/52_reload_conf_file.mdx | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) 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 index d72d21eb650..44a6c95fc3c 100644 --- 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 @@ -85,11 +85,17 @@ The table shows whether a configuration property can be reloaded. This example reloads the configuration file. -```shell -$ java -jar edb-repcli.jar -reloadconf -repsvrfile ~/subsvr.prop +!!! 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. +```shell +java -jar edb-repcli.jar -reloadconf -repsvrfile subsvr.prop +__OUTPUT__ Reloading Subscription Server configuration file... Reloaded configuration options from ../etc/xdb_subserver.conf... +The conf option 'snapshotParallelTableLoaderLimit' set to '1' +The conf option 'skipCheckConst' set to 'false' +The conf option 'snapshotParallelLoadCount' set to '1' Configuration was reloaded successfully. ``` From 237c3d75e829ce1b70425ab6fe1f6888dd0bd0a0 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 27 Aug 2023 09:20:21 -0400 Subject: [PATCH 041/255] UPM-2072 Default locale for logs --- .../01_controlling_logging_level.mdx | 23 ++++++++++++++----- 1 file changed, 17 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx index a7662b54ed4..85ea46bfd4b 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx @@ -1,5 +1,6 @@ --- -title: "Controlling logging level, log file sizes, and rotation count" +title: "Controlling logging level, log file sizes, rotation count, and locale" +navTitle: "Controlling message logging" redirects: - /eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level --- @@ -13,7 +14,7 @@ The following options control various aspects of message logging in the publicat See [Publication and subscription server startup failures](../../02_resolving_problems/02_where_to_look_for_errors/#pub_and_sub_startup_failures) and [Snapshot replication failures](../../02_resolving_problems/02_where_to_look_for_errors/#snapshot_replication_failures) for more information. -`logging.level` +## `logging.level` Set the `logging.level` option to control the severity of messages written to the publication server log file and the subscription server log file. @@ -21,7 +22,7 @@ Set the `logging.level` option to control the severity of messages written to th The default value is `WARNING`. -`logging.file.size` +## `logging.file.size` Set the `logging.file.size` option to control the maximum file size (in megabytes) of the publication server log file and the subscription server log file. @@ -32,7 +33,7 @@ Set the `logging.file.size` option to control the maximum file size (in megabyte The default value is `50`, in megabytes. -`logging.file.count` +## `logging.file.count` Set the `logging.file.count` option to control the number of files in the log file rotation history of the publication server log file and the subscription server log file. @@ -57,7 +58,15 @@ When log file rotation is enabled and the current, active log file (`pubserver.l - Each remaining log file is renamed with the next greater integer suffix (`pubserver.log.m` is renamed to `pubserver.log.m+1`, with m varying from `0` to `n-2`). - A new, active log file is created (`pubserver.log.0`). -`mtk.logging.file.size` +## `logging.default.locale` + +Set the `logging.default.locale` option to use either the current system locale or English (en) for publication and subscription logs. + +`logging.default.locale={system | en}` + +The default value is `system`. + +## `mtk.logging.file.size` !!! Note This option applies only to the publication server. @@ -68,7 +77,7 @@ Set the `mtk.logging.file.size` option to control the maximum file size (in mega The default value is `50`, in megabytes. -`mtk.logging.file.count` +## `mtk.logging.file.count` !!! Note This option applies only to the publication server. @@ -94,3 +103,5 @@ When the current, active log file (`mtk.log`) reaches the size specified by `mtk - Each remaining log file with a suffix is renamed with the next greater integer suffix (`mtk.log.m` is renamed to `mtk.log.m+1`, with `m` varying from `1` to `n-1`). - Log file `mtk.log` is renamed to `mtk.log.1`. - A new, active log file is created (`mtk.log`). + + From 42f5d617d7248c4d5cee2df9ccf5533814c915b8 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 29 Aug 2023 15:04:16 -0400 Subject: [PATCH 042/255] XDB-1427 - BigAnimal support --- .../7/01_introduction/03_certified_supported_versions.mdx | 5 ++++- product_docs/docs/eprs/7/supported_platforms.mdx | 4 ++-- 2 files changed, 6 insertions(+), 3 deletions(-) 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 index a7f6073b5a3..6e3b38ed101 100644 --- 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 @@ -5,13 +5,16 @@ title: "Certified and supported product versions" You can use the following database product versions with Replication Server: - PostgreSQL versions 11, 12, 13, 14, and 15 -- Advanced Server versions 11, 12, 13, 14, and 15 +- EDB Postgres Advanced Server versions 11, 12, 13, 14, and 15 - Oracle 11g Release 2 version 11.2.0.2.0 is explicitly certified. Newer minor versions in the 11.2 line are supported as well. - Oracle 12c version 12.1.0.2.0 is explicitly certified. Newer minor versions in the 12.1 line are supported as well. - Oracle 18c version 18.1.0.2.0 is explicitly certified. Newer minor versions in the 18.1 line are supported as well. - Oracle 19c version 19.1.0.2.0 is explicitly certified. Newer minor versions in the 19.1 line are supported as well. - SQL Server 2014 version 12.0.5000.0 is explicitly certified. Newer minor versions in the 12.0 line are supported as well. +!!!Note + See BigAnimal's [database version policy](/biganimal/latest/overview/05_database_version_policy/) for the versions of PostgreSQL and EDB Postgres Advanced Server available using [BigAnimal](/biganimal/latest/) (EDB’s managed database cloud service). + As of Replication Server 7.1.0: - SQL Server 2016 version 13.00.5026 is explicitly certified. Newer minor versions in the 13.0 line are supported as well. - SQL Server 2017 version 14.0.1000.169 is explicitly certified. Newer minor versions in the 14.0 line are supported as well. diff --git a/product_docs/docs/eprs/7/supported_platforms.mdx b/product_docs/docs/eprs/7/supported_platforms.mdx index 58e1e24015a..c142c40aef6 100644 --- a/product_docs/docs/eprs/7/supported_platforms.mdx +++ b/product_docs/docs/eprs/7/supported_platforms.mdx @@ -1,5 +1,5 @@ --- -title: "Supported platforms" +title: "Supported Java platforms" redirects: - /eprs/latest/01_introduction/04_supported_jdk_versions/ - /eprs/latest/01_introduction/05_supported_jdk_versions/ @@ -22,4 +22,4 @@ Replication Server is certified to work with the following Java platforms: | Debian 10 and 11 | Red Hat OpenJDK 11 | | Ubuntu 18, 20, 22 | OpenJDK 11 | -See [Product Compatibility](https://www.enterprisedb.com/platform-compatibility#eprs) for more information. +See [Product Compatibility](https://www.enterprisedb.com/platform-compatibility#eprs) for more information on operating system support. From 76372f542a2fdcce4d4194954f87601bd58888ef Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 31 Aug 2023 09:17:04 -0400 Subject: [PATCH 043/255] Incorporated Matt's excellent suggestion --- .../eprs/7/01_introduction/03_certified_supported_versions.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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 index 6e3b38ed101..6c6cefbddc8 100644 --- 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,8 @@ 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 - See BigAnimal's [database version policy](/biganimal/latest/overview/05_database_version_policy/) for the versions of PostgreSQL and EDB Postgres Advanced Server available using [BigAnimal](/biganimal/latest/) (EDB’s managed database cloud service). + 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. + As of Replication Server 7.1.0: - SQL Server 2016 version 13.00.5026 is explicitly certified. Newer minor versions in the 13.0 line are supported as well. From 11ddce21fa9364a73b415ef0e98eec76f4fea270 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 1 Sep 2023 05:53:44 -0400 Subject: [PATCH 044/255] Added limitations to logging.default.locale --- .../01_controlling_logging_level.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx index 85ea46bfd4b..90931a7714a 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx @@ -66,6 +66,12 @@ 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. + +The RepCLI and RepConsole logs continue showing text in the default locale. +!!! + ## `mtk.logging.file.size` !!! Note From 3a2a1976fb5993ee3bea7ba7a90d21ef11281bc4 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 6 Sep 2023 08:39:14 -0400 Subject: [PATCH 045/255] fenced note --- .../7/08_xdb_cli/03_xdb_cli_commands/52_reload_conf_file.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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 index 44a6c95fc3c..a95c78c6c34 100644 --- 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 have been 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 @@ -99,3 +99,4 @@ The conf option 'snapshotParallelLoadCount' set to '1' Configuration was reloaded successfully. ``` +!!! From 9107ec2579e8d857f72e14cc0ce0c783106e99c5 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 5 Sep 2023 12:17:42 -0400 Subject: [PATCH 046/255] changes for version 14 --- .../01_object_type_specification_syntax.mdx | 17 +++++------------ .../02_object_type_body_syntax.mdx | 9 ++++----- 2 files changed, 9 insertions(+), 17 deletions(-) diff --git a/product_docs/docs/epas/14/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx b/product_docs/docs/epas/14/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx index daa8f37bf9e..36b0ac4d969 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx @@ -53,15 +53,14 @@ Where `subprogram_spec` is the following: Where `constructor` is the following: ```text -CONSTRUCTOR - [ ( [ SELF [ IN | IN OUT ] ] - [, [ IN | IN OUT | OUT ] +CONSTRUCTOR FUNCTION + [ ( [ [ IN | IN OUT | OUT ] [ DEFAULT ] ] [, [ IN | IN OUT | OUT ] [ DEFAULT ] ] ...) ] -RETURN self AS RESULT +RETURN ; ``` !!! Note @@ -103,9 +102,9 @@ Before defining a method, use `[ NOT ] INSTANTIABLE` to specify whether the obje `proc_name` is an identifier of a procedure. If you specify the `SELF` parameter, `name` is the object type name given in the `CREATE TYPE` command. If specified, `parm1, parm2, …` are the formal parameters of the procedure. `datatype1, datatype2, …` are the data types of `parm1, parm2, …` respectively. `IN`, `IN OUT`, and `OUT` are the possible parameter modes for each formal parameter. The default is `IN`. `value1, value2, …` are default values that you can specify for `IN` parameters. -Include the `CONSTRUCTOR` keyword and function definition to define a constructor function. +Include the `CONSTRUCTOR FUNCTION` keyword and function definition to define a constructor function. -`func_name` is an identifier of a function. If you specify the `SELF` parameter, `name` is the object type name given in the `CREATE TYPE` command. If specified, `parm1, parm2, …` are the formal parameters of the function. `datatype1, datatype2, …` are the data types of `parm1, parm2, …` respectively. `IN`, `IN OUT`, and `OUT` are the possible parameter modes for each formal parameter. The default is `IN`. `value1, value2, …` are default values that you can specify for `IN` parameters. `return_type` is the data type of the value the function returns. +`func_name` is an identifier of a function. If specified, `parm1, parm2, …` are the formal parameters of the function. `datatype1, datatype2, …` are the data types of `parm1, parm2, …` respectively. `IN`, `IN OUT`, and `OUT` are the possible parameter modes for each formal parameter. The default is `IN`. `value1, value2, …` are default values that you can specify for `IN` parameters. `return_type` is the data type of the value the function returns. Note the following about an object type specification: @@ -113,12 +112,6 @@ Note the following about an object type specification: - There can be zero, one, or more methods defined in the object type. -- For each member method, there is an implicit, built-in parameter named `SELF` whose data type is that of the object type being defined. - - `SELF` refers to the object instance that's currently invoking the method. `SELF` can be explicitly declared as an `IN` or `IN OUT` parameter in the parameter list (for example, as `MEMBER FUNCTION (SELF IN OUT object_type ...)`). - - If `SELF` is explicitly declared, `SELF` must be the first parameter in the parameter list. If `SELF` isn't explicitly declared, its parameter mode defaults to `IN OUT` for member procedures and `IN` for member functions. - - A static method can't be overridden. You can't specify `OVERRIDING` and `STATIC` together in `method_spec`. - A static method must be instantiable. You can't specify `NOT INSTANTIABLE` and `STATIC` together in `method_spec`. diff --git a/product_docs/docs/epas/14/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx b/product_docs/docs/epas/14/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx index 68d391fa46f..99c695c2c35 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx @@ -59,15 +59,14 @@ Where `method_spec` is `subprogram_spec`, and `subprogram_spec` is the following Where `constructor` is: ```text -CONSTRUCTOR - [ ( [ SELF [ IN | IN OUT ] ] - [, [ IN | IN OUT | OUT ] +CONSTRUCTOR FUNCTION + [ ( [ [ IN | IN OUT | OUT ] [ DEFAULT ] ] [, [ IN | IN OUT | OUT ] [ DEFAULT ] ] ...) ] -RETURN self AS RESULT +RETURN ; { IS | AS } [ ] BEGIN @@ -92,7 +91,7 @@ If `NOT INSTANTIABLE` was specified in `method_spec` of the `CREATE TYPE` comman `proc_name` is an identifier of a procedure specified in the `CREATE TYPE` command. The parameter declarations have the same meaning as described for the `CREATE TYPE` command. They must be specified in the `CREATE TYPE BODY` command in the same manner as in the `CREATE TYPE` command. -Include the `CONSTRUCTOR` keyword and function definition to define a constructor function. +Include the `CONSTRUCTOR FUNCTION` keyword and function definition to define a constructor function. `func_name` is an identifier of a function specified in the `CREATE TYPE` command. The parameter declarations have the same meaning as described for the `CREATE TYPE` command and must be specified in the `CREATE TYPE BODY` command in the same manner as in the `CREATE TYPE` command. `return_type` is the data type of the value the function returns and must match the `return_type` given in the `CREATE TYPE` command. From c7b9ced0a7c03cfbc89308a2758570550b0c8ca4 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Sep 2023 08:37:41 -0400 Subject: [PATCH 047/255] changes for versions 11 through 13 --- .../01_object_type_specification_syntax.mdx | 11 +++++------ .../02_object_type_body_syntax.mdx | 9 ++++----- .../01_object_type_specification_syntax.mdx | 11 +++++------ .../02_object_type_body_syntax.mdx | 9 ++++----- .../01_object_type_specification_syntax.mdx | 11 +++++------ .../02_object_type_body_syntax.mdx | 9 ++++----- 6 files changed, 27 insertions(+), 33 deletions(-) diff --git a/product_docs/docs/epas/11/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx b/product_docs/docs/epas/11/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx index 2c685251cf8..a205868915f 100644 --- a/product_docs/docs/epas/11/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx +++ b/product_docs/docs/epas/11/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx @@ -54,15 +54,14 @@ where `subprogram_spec` is the following: where `constructor` is the following: ```text -CONSTRUCTOR - [ ( [ SELF [ IN | IN OUT ] ] - [, [ IN | IN OUT | OUT ] +CONSTRUCTOR FUNCTION + [ ( [ [ IN | IN OUT | OUT ] [ DEFAULT ] ] [, [ IN | IN OUT | OUT ] [ DEFAULT ] ] ...) ] -RETURN self AS RESULT +RETURN ; ``` !!! Note @@ -104,9 +103,9 @@ Prior to the definition of a method, `[ NOT ] INSTANTIABLE` specifies whether or `proc_name` is an identifier of a procedure. If the `SELF` parameter is specified, `name` is the object type name given in the `CREATE TYPE` command. If specified, `parm1, parm2, …` are the formal parameters of the procedure. `datatype1, datatype2, …` are the data types of `parm1, parm2, …` respectively. `IN, IN OUT`, and `OUT` are the possible parameter modes for each formal parameter. If none are specified, the default is `IN`. `value1, value2, …` are default values that may be specified for `IN` parameters. -Include the `CONSTRUCTOR` keyword and function definition to define a constructor function. +Include the `CONSTRUCTOR FUNCTION` keyword and function definition to define a constructor function. -`func_name` is an identifier of a function. If the `SELF` parameter is specified, `name` is the object type name given in the `CREATE TYPE` command. If specified, `parm1, parm2, …` are the formal parameters of the function. `datatype1, datatype2, …` are the data types of `parm1, parm2, …` respectively. `IN, IN OUT`, and `OUT` are the possible parameter modes for each formal parameter. If none are specified, the default is `IN`. `value1, value2, …` are default values that may be specified for `IN` parameters. `return_type` is the data type of the value the function returns. +`func_name` is an identifier of a function. If specified, `parm1, parm2, …` are the formal parameters of the function. `datatype1, datatype2, …` are the data types of `parm1, parm2, …` respectively. `IN, IN OUT`, and `OUT` are the possible parameter modes for each formal parameter. If none are specified, the default is `IN`. `value1, value2, …` are default values that may be specified for `IN` parameters. `return_type` is the data type of the value the function returns. The following points should be noted about an object type specification: diff --git a/product_docs/docs/epas/11/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx b/product_docs/docs/epas/11/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx index fa41c82315a..b01b6e080e0 100644 --- a/product_docs/docs/epas/11/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx +++ b/product_docs/docs/epas/11/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx @@ -64,15 +64,14 @@ and `subprogram_spec` is the following: where `constructor` is: ```text -CONSTRUCTOR - [ ( [ SELF [ IN | IN OUT ] ] - [, [ IN | IN OUT | OUT ] +CONSTRUCTOR FUNCTION + [ ( [ [ IN | IN OUT | OUT ] [ DEFAULT ] ] [, [ IN | IN OUT | OUT ] [ DEFAULT ] ] ...) ] -RETURN self AS RESULT +RETURN ; { IS | AS } [ ] BEGIN @@ -95,7 +94,7 @@ If `NOT INSTANTIABLE` was specified in `method_spec` of the `CREATE TYPE` comman `proc_name` is an identifier of a procedure specified in the `CREATE TYPE` command. The parameter declarations have the same meaning as described for the `CREATE TYPE` command, and must be specified in the `CREATE TYPE BODY` command in the same manner as specified in the `CREATE TYPE` command. -Include the `CONSTRUCTOR` keyword and function definition to define a constructor function. +Include the `CONSTRUCTOR FUNCTION` keyword and function definition to define a constructor function. `func_name` is an identifier of a function specified in the `CREATE TYPE` command. The parameter declarations have the same meaning as described for the `CREATE TYPE` command, and must be specified in the `CREATE TYPE BODY` command in the same manner as specified in the `CREATE TYPE` command. `return_type` is the data type of the value the function returns and must match `return_type` given in the `CREATE TYPE` command. diff --git a/product_docs/docs/epas/12/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx b/product_docs/docs/epas/12/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx index 2c685251cf8..a205868915f 100644 --- a/product_docs/docs/epas/12/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx +++ b/product_docs/docs/epas/12/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx @@ -54,15 +54,14 @@ where `subprogram_spec` is the following: where `constructor` is the following: ```text -CONSTRUCTOR - [ ( [ SELF [ IN | IN OUT ] ] - [, [ IN | IN OUT | OUT ] +CONSTRUCTOR FUNCTION + [ ( [ [ IN | IN OUT | OUT ] [ DEFAULT ] ] [, [ IN | IN OUT | OUT ] [ DEFAULT ] ] ...) ] -RETURN self AS RESULT +RETURN ; ``` !!! Note @@ -104,9 +103,9 @@ Prior to the definition of a method, `[ NOT ] INSTANTIABLE` specifies whether or `proc_name` is an identifier of a procedure. If the `SELF` parameter is specified, `name` is the object type name given in the `CREATE TYPE` command. If specified, `parm1, parm2, …` are the formal parameters of the procedure. `datatype1, datatype2, …` are the data types of `parm1, parm2, …` respectively. `IN, IN OUT`, and `OUT` are the possible parameter modes for each formal parameter. If none are specified, the default is `IN`. `value1, value2, …` are default values that may be specified for `IN` parameters. -Include the `CONSTRUCTOR` keyword and function definition to define a constructor function. +Include the `CONSTRUCTOR FUNCTION` keyword and function definition to define a constructor function. -`func_name` is an identifier of a function. If the `SELF` parameter is specified, `name` is the object type name given in the `CREATE TYPE` command. If specified, `parm1, parm2, …` are the formal parameters of the function. `datatype1, datatype2, …` are the data types of `parm1, parm2, …` respectively. `IN, IN OUT`, and `OUT` are the possible parameter modes for each formal parameter. If none are specified, the default is `IN`. `value1, value2, …` are default values that may be specified for `IN` parameters. `return_type` is the data type of the value the function returns. +`func_name` is an identifier of a function. If specified, `parm1, parm2, …` are the formal parameters of the function. `datatype1, datatype2, …` are the data types of `parm1, parm2, …` respectively. `IN, IN OUT`, and `OUT` are the possible parameter modes for each formal parameter. If none are specified, the default is `IN`. `value1, value2, …` are default values that may be specified for `IN` parameters. `return_type` is the data type of the value the function returns. The following points should be noted about an object type specification: diff --git a/product_docs/docs/epas/12/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx b/product_docs/docs/epas/12/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx index fa41c82315a..b01b6e080e0 100644 --- a/product_docs/docs/epas/12/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx +++ b/product_docs/docs/epas/12/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx @@ -64,15 +64,14 @@ and `subprogram_spec` is the following: where `constructor` is: ```text -CONSTRUCTOR - [ ( [ SELF [ IN | IN OUT ] ] - [, [ IN | IN OUT | OUT ] +CONSTRUCTOR FUNCTION + [ ( [ [ IN | IN OUT | OUT ] [ DEFAULT ] ] [, [ IN | IN OUT | OUT ] [ DEFAULT ] ] ...) ] -RETURN self AS RESULT +RETURN ; { IS | AS } [ ] BEGIN @@ -95,7 +94,7 @@ If `NOT INSTANTIABLE` was specified in `method_spec` of the `CREATE TYPE` comman `proc_name` is an identifier of a procedure specified in the `CREATE TYPE` command. The parameter declarations have the same meaning as described for the `CREATE TYPE` command, and must be specified in the `CREATE TYPE BODY` command in the same manner as specified in the `CREATE TYPE` command. -Include the `CONSTRUCTOR` keyword and function definition to define a constructor function. +Include the `CONSTRUCTOR FUNCTION` keyword and function definition to define a constructor function. `func_name` is an identifier of a function specified in the `CREATE TYPE` command. The parameter declarations have the same meaning as described for the `CREATE TYPE` command, and must be specified in the `CREATE TYPE BODY` command in the same manner as specified in the `CREATE TYPE` command. `return_type` is the data type of the value the function returns and must match `return_type` given in the `CREATE TYPE` command. diff --git a/product_docs/docs/epas/13/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx b/product_docs/docs/epas/13/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx index 901781b4bfb..05e797abf97 100644 --- a/product_docs/docs/epas/13/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx +++ b/product_docs/docs/epas/13/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx @@ -57,15 +57,14 @@ where `subprogram_spec` is the following: where `constructor` is the following: ```text -CONSTRUCTOR - [ ( [ SELF [ IN | IN OUT ] ] - [, [ IN | IN OUT | OUT ] +CONSTRUCTOR FUNCTION + [ ( [ [ IN | IN OUT | OUT ] [ DEFAULT ] ] [, [ IN | IN OUT | OUT ] [ DEFAULT ] ] ...) ] -RETURN self AS RESULT +RETURN ; ``` !!! Note @@ -107,9 +106,9 @@ Prior to the definition of a method, `[ NOT ] INSTANTIABLE` specifies whether or `proc_name` is an identifier of a procedure. If the `SELF` parameter is specified, `name` is the object type name given in the `CREATE TYPE` command. If specified, `parm1, parm2, …` are the formal parameters of the procedure. `datatype1, datatype2, …` are the data types of `parm1, parm2, …` respectively. `IN, IN OUT`, and `OUT` are the possible parameter modes for each formal parameter. If none are specified, the default is `IN`. `value1, value2, …` are default values that may be specified for `IN` parameters. -Include the `CONSTRUCTOR` keyword and function definition to define a constructor function. +Include the `CONSTRUCTOR FUNCTION` keyword and function definition to define a constructor function. -`func_name` is an identifier of a function. If the `SELF` parameter is specified, `name` is the object type name given in the `CREATE TYPE` command. If specified, `parm1, parm2, …` are the formal parameters of the function. `datatype1, datatype2, …` are the data types of `parm1, parm2, …` respectively. `IN, IN OUT`, and `OUT` are the possible parameter modes for each formal parameter. If none are specified, the default is `IN`. `value1, value2, …` are default values that may be specified for `IN` parameters. `return_type` is the data type of the value the function returns. +`func_name` is an identifier of a function. If specified, `parm1, parm2, …` are the formal parameters of the function. `datatype1, datatype2, …` are the data types of `parm1, parm2, …` respectively. `IN, IN OUT`, and `OUT` are the possible parameter modes for each formal parameter. If none are specified, the default is `IN`. `value1, value2, …` are default values that may be specified for `IN` parameters. `return_type` is the data type of the value the function returns. The following points should be noted about an object type specification: diff --git a/product_docs/docs/epas/13/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx b/product_docs/docs/epas/13/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx index 9bfa45919a5..adb881f7c3c 100644 --- a/product_docs/docs/epas/13/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx +++ b/product_docs/docs/epas/13/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx @@ -67,15 +67,14 @@ and `subprogram_spec` is the following: where `constructor` is: ```text -CONSTRUCTOR - [ ( [ SELF [ IN | IN OUT ] ] - [, [ IN | IN OUT | OUT ] +CONSTRUCTOR FUNCTION + [ ( [ [ IN | IN OUT | OUT ] [ DEFAULT ] ] [, [ IN | IN OUT | OUT ] [ DEFAULT ] ] ...) ] -RETURN self AS RESULT +RETURN ; { IS | AS } [ ] BEGIN @@ -98,7 +97,7 @@ If `NOT INSTANTIABLE` was specified in `method_spec` of the `CREATE TYPE` comman `proc_name` is an identifier of a procedure specified in the `CREATE TYPE` command. The parameter declarations have the same meaning as described for the `CREATE TYPE` command, and must be specified in the `CREATE TYPE BODY` command in the same manner as specified in the `CREATE TYPE` command. -Include the `CONSTRUCTOR` keyword and function definition to define a constructor function. +Include the `CONSTRUCTOR FUNCTION` keyword and function definition to define a constructor function. `func_name` is an identifier of a function specified in the `CREATE TYPE` command. The parameter declarations have the same meaning as described for the `CREATE TYPE` command, and must be specified in the `CREATE TYPE BODY` command in the same manner as specified in the `CREATE TYPE` command. `return_type` is the data type of the value the function returns and must match `return_type` given in the `CREATE TYPE` command. From 68dd9074b9cc3d202732fc4c966baf3f90be5aa6 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Wed, 6 Sep 2023 10:46:19 -0400 Subject: [PATCH 048/255] Image Update --- advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx | 2 ++ .../partner_docs/VeeamKasten/Images/LaunchaBackup.png | 3 +++ 2 files changed, 5 insertions(+) create mode 100644 advocacy_docs/partner_docs/VeeamKasten/Images/LaunchaBackup.png diff --git a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx index 2275b542b5a..606dc049a3d 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx @@ -13,6 +13,8 @@ When you have configured your Kubernetes environment per the `Configuring` secti 3. You now have a backup we can use to validate a restore in the next section + ![Launch a Backup](Images/LaunchaBackup.png) + !!! Note The Veeam backup process is explained below: 1. EDB elects a replica for the backup. diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/LaunchaBackup.png b/advocacy_docs/partner_docs/VeeamKasten/Images/LaunchaBackup.png new file mode 100644 index 00000000000..69497874fe6 --- /dev/null +++ b/advocacy_docs/partner_docs/VeeamKasten/Images/LaunchaBackup.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44440bacf12dcf57d13842bb473c32b1711f39c8ab620d13da3ba155d4f395c4 +size 77474 From 5e75ce46f83d01aeab99caf6ccb3df0391f9590a Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Wed, 6 Sep 2023 12:55:18 -0400 Subject: [PATCH 049/255] Update epas15_4_0_rel_notes.mdx --- .../15/epas_rel_notes/epas15_4_0_rel_notes.mdx | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx b/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx index 097a670e896..d12ed1b10a7 100644 --- a/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx +++ b/product_docs/docs/epas/15/epas_rel_notes/epas15_4_0_rel_notes.mdx @@ -9,7 +9,7 @@ Released: 21 Aug 2023 Updated: 30 Aug 2023 !!! Important Upgrading -Once you upgrade to this version of EDB Postgres Advanced Server, you need to run edb_sqlpatch on all your databases to complete the upgrade. This application checks that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool. +After you upgrade to this version of EDB Postgres Advanced Server, you need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application checks that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool. !!! !!! Note After applying patches @@ -23,14 +23,14 @@ EDB Postgres Advanced Server 15.4.0 includes the following enhancements and bug | Type | Description | Addresses                | | | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | --- | | Upstream merge | Merged with community PostgreSQL 15.4. See the [PostgreSQL 15 Release Notes](https://www.postgresql.org/docs/15/release-15-4.html) for more information. | | | -| Security fix | EDB Postgres Advanced Server SECURITY DEFINER functions and procedures might be hijacked by way of search_path. | [CVE-2023-XXXXX-1](/security/advisories/cve2023xxxxx1/) | 11+ | -| Security fix | EDB Postgres Advanced Server dbms_aq helper function might run arbitrary SQL as a superuser. | [CVE-2023-XXXXX-2](/security/advisories/cve2023xxxxx2/) | 11+ | -| Security fix | EDB Postgres Advanced Server permissions bypass by way of accesshistory() | [CVE-2023-XXXXX-3](/security/advisories/cve2023xxxxx3/) | 11+ | -| Security fix | EDB Postgres Advanced Server UTL_FILE permission bypass | [CVE-2023-XXXXX-4](/security/advisories/cve2023xxxxx4/) | 11+ | -| Security fix | EDB Postgres Advanced Server permission bypass for materialized views | [CVE-2023-XXXXX-5](/security/advisories/cve2023xxxxx5/) | 11+ | -| Security fix | EDB Postgres Advanced Server authenticated users can fetch any URL | [CVE-2023-XXXXX-6](/security/advisories/cve2023xxxxx6/) | 11+ | -| Security fix | EDB Postgres Advanced Server permission bypass for large objects | [CVE-2023-XXXXX-7](/security/advisories/cve2023xxxxx7/) | 11+ | -| Security fix | EDB Postgres Advanced Server DBMS_PROFILER data might be removed without permission | [CVE-2023-XXXXX-8](/security/advisories/cve2023xxxxx8/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path. | [CVE-2023-XXXXX-1](/security/advisories/cve2023xxxxx1/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser. | [CVE-2023-XXXXX-2](/security/advisories/cve2023xxxxx2/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory() | [CVE-2023-XXXXX-3](/security/advisories/cve2023xxxxx3/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass | [CVE-2023-XXXXX-4](/security/advisories/cve2023xxxxx4/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) permission bypass for materialized views | [CVE-2023-XXXXX-5](/security/advisories/cve2023xxxxx5/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL | [CVE-2023-XXXXX-6](/security/advisories/cve2023xxxxx6/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) permission bypass for large objects | [CVE-2023-XXXXX-7](/security/advisories/cve2023xxxxx7/) | 11+ | +| Security fix | EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission | [CVE-2023-XXXXX-8](/security/advisories/cve2023xxxxx8/) | 11+ | | Bug fix | Allowed subtypes in INDEX BY clause of the packaged collection. | #1371 | 11+ | | Bug fix | Fixed %type resolution when pointing to a packaged type field. | #1243 | 11+ | | Bug fix | Profile: Fixed upgrade when `REUSE` constraints were `ENABLED`/`DISABLED`. | #92739 | 11+ | From 4a51ab2fc3337e2d27eba037f180a02985360e48 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 6 Sep 2023 13:56:37 -0400 Subject: [PATCH 050/255] release notes --- .../7/eprs_rel_notes/eprs_rel_notes_7.6.0.mdx | 22 +++++++++++++++++++ .../docs/eprs/7/eprs_rel_notes/index.mdx | 4 +++- 2 files changed, 25 insertions(+), 1 deletion(-) create mode 100644 product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.6.0.mdx 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 new file mode 100644 index 00000000000..b9db5af9199 --- /dev/null +++ b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.6.0.mdx @@ -0,0 +1,22 @@ +--- +title: Replication Server 7.6.0 release notes +navTitle: "Version 7.6.0" +--- + +Released: 07 Sep 2023 + +New features, enhancements, bug fixes, and other changes in Replication Server 7.6.0 include the following: + +| 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 | 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 | 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. | diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx index 8ba40e8def8..f24b2ccc714 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx @@ -1,8 +1,9 @@ --- -title: "Release Notes" +title: "Release notes" redirects: - ../01_whats_new/ navigation: + - eprs_rel_notes_7.6.0 - eprs_rel_notes_7.5.1 - eprs_rel_notes_7.5.0 - eprs_rel_notes_7.4.0 @@ -13,6 +14,7 @@ The Replication Server documentation describes the latest version including mino | Version | Release Date | | -------------------------------- | ------------ | +| [7.6.0](eprs_rel_notes_7.6.0) | 07 Sep 2023 | | [7.5.1](eprs_rel_notes_7.5.1) | 26 May 2023 | | [7.5.0](eprs_rel_notes_7.5.0) | 14 Feb 2023 | | [7.4.0](eprs_rel_notes_7.4.0) | 29 Nov 2022 | From eede09c6fff5825438605b20e90e9d47fdd5624a Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Wed, 6 Sep 2023 16:50:48 -0400 Subject: [PATCH 051/255] Updated epas 11-14 upgrade release note note --- .../docs/epas/11/epas_rel_notes/epas11_21_32_rel_notes.mdx | 2 +- .../docs/epas/12/epas_rel_notes/epas12_16_20_rel_notes.mdx | 2 +- .../docs/epas/13/epas_rel_notes/epas13_12_17_rel_notes.mdx | 2 +- .../docs/epas/14/epas_rel_notes/epas14_9_0_rel_notes.mdx | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/epas/11/epas_rel_notes/epas11_21_32_rel_notes.mdx b/product_docs/docs/epas/11/epas_rel_notes/epas11_21_32_rel_notes.mdx index acf4dc472c1..21928c066c9 100644 --- a/product_docs/docs/epas/11/epas_rel_notes/epas11_21_32_rel_notes.mdx +++ b/product_docs/docs/epas/11/epas_rel_notes/epas11_21_32_rel_notes.mdx @@ -8,7 +8,7 @@ Released: 21 Aug 2023 Updated: 30 Aug 2023 !!! Important Upgrading -Once you have upgraded to this version of EDB Postgres Advanced Server, you will need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application will check that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool. +After you upgrade to this version of EDB Postgres Advanced Server, you need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application checks that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool. !!! !!! Note After applying patches diff --git a/product_docs/docs/epas/12/epas_rel_notes/epas12_16_20_rel_notes.mdx b/product_docs/docs/epas/12/epas_rel_notes/epas12_16_20_rel_notes.mdx index bd79f163261..5896ba11272 100644 --- a/product_docs/docs/epas/12/epas_rel_notes/epas12_16_20_rel_notes.mdx +++ b/product_docs/docs/epas/12/epas_rel_notes/epas12_16_20_rel_notes.mdx @@ -8,7 +8,7 @@ Released: 21 Aug 2023 Updated: 30 Aug 2023 !!! Important Upgrading -Once you have upgraded to this version of EDB Postgres Advanced Server, you will need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application will check that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool. +After you upgrade to this version of EDB Postgres Advanced Server, you need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application checks that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool. !!! !!! Note After applying patches diff --git a/product_docs/docs/epas/13/epas_rel_notes/epas13_12_17_rel_notes.mdx b/product_docs/docs/epas/13/epas_rel_notes/epas13_12_17_rel_notes.mdx index b9526e79643..6203a28d7e1 100644 --- a/product_docs/docs/epas/13/epas_rel_notes/epas13_12_17_rel_notes.mdx +++ b/product_docs/docs/epas/13/epas_rel_notes/epas13_12_17_rel_notes.mdx @@ -8,7 +8,7 @@ Released: 21 Aug 2023 Updated: 30 Aug 2023 !!! Important Upgrading -Once you have upgraded to this version of EDB Postgres Advanced Server, you will need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application will check that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool. +After you upgrade to this version of EDB Postgres Advanced Server, you need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application checks that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool. !!! !!! Note After applying patches diff --git a/product_docs/docs/epas/14/epas_rel_notes/epas14_9_0_rel_notes.mdx b/product_docs/docs/epas/14/epas_rel_notes/epas14_9_0_rel_notes.mdx index 66390b3ff79..647f5fcc450 100644 --- a/product_docs/docs/epas/14/epas_rel_notes/epas14_9_0_rel_notes.mdx +++ b/product_docs/docs/epas/14/epas_rel_notes/epas14_9_0_rel_notes.mdx @@ -8,7 +8,7 @@ Released: 21 Aug 2023 Updated: 30 Aug 2023 !!! Important Upgrading -Once you have upgraded to this version of EDB Postgres Advanced Server, you will need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application will check that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool. +After you upgrade to this version of EDB Postgres Advanced Server, you need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application checks that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool. !!! !!! Note After applying patches From 8b0a2256034d4f3477cb2c1ef27997125d78c4ec Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 6 Sep 2023 17:25:34 +0100 Subject: [PATCH 052/255] Updated with modified pglogical importer Signed-off-by: Dj Walker-Morgan --- .../pglogical2/configuration-options.mdx | 4 +- .../pglogical2/conflicts.mdx | 4 +- .../pglogical2/index.mdx | 9 +- .../pglogical2/installation.mdx | 8 +- .../limitations-and-restrictions.mdx | 4 +- .../pglogical2/release-notes.mdx | 26 ++- .../pglogical2/requirements.mdx | 4 +- .../pglogical2/synchronous-replication.mdx | 4 +- .../pglogical2/usage.mdx | 4 +- scripts/source/pglogical2-s6.js | 164 ++++++++++++++++++ 10 files changed, 208 insertions(+), 23 deletions(-) create mode 100644 scripts/source/pglogical2-s6.js diff --git a/advocacy_docs/supported-open-source/pglogical2/configuration-options.mdx b/advocacy_docs/supported-open-source/pglogical2/configuration-options.mdx index 50f01f1150d..4a7f60687c2 100644 --- a/advocacy_docs/supported-open-source/pglogical2/configuration-options.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/configuration-options.mdx @@ -2,10 +2,10 @@ title: Configuration options product: pglogical 2 generatedBy: >- - /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from + /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from originalFilePath originalFilePath: >- - https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L687-#L767 + https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L691-#L771 --- diff --git a/advocacy_docs/supported-open-source/pglogical2/conflicts.mdx b/advocacy_docs/supported-open-source/pglogical2/conflicts.mdx index ef7ae3b31da..6abd3f08b00 100644 --- a/advocacy_docs/supported-open-source/pglogical2/conflicts.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/conflicts.mdx @@ -2,10 +2,10 @@ title: Conflicts product: pglogical 2 generatedBy: >- - /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from + /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from originalFilePath originalFilePath: >- - https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L673-#L685 + https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L677-#L689 --- diff --git a/advocacy_docs/supported-open-source/pglogical2/index.mdx b/advocacy_docs/supported-open-source/pglogical2/index.mdx index c2b060d0c62..b37ca1389cb 100644 --- a/advocacy_docs/supported-open-source/pglogical2/index.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/index.mdx @@ -2,7 +2,7 @@ title: pglogical 2 product: pglogical 2 generatedBy: >- - /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from + /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from originalFilePath navigation: - index @@ -25,12 +25,7 @@ originalFilePath: >- The pglogical 2 extension provides logical streaming replication for PostgreSQL, using a publish/subscribe model. It is based on technology developed as part -of [EDB Postgres Distributed](/pgd/latest/). - -!!! Note "pglogical 2 is open source" - EDB maintains pglogical as a service to the PostgreSQL community. - For license and copyright information, or for access to the source, - visit the project page at https://github.com/2ndQuadrant/pglogical +of the BDR project (). We use the following terms to describe data streams between nodes, deliberately reused from the earlier Slony technology: diff --git a/advocacy_docs/supported-open-source/pglogical2/installation.mdx b/advocacy_docs/supported-open-source/pglogical2/installation.mdx index 8285d463737..dcfb43ccd3d 100644 --- a/advocacy_docs/supported-open-source/pglogical2/installation.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/installation.mdx @@ -2,10 +2,10 @@ title: Installation product: pglogical 2 generatedBy: >- - /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from + /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from originalFilePath originalFilePath: >- - https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L55-#L160 + https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L55-#L164 --- @@ -36,6 +36,7 @@ If you don’t have PostgreSQL already: - PostgreSQL 12: `yum install postgresql12-server postgresql12-contrib` - PostgreSQL 13: `yum install postgresql13-server postgresql13-contrib` - PostgreSQL 14: `yum install postgresql14-server postgresql14-contrib` + - PostgreSQL 15: `yum install postgresql15-server postgresql15-contrib` Then install the “2ndQuadrant’s General Public” repository for your PostgreSQL version, by running the following instructions as root on the destination Linux server: @@ -48,6 +49,7 @@ version, by running the following instructions as root on the destination Linux - PostgreSQL 12: `curl https://techsupport.enterprisedb.com/api/repository/dl/default/release/12/rpm | bash` - PostgreSQL 13: `curl https://techsupport.enterprisedb.com/api/repository/dl/default/release/13/rpm | bash` - PostgreSQL 14: `curl https://techsupport.enterprisedb.com/api/repository/dl/default/release/14/rpm | bash` +- PostgreSQL 15: `curl https://techsupport.enterprisedb.com/api/repository/dl/default/release/15/rpm | bash` #### Installation @@ -61,6 +63,7 @@ Once the repository is installed, you can proceed to pglogical for your PostgreS - PostgreSQL 12: `yum install postgresql12-pglogical` - PostgreSQL 13: `yum install postgresql13-pglogical` - PostgreSQL 14: `yum install postgresql14-pglogical` +- PostgreSQL 15: `yum install postgresql15-pglogical` You may be prompted to accept the repository GPG key for package signing: @@ -95,6 +98,7 @@ Once pre-requisites are complete, installing pglogical is simply a matter of exe - PostgreSQL 12: `sudo apt-get install postgresql-12-pglogical` - PostgreSQL 13: `sudo apt-get install postgresql-13-pglogical` - PostgreSQL 14: `sudo apt-get install postgresql-14-pglogical` +- PostgreSQL 15: `sudo apt-get install postgresql-15-pglogical` ## From source code diff --git a/advocacy_docs/supported-open-source/pglogical2/limitations-and-restrictions.mdx b/advocacy_docs/supported-open-source/pglogical2/limitations-and-restrictions.mdx index 425f6c98b6a..2db59e08db8 100644 --- a/advocacy_docs/supported-open-source/pglogical2/limitations-and-restrictions.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/limitations-and-restrictions.mdx @@ -2,10 +2,10 @@ title: Limitations and restrictions product: pglogical 2 generatedBy: >- - /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from + /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from originalFilePath originalFilePath: >- - https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L769-#L938 + https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L773-#L942 --- diff --git a/advocacy_docs/supported-open-source/pglogical2/release-notes.mdx b/advocacy_docs/supported-open-source/pglogical2/release-notes.mdx index c9693084d36..2ac4794dedf 100644 --- a/advocacy_docs/supported-open-source/pglogical2/release-notes.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/release-notes.mdx @@ -2,13 +2,35 @@ title: Release Notes product: pglogical 2 generatedBy: >- - /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from + /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from originalFilePath originalFilePath: >- - https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L953-#L993 + https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L957-#L1019 --- +## pglogical 2.4.3 + +Version 2.4.3 is a maintenance release of pglogical 2. + +### Changes + +- Apply data filtering on the correct tuple during initial synchronization. + +- Restore the correct memory context while decoding a change. + +- Drop database never completes in PostgreSQL 15. + +- Don't replicate TRUNCATE as global message. + +## pglogical 2.4.2 + +Version 2.4.2 is a maintenance release of pglogical 2. + +### Changes + +- Add support for PostgreSQL 15. + ## pglogical 2.4.1 Version 2.4.1 is a maintenance release of pglogical 2. diff --git a/advocacy_docs/supported-open-source/pglogical2/requirements.mdx b/advocacy_docs/supported-open-source/pglogical2/requirements.mdx index 7803bce0b52..f2f71c4f616 100644 --- a/advocacy_docs/supported-open-source/pglogical2/requirements.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/requirements.mdx @@ -2,7 +2,7 @@ title: Requirements product: pglogical 2 generatedBy: >- - /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from + /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from originalFilePath originalFilePath: >- https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L36-#L53 @@ -24,4 +24,4 @@ be the same or weaker (more permissive) on the subscriber than the provider. Tables must have the same `PRIMARY KEY`s. It is not recommended to add additional `UNIQUE` constraints other than the `PRIMARY KEY` (see below). -Some additional requirements are covered in [Limitations and Restrictions](limitations-and-restrictions.mdx). \ No newline at end of file +Some additional requirements are covered in [Limitations and Restrictions](limitations-and-restrictions). diff --git a/advocacy_docs/supported-open-source/pglogical2/synchronous-replication.mdx b/advocacy_docs/supported-open-source/pglogical2/synchronous-replication.mdx index e92e268f23b..ebce1bf5132 100644 --- a/advocacy_docs/supported-open-source/pglogical2/synchronous-replication.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/synchronous-replication.mdx @@ -2,10 +2,10 @@ title: Synchronous Replication product: pglogical 2 generatedBy: >- - /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from + /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from originalFilePath originalFilePath: >- - https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L663-#L671 + https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L667-#L675 --- diff --git a/advocacy_docs/supported-open-source/pglogical2/usage.mdx b/advocacy_docs/supported-open-source/pglogical2/usage.mdx index 473181e9c5b..df0b80fca18 100644 --- a/advocacy_docs/supported-open-source/pglogical2/usage.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/usage.mdx @@ -2,10 +2,10 @@ title: Usage product: pglogical 2 generatedBy: >- - /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from + /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from originalFilePath originalFilePath: >- - https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L162-#L661 + https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L166-#L665 --- diff --git a/scripts/source/pglogical2-s6.js b/scripts/source/pglogical2-s6.js new file mode 100644 index 00000000000..4b94e0d1821 --- /dev/null +++ b/scripts/source/pglogical2-s6.js @@ -0,0 +1,164 @@ +// run: node scripts/source/pglogical2.js +// purpose: +// Import and convert the pglogical2 docs from https://raw.githubusercontent.com/2ndQuadrant/pglogical/REL2_x_STABLE/docs/README.md, rendering them in /advocacy_docs/supported-open-source/pglogical2/ +// +import path from "path"; +import fs from "fs/promises"; +import https from "https"; +import pkg from 'to-vfile'; +const {write, read} = pkg; +import remarkParse from "remark-parse"; +import mdx from "remark-mdx"; +import unified from "unified"; +import remarkFrontmatter from "remark-frontmatter"; +import remarkStringify from "remark-stringify"; +import admonitions from "remark-admonitions"; +import yaml from "js-yaml"; +import visit from "unist-util-visit"; +import visitAncestors from "unist-util-visit-parents"; +import mdast2string from "mdast-util-to-string"; +import slugger from "github-slugger"; + +const outputFiles = []; +const source = new URL( + "https://raw.githubusercontent.com/2ndQuadrant/pglogical/REL2_x_STABLE/docs/README.md", +); +const originalSource = + "https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1"; +const destination = path.resolve( + process.argv[1], + "../../../advocacy_docs/supported-open-source/pglogical2/", +); + +(async () => { + const readme = await getReadme(); + + const processor = unified() + .use(remarkParse) + .use(remarkStringify, { emphasis: "*", bullet: "-", fences: true }) + .use(admonitions, { tag: "!!!", icons: "none", infima: true }) + .use(remarkFrontmatter) + .use(mdx) + .use(pglogicalTransformer); + + let ast = await processor.parse({ contents: readme }); + ast = await processor.run(ast); + + for (let file of ast.children) { + file.metadata.originalFilePath = + originalSource + + `#L${file.data.position.start.line}-#L${file.data.position.end.line}`; + file.data.children[0].value = yaml.dump(file.metadata); + file.contents = await processor.stringify(file.data); + try { + await fs.mkdir(path.dirname(file.path), { recursive: true }); + } catch {} + await write(file); + console.log("wrote: " + file.path); + } +})(); + +async function getReadme() { + const promise = new Promise((resolve, reject) => { + let data = ""; + https + .get(source, (response) => { + response + .on("data", (readme) => { + data += readme; + }) + .on("end", () => { + resolve(data); + }); + }) + .on("error", (e) => { + reject(e); + }); + }); + + return await promise; +} + +function pglogicalTransformer() { + return (tree, file) => { + let files = []; + + // split file by heading - keep track of link targets + let mapLinkTargetToFile = {}; + for (let node of tree.children) { + if (node.type === "heading") { + const title = cleanTitle(node); + const filename = + node.depth < 3 + ? makeFilename(node) + : path.basename(files[files.length - 1].path); + mapLinkTargetToFile["#" + slugger.slug(title)] = path.basename( + filename, + ".mdx", + ); + + if (node.depth < 3) { + files.push({ + path: path.resolve(destination, filename), + metadata: { + title: title, + product: "pglogical 2", + generatedBy: `${process.argv[1]} - re-run to regenerate from originalFilePath`, + }, + data: { + type: "root", + children: [{ type: "yaml" }], + position: { start: node.position.start, end: node.position.end }, + }, + }); + continue; + } + node.depth -= 1; + } + + files[files.length - 1].data.children.push(node); + files[files.length - 1].data.position.end = node.position.end; + } + + // rewrite links + for (let file of files) { + visit(file.data, "link", (link) => { + const dest = mapLinkTargetToFile[link.url]; + const isTopLevel = "#" + dest === link.url; + if (dest && dest !== path.basename(file.path, ".mdx")) + link.url = dest + (isTopLevel ? "" : link.url); + }); + } + + // move release notes to top + files.splice( + 1, + 0, + ...files.splice( + files.indexOf((f) => f.title === "Release Notes"), + 1, + ), + ); + + files = files.filter((f) => f.metadata.title !== "Credits and License"); + + files[0].metadata.navigation = files.map((f) => + path.basename(f.path, ".mdx"), + ); + files[0].metadata.indexCards = "simple"; + files[0].metadata.directoryDefaults = { + iconName: "EdbReplicate", + editTarget: "originalFilePath", + }; + tree.children = files; + }; +} + +function cleanTitle(heading) { + return mdast2string(heading).replace(/^Appendix \w: /, ""); +} + +function makeFilename(heading) { + if (heading.depth === 1) return "index.mdx"; + return slugger.slug(cleanTitle(heading)) + ".mdx"; +} From bb283059a222352ba8ba2f5b234a1443d940420a Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Wed, 6 Sep 2023 16:47:19 +0000 Subject: [PATCH 053/255] Keep same name for script, use relative path for generated files, restore blurb in index.mdx --- .../pglogical2/configuration-options.mdx | 4 +- .../pglogical2/conflicts.mdx | 4 +- .../pglogical2/index.mdx | 11 +- .../pglogical2/installation.mdx | 4 +- .../limitations-and-restrictions.mdx | 4 +- .../pglogical2/release-notes.mdx | 4 +- .../pglogical2/requirements.mdx | 4 +- .../pglogical2/synchronous-replication.mdx | 4 +- .../pglogical2/usage.mdx | 4 +- scripts/source/pglogical2-s6.js | 164 ------------------ scripts/source/pglogical2.js | 43 ++--- 11 files changed, 38 insertions(+), 212 deletions(-) delete mode 100644 scripts/source/pglogical2-s6.js diff --git a/advocacy_docs/supported-open-source/pglogical2/configuration-options.mdx b/advocacy_docs/supported-open-source/pglogical2/configuration-options.mdx index 4a7f60687c2..5e388125e55 100644 --- a/advocacy_docs/supported-open-source/pglogical2/configuration-options.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/configuration-options.mdx @@ -1,9 +1,7 @@ --- title: Configuration options product: pglogical 2 -generatedBy: >- - /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from - originalFilePath +generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath originalFilePath: >- https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L691-#L771 diff --git a/advocacy_docs/supported-open-source/pglogical2/conflicts.mdx b/advocacy_docs/supported-open-source/pglogical2/conflicts.mdx index 6abd3f08b00..f012be24440 100644 --- a/advocacy_docs/supported-open-source/pglogical2/conflicts.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/conflicts.mdx @@ -1,9 +1,7 @@ --- title: Conflicts product: pglogical 2 -generatedBy: >- - /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from - originalFilePath +generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath originalFilePath: >- https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L677-#L689 diff --git a/advocacy_docs/supported-open-source/pglogical2/index.mdx b/advocacy_docs/supported-open-source/pglogical2/index.mdx index b37ca1389cb..041c03c0cac 100644 --- a/advocacy_docs/supported-open-source/pglogical2/index.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/index.mdx @@ -1,9 +1,7 @@ --- title: pglogical 2 product: pglogical 2 -generatedBy: >- - /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from - originalFilePath +generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath navigation: - index - release-notes @@ -25,7 +23,12 @@ originalFilePath: >- The pglogical 2 extension provides logical streaming replication for PostgreSQL, using a publish/subscribe model. It is based on technology developed as part -of the BDR project (). +of [EDB Postgres Distributed](/pgd/latest/). + +!!! Note "pglogical 2 is open source" + EDB maintains pglogical as a service to the PostgreSQL community. + For license and copyright information, or for access to the source, + visit the project page at https://github.com/2ndQuadrant/pglogical We use the following terms to describe data streams between nodes, deliberately reused from the earlier Slony technology: diff --git a/advocacy_docs/supported-open-source/pglogical2/installation.mdx b/advocacy_docs/supported-open-source/pglogical2/installation.mdx index dcfb43ccd3d..36ab4a7dfc3 100644 --- a/advocacy_docs/supported-open-source/pglogical2/installation.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/installation.mdx @@ -1,9 +1,7 @@ --- title: Installation product: pglogical 2 -generatedBy: >- - /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from - originalFilePath +generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath originalFilePath: >- https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L55-#L164 diff --git a/advocacy_docs/supported-open-source/pglogical2/limitations-and-restrictions.mdx b/advocacy_docs/supported-open-source/pglogical2/limitations-and-restrictions.mdx index 2db59e08db8..9c2cb3e8a4a 100644 --- a/advocacy_docs/supported-open-source/pglogical2/limitations-and-restrictions.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/limitations-and-restrictions.mdx @@ -1,9 +1,7 @@ --- title: Limitations and restrictions product: pglogical 2 -generatedBy: >- - /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from - originalFilePath +generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath originalFilePath: >- https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L773-#L942 diff --git a/advocacy_docs/supported-open-source/pglogical2/release-notes.mdx b/advocacy_docs/supported-open-source/pglogical2/release-notes.mdx index 2ac4794dedf..e092f6379f7 100644 --- a/advocacy_docs/supported-open-source/pglogical2/release-notes.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/release-notes.mdx @@ -1,9 +1,7 @@ --- title: Release Notes product: pglogical 2 -generatedBy: >- - /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from - originalFilePath +generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath originalFilePath: >- https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L957-#L1019 diff --git a/advocacy_docs/supported-open-source/pglogical2/requirements.mdx b/advocacy_docs/supported-open-source/pglogical2/requirements.mdx index f2f71c4f616..96748d21726 100644 --- a/advocacy_docs/supported-open-source/pglogical2/requirements.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/requirements.mdx @@ -1,9 +1,7 @@ --- title: Requirements product: pglogical 2 -generatedBy: >- - /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from - originalFilePath +generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath originalFilePath: >- https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L36-#L53 diff --git a/advocacy_docs/supported-open-source/pglogical2/synchronous-replication.mdx b/advocacy_docs/supported-open-source/pglogical2/synchronous-replication.mdx index ebce1bf5132..61f096a3109 100644 --- a/advocacy_docs/supported-open-source/pglogical2/synchronous-replication.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/synchronous-replication.mdx @@ -1,9 +1,7 @@ --- title: Synchronous Replication product: pglogical 2 -generatedBy: >- - /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from - originalFilePath +generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath originalFilePath: >- https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L667-#L675 diff --git a/advocacy_docs/supported-open-source/pglogical2/usage.mdx b/advocacy_docs/supported-open-source/pglogical2/usage.mdx index df0b80fca18..dce68454c54 100644 --- a/advocacy_docs/supported-open-source/pglogical2/usage.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/usage.mdx @@ -1,9 +1,7 @@ --- title: Usage product: pglogical 2 -generatedBy: >- - /Users/dj/docs/scripts/source/pglogical2-s6.js - re-run to regenerate from - originalFilePath +generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath originalFilePath: >- https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L166-#L665 diff --git a/scripts/source/pglogical2-s6.js b/scripts/source/pglogical2-s6.js deleted file mode 100644 index 4b94e0d1821..00000000000 --- a/scripts/source/pglogical2-s6.js +++ /dev/null @@ -1,164 +0,0 @@ -// run: node scripts/source/pglogical2.js -// purpose: -// Import and convert the pglogical2 docs from https://raw.githubusercontent.com/2ndQuadrant/pglogical/REL2_x_STABLE/docs/README.md, rendering them in /advocacy_docs/supported-open-source/pglogical2/ -// -import path from "path"; -import fs from "fs/promises"; -import https from "https"; -import pkg from 'to-vfile'; -const {write, read} = pkg; -import remarkParse from "remark-parse"; -import mdx from "remark-mdx"; -import unified from "unified"; -import remarkFrontmatter from "remark-frontmatter"; -import remarkStringify from "remark-stringify"; -import admonitions from "remark-admonitions"; -import yaml from "js-yaml"; -import visit from "unist-util-visit"; -import visitAncestors from "unist-util-visit-parents"; -import mdast2string from "mdast-util-to-string"; -import slugger from "github-slugger"; - -const outputFiles = []; -const source = new URL( - "https://raw.githubusercontent.com/2ndQuadrant/pglogical/REL2_x_STABLE/docs/README.md", -); -const originalSource = - "https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1"; -const destination = path.resolve( - process.argv[1], - "../../../advocacy_docs/supported-open-source/pglogical2/", -); - -(async () => { - const readme = await getReadme(); - - const processor = unified() - .use(remarkParse) - .use(remarkStringify, { emphasis: "*", bullet: "-", fences: true }) - .use(admonitions, { tag: "!!!", icons: "none", infima: true }) - .use(remarkFrontmatter) - .use(mdx) - .use(pglogicalTransformer); - - let ast = await processor.parse({ contents: readme }); - ast = await processor.run(ast); - - for (let file of ast.children) { - file.metadata.originalFilePath = - originalSource + - `#L${file.data.position.start.line}-#L${file.data.position.end.line}`; - file.data.children[0].value = yaml.dump(file.metadata); - file.contents = await processor.stringify(file.data); - try { - await fs.mkdir(path.dirname(file.path), { recursive: true }); - } catch {} - await write(file); - console.log("wrote: " + file.path); - } -})(); - -async function getReadme() { - const promise = new Promise((resolve, reject) => { - let data = ""; - https - .get(source, (response) => { - response - .on("data", (readme) => { - data += readme; - }) - .on("end", () => { - resolve(data); - }); - }) - .on("error", (e) => { - reject(e); - }); - }); - - return await promise; -} - -function pglogicalTransformer() { - return (tree, file) => { - let files = []; - - // split file by heading - keep track of link targets - let mapLinkTargetToFile = {}; - for (let node of tree.children) { - if (node.type === "heading") { - const title = cleanTitle(node); - const filename = - node.depth < 3 - ? makeFilename(node) - : path.basename(files[files.length - 1].path); - mapLinkTargetToFile["#" + slugger.slug(title)] = path.basename( - filename, - ".mdx", - ); - - if (node.depth < 3) { - files.push({ - path: path.resolve(destination, filename), - metadata: { - title: title, - product: "pglogical 2", - generatedBy: `${process.argv[1]} - re-run to regenerate from originalFilePath`, - }, - data: { - type: "root", - children: [{ type: "yaml" }], - position: { start: node.position.start, end: node.position.end }, - }, - }); - continue; - } - node.depth -= 1; - } - - files[files.length - 1].data.children.push(node); - files[files.length - 1].data.position.end = node.position.end; - } - - // rewrite links - for (let file of files) { - visit(file.data, "link", (link) => { - const dest = mapLinkTargetToFile[link.url]; - const isTopLevel = "#" + dest === link.url; - if (dest && dest !== path.basename(file.path, ".mdx")) - link.url = dest + (isTopLevel ? "" : link.url); - }); - } - - // move release notes to top - files.splice( - 1, - 0, - ...files.splice( - files.indexOf((f) => f.title === "Release Notes"), - 1, - ), - ); - - files = files.filter((f) => f.metadata.title !== "Credits and License"); - - files[0].metadata.navigation = files.map((f) => - path.basename(f.path, ".mdx"), - ); - files[0].metadata.indexCards = "simple"; - files[0].metadata.directoryDefaults = { - iconName: "EdbReplicate", - editTarget: "originalFilePath", - }; - tree.children = files; - }; -} - -function cleanTitle(heading) { - return mdast2string(heading).replace(/^Appendix \w: /, ""); -} - -function makeFilename(heading) { - if (heading.depth === 1) return "index.mdx"; - return slugger.slug(cleanTitle(heading)) + ".mdx"; -} diff --git a/scripts/source/pglogical2.js b/scripts/source/pglogical2.js index f3596fdc620..6d522df7d1d 100644 --- a/scripts/source/pglogical2.js +++ b/scripts/source/pglogical2.js @@ -2,23 +2,22 @@ // purpose: // Import and convert the pglogical2 docs from https://raw.githubusercontent.com/2ndQuadrant/pglogical/REL2_x_STABLE/docs/README.md, rendering them in /advocacy_docs/supported-open-source/pglogical2/ // -const path = require("path"); -const fs = require("fs/promises"); -const https = require("https"); -const { read, write } = require("to-vfile"); -const remarkParse = require("remark-parse"); -const mdx = require("remark-mdx"); -const unified = require("unified"); -const remarkFrontmatter = require("remark-frontmatter"); -const remarkStringify = require("remark-stringify"); -const admonitions = require("remark-admonitions"); -const yaml = require("js-yaml"); -const visit = require("unist-util-visit"); -const visitAncestors = require("unist-util-visit-parents"); -const mdast2string = require("mdast-util-to-string"); -const { exec } = require("child_process"); -const isAbsoluteUrl = require("is-absolute-url"); -const slugger = require("github-slugger"); +import path from "path"; +import fs from "fs/promises"; +import https from "https"; +import pkg from 'to-vfile'; +const {write, read} = pkg; +import remarkParse from "remark-parse"; +import mdx from "remark-mdx"; +import unified from "unified"; +import remarkFrontmatter from "remark-frontmatter"; +import remarkStringify from "remark-stringify"; +import admonitions from "remark-admonitions"; +import yaml from "js-yaml"; +import visit from "unist-util-visit"; +import visitAncestors from "unist-util-visit-parents"; +import mdast2string from "mdast-util-to-string"; +import slugger from "github-slugger"; const outputFiles = []; const source = new URL( @@ -26,9 +25,13 @@ const source = new URL( ); const originalSource = "https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1"; -const destination = path.resolve( +const docsRoot = path.resolve( process.argv[1], - "../../../advocacy_docs/supported-open-source/pglogical2/", + "../../../", +); +const destination = path.resolve( + docsRoot, + "advocacy_docs/supported-open-source/pglogical2/", ); (async () => { @@ -104,7 +107,7 @@ function pglogicalTransformer() { metadata: { title: title, product: "pglogical 2", - generatedBy: `${process.argv[1]} - re-run to regenerate from originalFilePath`, + generatedBy: `${path.relative(docsRoot, process.argv[1])} - re-run to regenerate from originalFilePath`, }, data: { type: "root", From 855e91d75a97c0ba9a3d10a34ddb5a4ffcbbb826 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 6 Sep 2023 17:06:14 +0100 Subject: [PATCH 054/255] Test a Codeowners addition Signed-off-by: Dj Walker-Morgan --- CODEOWNERS | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 CODEOWNERS diff --git a/CODEOWNERS b/CODEOWNERS new file mode 100644 index 00000000000..907737c5090 --- /dev/null +++ b/CODEOWNERS @@ -0,0 +1,5 @@ +# First pass basic codeowners file + +product_docs/docs/pgd/ @djw-m +product_docs/docs/epas/ @nidhibhammar +product_docs/docs/biganimal/ @drothery-edb From 965800178a9147a596c25ee461be16fa2ae61c27 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Fri, 28 Jul 2023 10:44:32 +0100 Subject: [PATCH 055/255] Splitting app usage and testing Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/appusage.mdx | 314 +------------------ product_docs/docs/pgd/5/index.mdx | 1 + product_docs/docs/pgd/5/testingandtuning.mdx | 145 +++++++++ 3 files changed, 149 insertions(+), 311 deletions(-) create mode 100644 product_docs/docs/pgd/5/testingandtuning.mdx diff --git a/product_docs/docs/pgd/5/appusage.mdx b/product_docs/docs/pgd/5/appusage.mdx index 3cf4f83520d..4003806f1d8 100644 --- a/product_docs/docs/pgd/5/appusage.mdx +++ b/product_docs/docs/pgd/5/appusage.mdx @@ -314,8 +314,9 @@ Being asynchronous by default, peer nodes might lag behind, making it possible for a client connected to multiple PGD nodes or switching between them to read stale data. -A [queue wait function](/pgd/latest/reference/functions/#bdrwait_for_apply_queue) is -provided for clients or proxies to prevent such stale reads. +A [queue wait +function](/pgd/latest/reference/functions/#bdrwait_for_apply_queue) is provided +for clients or proxies to prevent such stale reads. The synchronous replication features of Postgres are available to PGD as well. In addition, PGD provides multiple variants for more synchronous @@ -323,312 +324,3 @@ replication. See [Durability and performance options](durability) for an overview and comparison of all variants available and its different modes. -## Application testing - -You can test PGD applications using the following programs, -in addition to other techniques: - -- [Trusted Postgres Architect](#trusted-postgres-architect) -- [pgbench with CAMO/Failover options](#pgbench-with-camofailover-options) -- [isolationtester with multi-node access](#isolationtester-with-multi-node-access) - -### Trusted Postgres Architect - -[Trusted Postgres Architect](/tpa/latest) is the system used by EDB to -deploy reference architectures, including those based on EDB Postgres Distributed. - -Trusted Postgres Architect includes test suites for each reference architecture. -It also simplifies creating and managing a local collection of tests to run -against a TPA cluster, using a syntax like the following: - -``` -tpaexec test mycluster mytest -``` - -We strongly recommend that developers write their own multi-node suite -of Trusted Postgres Architect tests that verify the main expected properties -of the application. - -### pgbench with CAMO/failover options - -In EDB Postgres Extended, the pgbench was extended to allow users to -run failover tests while using CAMO or regular PGD deployments. The following options were added: - -``` --m, --mode=regular|camo|failover -mode in which pgbench should run (default: regular) - ---retry -retry transactions on failover -``` - -In addition to these options, you must specify the connection information about the -peer node for failover in [DSN -form](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING). - -- Use `-m camo` or `-m failover` to specify the mode for pgbench. - You can use The `-m failover` specification to test failover in - regular PGD deployments. - -- Use `--retry` to specify whether to retry transactions when - failover happens with `-m failover` mode. This option is enabled by default - for `-m camo` mode. - -Here's an example in a CAMO environment: - -```sh - pgbench -m camo -p $node1_port -h $node1_host bdrdemo \ - "host=$node2_host user=postgres port=$node2_port dbname=bdrdemo" -``` - -This command runs in CAMO mode. It connects to node1 and runs the tests. If the -connection to node1 is lost, then pgbench connects to -node2. It queries node2 to get the status of in-flight transactions. -Aborted and in-flight transactions are retried in camo mode. - -In failover mode, if you specify `--retry`, then in-flight transactions are retried. In -this scenario there's no way to find the status of in-flight transactions. - -### isolationtester with multi-node access - -`isolationtester` was extended to allow users to run tests on multiple -sessions and on multiple nodes. This tool is used for internal PGD testing, -although it's also available for use with user application testing. - -``` -$ isolationtester \ - --outputdir=./iso_output \ - --create-role=logical \ - --dbname=postgres \ - --server 'd1=dbname=node1' \ - --server 'd2=dbname=node2' \ - --server 'd3=dbname=node3' -``` - -Isolation tests are a set of tests for examining concurrent behaviors in -PostgreSQL. These tests require running multiple interacting transactions, -which requires managing multiple concurrent connections and therefore -can't be tested using the normal `pg_regress` program. The name "isolation" -comes from the fact that the original motivation was to test the -serializable isolation level. Tests for other sorts of concurrent -behaviors were added as well. - -It's built using PGXS as an external module. -On installation, it creates the `isolationtester` binary file, which is run by -`pg_isolation_regress` to perform concurrent regression tests and observe -results. - -`pg_isolation_regress` is a tool similar to `pg_regress`, but instead of using -psql to execute a test, it uses isolationtester. It accepts all the same -command-line arguments as `pg_regress`. It was modified to accept multiple -hosts as parameters. It then passes the host conninfo along with server names -to the `isolationtester` binary. Isolation tester compares these server names with the -names specified in each session in the spec files and runs given tests on -respective servers. - -To define tests with overlapping transactions, use test specification -files with a custom syntax. To add -a new test, place a spec file in the `specs/` subdirectory, add the expected -output in the `expected/` subdirectory, and add the test's name to the makefile. - -Isolationtester is a program that uses libpq to open multiple connections -and executes a test specified by a spec file. A libpq connection string -specifies the server and database to connect to. Defaults derived from -environment variables are used otherwise. - -Specification consists of five parts, tested in this order: - -`server ""` - - This part defines the name of the servers for the sessions to run on. - There can be zero or more server `""` specifications. - The conninfo corresponding to the names is provided by the command to - run `isolationtester`. This is described in `quickstart_isolationtest.md`. - This part is optional. - -`setup { }` - - The given SQL block is executed once, in one session only, before running - the test. Create any test tables or other required objects here. This - part is optional. Multiple setup blocks are allowed if needed. Each is - run separately, in the given order. The reason for allowing multiple - setup blocks is that each block is run as a single PQexec submission, - and some statements such as VACUUM can't be combined with others in such - a block. - -`teardown { }` - - The teardown SQL block is executed once after the test is finished. Use - this part to clean up in preparation for the next permutation, such as dropping - any test tables created by setup. This part is optional. - -`session ""` - - There are normally several "session" parts in a spec file. Each - session is executed in its own connection. A session part consists - of three parts: setup, teardown, and one or more "steps." The per-session - setup and teardown parts have the same syntax as the per-test setup and - teardown, but they are executed in each session. The - setup part typically contains a BEGIN command to begin a transaction. - - A session part also consists of `connect_to` specification, - which points to a server name specified in the beginning that - indicates the server on which this session runs. - - `connect_to ""` - - Each step has the syntax: - - `step "" { }` - - Where `` is a name identifying this step, and SQL is a SQL statement - (or statements, separated by semicolons) that's executed in the step. - Step names must be unique across the whole spec file. - -`permutation ""` - - A permutation line specifies a list of steps that are run in that order. - Any number of permutation lines can appear. If no permutation lines are - given, the test program automatically generates all possible orderings - of the steps from each session (running the steps of any one session in - order). The list of steps in a manually specified - "permutation" line doesn't actually have to be a permutation of the - available steps. It can, for instance, repeat some steps more than once - or leave others out. - -Lines beginning with # are comments. - -For each permutation of the session steps (whether these are manually -specified in the spec file or automatically generated), the isolation -tester runs: - -1. The main setup part -1. Per-session setup parts -1. The selected session steps -1. Per-session teardown -1. The main teardown script - -Each selected step is sent to the connection associated -with its session. - -To run isolation tests in a PGD environment that ran all prerequisite make -commands: - -1. Run `make isolationcheck-install` to install the isolationtester submodule. - -2. You can run isolation regression tests using either - of the following commands from the bdr-private repo: - - `make isolationcheck-installcheck` - `make isolationcheck-makecheck` - -To run `isolationcheck-installcheck`, you need to have two or more postgresql -servers running. Pass the conninfo of each server to `pg_isolation_regress` -in the PGD makefile. - Ex: `pg_isolation_regress --server 'd1=host=myhost dbname=mydb port=5434' - --server 'd2=host=myhost1 dbname=mydb port=5432'` - -Next, add a `.spec` file containing tests in the `specs/isolation` directory -of the `bdr-private/` repo. Add a `.out` file in the `expected/isolation` directory of -the `bdr-private/` repo. - -Then run: - - `make isolationcheck-installcheck` - -`Isolationcheck-makecheck` currently supports running isolation tests on a -single instance by setting up PGD between multiple databases. - -You need to pass appropriate database names and the conninfo of bdr instances -to `pg_isolation_regress` in the PGD makefile as follows: - `pg_isolation_regress --dbname=db1,db2 --server 'd1=dbname=db1' - --server 'd2=dbname=db2'` - -Then run: - - `make isolationcheck-makecheck` - -Each step can contain commands that block until further action is taken. -Most likely, some other session runs a step that unblocks it or causes a -deadlock. A test that uses this ability must manually specify valid -permutations, that is, those that don't expect a blocked session to execute a -command. If a test doesn't follow that rule, `isolationtester` cancels it -after 300 seconds. If the cancel doesn't work, `isolationtester` exits -uncleanly after 375 seconds of wait time. Avoid testing invalid -permutations because they can make the isolation tests take -a very long time to run, and they serve no useful testing purpose. - -`isolationtester` recognizes that a command has blocked by checking whether it's shown as waiting in the `pg_locks` view. Therefore, only -blocks on heavyweight locks are detected. - -## Performance testing and tuning - -PGD allows you to issue write transactions onto multiple master nodes. -Bringing those writes back together onto each node has a cost in -performance. - -First, replaying changes from another node has a CPU cost, an I/O cost, -and it generates WAL records. The resource use is usually less -than in the original transaction since CPU overheads are lower as a result -of not needing to reexecute SQL. In the case of UPDATE and DELETE -transactions, there might be I/O costs on replay if data isn't cached. - -Second, replaying changes holds table-level and row-level locks that can -produce contention against local workloads. The conflict-free replicated data types (CRDT) and column-level conflict detection (CLCD) features -ensure you get the correct answers even for concurrent updates, but they -don't remove the normal locking overheads. If you get locking contention, -try to avoid conflicting updates, or keep transactions as short as -possible. A heavily updated row in a larger transaction causes -a bottleneck on performance for that transaction. Complex applications -require some thought to maintain scalability. - -If you think you're having performance problems, -develop performance tests using the benchmarking tools. pgbench -allows you to write custom test scripts specific to your use case -so you can understand the overheads of your SQL and measure the impact -of concurrent execution. - -If PGD is running slow, then we suggest the following: - -1. Write a custom test script for pgbench, as close as you can make it - to the production system's problem case. -2. Run the script on one node to give you a baseline figure. -3. Run the script on as many nodes as occurs in production, using the - same number of sessions in total as you did on one node. This technique - shows you the effect of moving to multiple nodes. -4. Increase the number of sessions for these two tests so you can - plot the effect of increased contention on your application. -5. Make sure your tests are long enough to account for replication delays. -6. Ensure that replication delay isn't growing during your tests. - -Use all of the normal Postgres tuning features to improve the speed -of critical parts of your application. - -## Use of table access methods (TAMs) in PGD - -PGD 5.0 supports two table access methods released with EDB Postgres 15.0. -These two table access methods have been certified and allowed in PGD 5.0: - - * Auto cluster - * Ref data - -Any other TAM is restricted until certified by EDB. -If you are planning to use any of the table access method on a table, -you need to configure that TAM on each participating node in the -PGD cluster. -To configure auto cluster or ref data TAM, follow these steps on each node: -1. Update `postgresql.conf` to specify TAMs `autocluster` or `refdata` for the - `shared_preload_libraries` parameter. -1. Restart the server and execute `CREATE EXTENSION autocluster;` or - `CREATE EXTENSION refdata;`. - -After you create the extension, you can use TAM to create a table using -`CREATE TABLE test USING autocluster;` or `CREATE TABLE test USING refdata;`. -This replicates to all the PGD nodes. -For more information on these table access methods, see [`CREATE TABLE`](/epas/latest/epas_compat_sql/36_create_table/). - - - - - - diff --git a/product_docs/docs/pgd/5/index.mdx b/product_docs/docs/pgd/5/index.mdx index 1285499d76e..ff42aeb253c 100644 --- a/product_docs/docs/pgd/5/index.mdx +++ b/product_docs/docs/pgd/5/index.mdx @@ -36,6 +36,7 @@ navigation: - monitoring - cli - transaction-streaming + - testingandtuning - striggers - scaling - twophase diff --git a/product_docs/docs/pgd/5/testingandtuning.mdx b/product_docs/docs/pgd/5/testingandtuning.mdx new file mode 100644 index 00000000000..1609106536a --- /dev/null +++ b/product_docs/docs/pgd/5/testingandtuning.mdx @@ -0,0 +1,145 @@ +--- +title: Testing and Tuning PGD clusters +navTitle: Testing and Tuning +--- + +## Application testing + +You can test PGD applications using the following programs, +in addition to other techniques: + +- [Trusted Postgres Architect](#trusted-postgres-architect) +- [pgd_bench with CAMO/Failover options](#pgd_bench-with-camofailover-options) + + +### Trusted Postgres Architect + +[Trusted Postgres Architect](/tpa/latest) is the system used by EDB to +deploy reference architectures, including those based on EDB Postgres Distributed. + +Trusted Postgres Architect includes test suites for each reference architecture. +It also simplifies creating and managing a local collection of tests to run +against a TPA cluster, using a syntax like the following: + +``` +tpaexec test mycluster mytest +``` + +We strongly recommend that developers write their own multi-node suite +of Trusted Postgres Architect tests that verify the main expected properties +of the application. + +### pgd_bench with CAMO/failover options + +The Postgres benchmarking application [`pgbench`](https://www.postgresql.org/docs/current/pgbench.html) has been extended in PGD 5.0 in the form of a new applications: `pgd_bench`. This version allows users to run failover tests while using CAMO or regular PGD deployments. + +The following options were added: + +``` +-m, --mode=regular|camo|failover +mode in which pgbench should run (default: regular) +``` + +- Use `-m camo` or `-m failover` to specify the mode for pgd_bench. + You can use The `-m failover` specification to test failover in + regular PGD deployments. + +``` +--retry +retry transactions on failover +``` + +- Use `--retry` to specify whether to retry transactions when + failover happens with `-m failover` mode. This option is enabled by default + for `-m camo` mode. + +In addition to these options, you must specify the connection information about +the peer node for failover in [DSN +form](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING). + + +Here's an example in a CAMO environment: + +```sh + pgd_bench -m camo -p $node1_port -h $node1_host bdrdemo \ + "host=$node2_host user=postgres port=$node2_port dbname=bdrdemo" +``` + +This command runs in CAMO mode. It connects to node1 and runs the tests. If the +connection to node1 is lost, then pgd_bench connects to node2. It queries node2 +to get the status of in-flight transactions. Aborted and in-flight transactions +are retried in CAMO mode. + +In failover mode, if you specify `--retry`, then in-flight transactions are +retried. In this scenario there's no way to find the status of in-flight +transactions. + +## Performance testing and tuning + +PGD allows you to issue write transactions onto multiple master nodes. Bringing +those writes back together onto each node has a cost in performance. + +First, replaying changes from another node has a CPU cost, an I/O cost, +and it generates WAL records. The resource use is usually less +than in the original transaction since CPU overheads are lower as a result +of not needing to reexecute SQL. In the case of UPDATE and DELETE +transactions, there might be I/O costs on replay if data isn't cached. + +Second, replaying changes holds table-level and row-level locks that can produce +contention against local workloads. The conflict-free replicated data types +(CRDT) and column-level conflict detection (CLCD) features ensure you get the +correct answers even for concurrent updates, but they don't remove the normal +locking overheads. If you get locking contention, try to avoid conflicting +updates, or keep transactions as short as possible. A heavily updated row in a +larger transaction causes a bottleneck on performance for that transaction. +Complex applications require some thought to maintain scalability. + +If you think you're having performance problems, develop performance tests using +the benchmarking tools. pgd_bench allows you to write custom test scripts specific +to your use case so you can understand the overheads of your SQL and measure the +impact of concurrent execution. + +If PGD is running slow, then we suggest the following: + +1. Write a custom test script for pgd_bench, as close as you can make it + to the production system's problem case. +2. Run the script on one node to give you a baseline figure. +3. Run the script on as many nodes as occurs in production, using the + same number of sessions in total as you did on one node. This technique + shows you the effect of moving to multiple nodes. +4. Increase the number of sessions for these two tests so you can + plot the effect of increased contention on your application. +5. Make sure your tests are long enough to account for replication delays. +6. Ensure that replication delay isn't growing during your tests. + +Use all of the normal Postgres tuning features to improve the speed +of critical parts of your application. + +## Use of table access methods (TAMs) in PGD + +PGD 5.0 supports two table access methods released with EDB Postgres 15.0. +These two table access methods have been certified and allowed in PGD 5.0: + + * Auto cluster + * Ref data + +Any other TAM is restricted until certified by EDB. +If you are planning to use any of the table access method on a table, +you need to configure that TAM on each participating node in the +PGD cluster. +To configure auto cluster or ref data TAM, follow these steps on each node: +1. Update `postgresql.conf` to specify TAMs `autocluster` or `refdata` for the + `shared_preload_libraries` parameter. +1. Restart the server and execute `CREATE EXTENSION autocluster;` or + `CREATE EXTENSION refdata;`. + +After you create the extension, you can use TAM to create a table using +`CREATE TABLE test USING autocluster;` or `CREATE TABLE test USING refdata;`. +This replicates to all the PGD nodes. +For more information on these table access methods, see [`CREATE TABLE`](/epas/latest/epas_compat_sql/36_create_table/). + + + + + + From 9022548612aca85c35d63eb164b73daf4d1fd7cd Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 30 Aug 2023 12:15:51 +0100 Subject: [PATCH 056/255] Command reference and general reworking Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/appusage.mdx | 23 ++++ product_docs/docs/pgd/5/reference/index.json | 1 + product_docs/docs/pgd/5/reference/index.mdx | 5 + .../docs/pgd/5/reference/index.mdx.src | 1 + .../docs/pgd/5/reference/testingandtuning.mdx | 119 ++++++++++++++++++ product_docs/docs/pgd/5/testingandtuning.mdx | 70 ++++++----- 6 files changed, 188 insertions(+), 31 deletions(-) create mode 100644 product_docs/docs/pgd/5/reference/testingandtuning.mdx diff --git a/product_docs/docs/pgd/5/appusage.mdx b/product_docs/docs/pgd/5/appusage.mdx index 4003806f1d8..7c54778a8cb 100644 --- a/product_docs/docs/pgd/5/appusage.mdx +++ b/product_docs/docs/pgd/5/appusage.mdx @@ -324,3 +324,26 @@ replication. See [Durability and performance options](durability) for an overview and comparison of all variants available and its different modes. +## Use of table access methods (TAMs) in PGD + +PGD 5.0 supports two table access methods released with EDB Postgres 15.0. +These two table access methods have been certified and allowed in PGD 5.0: + + * Auto cluster + * Ref data + +Any other TAM is restricted until certified by EDB. +If you are planning to use any of the table access method on a table, +you need to configure that TAM on each participating node in the +PGD cluster. +To configure auto cluster or ref data TAM, follow these steps on each node: +1. Update `postgresql.conf` to specify TAMs `autocluster` or `refdata` for the + `shared_preload_libraries` parameter. +1. Restart the server and execute `CREATE EXTENSION autocluster;` or + `CREATE EXTENSION refdata;`. + +After you create the extension, you can use TAM to create a table using +`CREATE TABLE test USING autocluster;` or `CREATE TABLE test USING refdata;`. +This replicates to all the PGD nodes. +For more information on these table access methods, see [`CREATE TABLE`](/epas/latest/epas_compat_sql/36_create_table/). + diff --git a/product_docs/docs/pgd/5/reference/index.json b/product_docs/docs/pgd/5/reference/index.json index 8e5c541ecc2..b846fc85cdc 100644 --- a/product_docs/docs/pgd/5/reference/index.json +++ b/product_docs/docs/pgd/5/reference/index.json @@ -185,6 +185,7 @@ "bdrreplication_set_remove_table": "/pgd/latest/reference/repsets-membership#bdrreplication_set_remove_table", "bdrreplication_set_add_ddl_filter": "/pgd/latest/reference/repsets-ddl-filtering#bdrreplication_set_add_ddl_filter", "bdrreplication_set_remove_ddl_filter": "/pgd/latest/reference/repsets-ddl-filtering#bdrreplication_set_remove_ddl_filter", + "pgd_bench": "/pgd/latest/reference/testingandtuning#pgd_bench", "bdralter_sequence_set_kind": "/pgd/latest/reference/sequences#bdralter_sequence_set_kind", "bdrextract_timestamp_from_snowflakeid": "/pgd/latest/reference/sequences#bdrextract_timestamp_from_snowflakeid", "bdrextract_nodeid_from_snowflakeid": "/pgd/latest/reference/sequences#bdrextract_nodeid_from_snowflakeid", diff --git a/product_docs/docs/pgd/5/reference/index.mdx b/product_docs/docs/pgd/5/reference/index.mdx index 504e73f87c9..8504dba6028 100644 --- a/product_docs/docs/pgd/5/reference/index.mdx +++ b/product_docs/docs/pgd/5/reference/index.mdx @@ -14,6 +14,7 @@ navigation: - repsets-management - repsets-membership - repsets-ddl-filtering +- testingandtuning - sequences - autopartition - streamtriggers @@ -263,6 +264,10 @@ The reference section is a definitive listing of all functions, views and comman * [`bdr.replication_set_remove_ddl_filter`](repsets-ddl-filtering#bdrreplication_set_remove_ddl_filter) +## [Testing and tuning commands](testingandtuning) + * [`pgd_bench`](testingandtuning#pgd_bench) + + ## [Global sequence management interfaces](sequences) ### [Sequence functions](sequences#sequence-functions) * [`bdr.alter_sequence_set_kind`](sequences#bdralter_sequence_set_kind) diff --git a/product_docs/docs/pgd/5/reference/index.mdx.src b/product_docs/docs/pgd/5/reference/index.mdx.src index 4443174c515..b95a72d417c 100644 --- a/product_docs/docs/pgd/5/reference/index.mdx.src +++ b/product_docs/docs/pgd/5/reference/index.mdx.src @@ -14,6 +14,7 @@ navigation: - repsets-management - repsets-membership - repsets-ddl-filtering +- testingandtuning - sequences - autopartition - streamtriggers diff --git a/product_docs/docs/pgd/5/reference/testingandtuning.mdx b/product_docs/docs/pgd/5/reference/testingandtuning.mdx new file mode 100644 index 00000000000..c903371afce --- /dev/null +++ b/product_docs/docs/pgd/5/reference/testingandtuning.mdx @@ -0,0 +1,119 @@ +--- +title: Testing and tuning commands +navTitle: Testing and tuning +indexdepth: 2 +--- + +EDB Postgres Distributed has tools which help with testing and tuning of your PGD clusters. For background, read the [Testing and Tuning](../testingandtuning) section. + + +## `pgd_bench` + +### Synopsis + +A benchmarking tool for PGD enhanced PostgreSQL. + +```shell +pgd_bench [OPTION]... [DBNAME] [DBNAME2] +``` + +`DBNAME` may be a conninfo string of the format: + `"host=10.1.1.2 user=postgres dbname=master"` + +Consult the [Testing and Tuning - Pgd_bench](../testingandtuning#pgd_bench)] section for examples +of `pgd_bench` options and usage. + +### Options + +`pgd_bench` specific options include: + +#### Setting mode + +`-m` or `--mode` + +Which can be set to `regular`, `camo`, or `failover`. It defaults to `regular`. + +* regular — regular description +* camo — +* failover — + +When using `-m=failover`, an additional option `--retry` is available. This will +instruct `pgd_bench` to retry transactions when there is a failover. + +#### Setting GUC variables + + `-o` or `--set-option` + +This option is followed by `NAME=VALUE` entries, which will be applied using the +Postgresql [`SET`](https://www.postgresql.org/docs/current/sql-set.html) command on each server, and only those servers, that `pgd_bench` connects to. + +The other options are identical to the Community PostgreSQL `pgbench`. For more +details, consult the [official documentation on +`pgbench`](https://www.postgresql.org/docs/current/pgbench.html). + +We list all the options (`pgd_bench` and `pgbench`) below for completeness. + +#### Initialization options: +- `-i, --initialize` — invokes initialization mode +- `-I, --init-steps=[dtgGvpf]+` (default `"dtgvp"`) — run selected initialization steps + - `d` — drop any existing `pgbench` tables + - `t` — create the tables used by the standard `pgbench` scenario + - `g` — generate data client-side and load it into the standard tables, replacing any data already present + - `G` — generate data server-side and load it into the standard tables, replacing any data already present + - `v` — invoke `VACUUM` on the standard tables + - `p` — create primary key indexes on the standard tables + - `f` — create foreign key constraints between the standard tables +- `-F, --fillfactor=NUM` — set fill factor +- `-n, --no-vacuum` — do not run `VACUUM` during initialization +- `-q, --quiet` — quiet logging (one message each 5 seconds) +- `-s, --scale=NUM` — scaling factor +- `--foreign-keys` — create foreign key constraints between tables +- `--index-tablespace=TABLESPACE` — create indexes in the specified tablespace +- `--partition-method=(range|hash)` — partition `pgbench_accounts` with this method (default: range) +- `--partitions=NUM` — partition `pgbench_accounts` into `NUM` parts (default: 0) +- `--tablespace=TABLESPACE` — create tables in the specified tablespace +- `--unlogged-tables` — create tables as unlogged tables (Note: unlogged tables are not replicated) + +#### Options to select what to run: +- `-b, --builtin=NAME[@W]` — add builtin script NAME weighted at W (default: 1). Use `-b list` to list available scripts. +- `-f, --file=FILENAME[@W]` — add script `FILENAME` weighted at W (default: 1) +- `-N, --skip-some-updates` — updates of pgbench_tellers and pgbench_branches. Same as `-b simple-update` +- `-S, --select-only` — perform SELECT-only transactions. Same as `-b select-only` + +#### Benchmarking options: +- `-c, --client=NUM` — number of concurrent database clients (default: 1) +- `-C, --connect` — establish new connection for each transaction +- `-D, --define=VARNAME=VALUE` — define variable for use by custom script +- `-j, --jobs=NUM` — number of threads (default: 1) +- `-l, --log` — write transaction times to log file +- `-L, --latency-limit=NUM` — count transactions lasting more than NUM ms as late +- `-m, --mode=regular|camo|failover` — mode in which pgbench should run (default: `regular`) +- `-M, --protocol=simple|extended|prepared` — protocol for submitting queries (default: `simple`) +- `-n, --no-vacuum` — do not run `VACUUM` before tests +- `-o, --set-option=NAME=VALUE` — specify runtime SET option +- `-P, --progress=NUM` — show thread progress report every NUM seconds +- `-r, --report-per-command` — latencies, failures and retries per command +- `-R, --rate=NUM` — target rate in transactions per second +- `-s, --scale=NUM` — report this scale factor in output +- `-t, --transactions=NUM` — number of transactions each client runs (default: 10) +- `-T, --time=NUM` — duration of benchmark test in seconds +- `-v, --vacuum-all` — vacuum all four standard tables before tests +- `--aggregate-interval=NUM` — data over NUM seconds +- `--failures-detailed` — report the failures grouped by basic types +- `--log-prefix=PREFIX` — prefix for transaction time log file (default: `pgbench_log`) +- `--max-tries=NUM` — max number of tries to run transaction (default: 1) +- `--progress-timestamp` — use Unix epoch timestamps for progress +- `--random-seed=SEED` — set random seed ("time", "rand", integer) +- `--retry` — retry transactions on failover, used with "-m" +- `--sampling-rate=NUM` — fraction of transactions to log (e.g., 0.01 for 1%) +- `--show-script=NAME` — show builtin script code, then exit +- `--verbose-errors` — print messages of all errors + +#### Common options: +- `-d, --debug` — print debugging output +- `-h, --host=HOSTNAME` — database server host or socket directory +- `-p, --port=PORT` — database server port number +- `-U, --username=USERNAME` — connect as specified database user +- `-V, --version` — output version information, then exit +- `-?, --help` — show help, then exit + diff --git a/product_docs/docs/pgd/5/testingandtuning.mdx b/product_docs/docs/pgd/5/testingandtuning.mdx index 1609106536a..3edbbb9f4ff 100644 --- a/product_docs/docs/pgd/5/testingandtuning.mdx +++ b/product_docs/docs/pgd/5/testingandtuning.mdx @@ -3,13 +3,10 @@ title: Testing and Tuning PGD clusters navTitle: Testing and Tuning --- -## Application testing - -You can test PGD applications using the following programs, -in addition to other techniques: +You can test PGD applications using the following approaches: - [Trusted Postgres Architect](#trusted-postgres-architect) -- [pgd_bench with CAMO/Failover options](#pgd_bench-with-camofailover-options) +- [pgd_bench with CAMO/Failover options](#pgd_bench) ### Trusted Postgres Architect @@ -29,9 +26,30 @@ We strongly recommend that developers write their own multi-node suite of Trusted Postgres Architect tests that verify the main expected properties of the application. -### pgd_bench with CAMO/failover options +### pgd_bench + +The Postgres benchmarking application +[`pgbench`](https://www.postgresql.org/docs/current/pgbench.html) has been +extended in PGD 5.0 in the form of a new applications: `pgd_bench`. + +`pgd_bench` is a regular command-line utility that's added to PostgreSQL's bin +directory. The utility is based on the Community PostgreSQL `pgbench` tool bit +supports benchmarking CAMO transactions and PGD specific workloads. + +Functionality of the `pgd_bench` is a superset of those of `pgbench` but +requires the BDR extension to be installed in order to work properly. + +Key differences include: -The Postgres benchmarking application [`pgbench`](https://www.postgresql.org/docs/current/pgbench.html) has been extended in PGD 5.0 in the form of a new applications: `pgd_bench`. This version allows users to run failover tests while using CAMO or regular PGD deployments. +- Adjustments to the initialization (`-i` flag) with the standard + `pgbench` scenario to prevent global lock timeouts in certain cases +- `VACUUM` command in the standard scenario is executed on all nodes +- `pgd_bench` releases are tied to the releases of the BDR extension + and are built against the corresponding PostgreSQL flavour (this is + reflected in the output of `--version` flag) + +The current version allows users to run failover tests while using CAMO or +regular PGD deployments. The following options were added: @@ -57,7 +75,6 @@ In addition to these options, you must specify the connection information about the peer node for failover in [DSN form](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING). - Here's an example in a CAMO environment: ```sh @@ -74,6 +91,20 @@ In failover mode, if you specify `--retry`, then in-flight transactions are retried. In this scenario there's no way to find the status of in-flight transactions. +### Notes on pgd_bench useage + +- When using custom init-scripts it is important to understand implications behind the DDL commands. +It is generally recommended to wait for the secondary nodes to catch-up on the data-load steps +before proceeding with DDL operations such as `CREATE INDEX`. The latter acquire global locks which +can't be acquired until the data-load is complete and thus may time out. + +- No extra steps are taken to suppress client messages, such as `NOTICE`s and `WARNING`s emitted +by PostgreSQL and or any possible extensions including the BDR extension. It is the user's +responsibility to suppress them by setting appropriate variables (e.g. `client_min_messages`, +`bdr.camo_enable_client_warnings ` etc.). + + + ## Performance testing and tuning PGD allows you to issue write transactions onto multiple master nodes. Bringing @@ -115,29 +146,6 @@ If PGD is running slow, then we suggest the following: Use all of the normal Postgres tuning features to improve the speed of critical parts of your application. -## Use of table access methods (TAMs) in PGD - -PGD 5.0 supports two table access methods released with EDB Postgres 15.0. -These two table access methods have been certified and allowed in PGD 5.0: - - * Auto cluster - * Ref data - -Any other TAM is restricted until certified by EDB. -If you are planning to use any of the table access method on a table, -you need to configure that TAM on each participating node in the -PGD cluster. -To configure auto cluster or ref data TAM, follow these steps on each node: -1. Update `postgresql.conf` to specify TAMs `autocluster` or `refdata` for the - `shared_preload_libraries` parameter. -1. Restart the server and execute `CREATE EXTENSION autocluster;` or - `CREATE EXTENSION refdata;`. - -After you create the extension, you can use TAM to create a table using -`CREATE TABLE test USING autocluster;` or `CREATE TABLE test USING refdata;`. -This replicates to all the PGD nodes. -For more information on these table access methods, see [`CREATE TABLE`](/epas/latest/epas_compat_sql/36_create_table/). - From 6fce11e9b8e31f6234ca786c1bcc7872d2b8db50 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 30 Aug 2023 14:18:34 +0100 Subject: [PATCH 057/255] Expanded the mode types reference Signed-off-by: Dj Walker-Morgan --- .../docs/pgd/5/reference/testingandtuning.mdx | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/pgd/5/reference/testingandtuning.mdx b/product_docs/docs/pgd/5/reference/testingandtuning.mdx index c903371afce..ad0e2b60e0d 100644 --- a/product_docs/docs/pgd/5/reference/testingandtuning.mdx +++ b/product_docs/docs/pgd/5/reference/testingandtuning.mdx @@ -33,12 +33,13 @@ of `pgd_bench` options and usage. Which can be set to `regular`, `camo`, or `failover`. It defaults to `regular`. -* regular — regular description -* camo — -* failover — +* regular — Only a single node is needed to run `pgd_bench` +* camo — A second node must be specified to act as the camo partner +* failover — A second node must be specified to act as the failover. -When using `-m=failover`, an additional option `--retry` is available. This will -instruct `pgd_bench` to retry transactions when there is a failover. +When using `-m failover`, an additional option `--retry` is available. This will +instruct `pgd_bench` to retry transactions when there is a failover. The `--retry` +option is automatically enabled with `-m camo`. #### Setting GUC variables From 976f69fc6885948ad16069e7e47908ca3f4de486 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 30 Aug 2023 15:44:21 +0100 Subject: [PATCH 058/255] typo Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/testingandtuning.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/testingandtuning.mdx b/product_docs/docs/pgd/5/testingandtuning.mdx index 3edbbb9f4ff..80ba43519c1 100644 --- a/product_docs/docs/pgd/5/testingandtuning.mdx +++ b/product_docs/docs/pgd/5/testingandtuning.mdx @@ -91,7 +91,7 @@ In failover mode, if you specify `--retry`, then in-flight transactions are retried. In this scenario there's no way to find the status of in-flight transactions. -### Notes on pgd_bench useage +### Notes on pgd_bench usage - When using custom init-scripts it is important to understand implications behind the DDL commands. It is generally recommended to wait for the secondary nodes to catch-up on the data-load steps From 362c2fe05386172cde2bcd9103e174f13680c316 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Tue, 5 Sep 2023 12:17:57 +0100 Subject: [PATCH 059/255] Typos and fixes Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/reference/testingandtuning.mdx | 6 +++--- product_docs/docs/pgd/5/testingandtuning.mdx | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/pgd/5/reference/testingandtuning.mdx b/product_docs/docs/pgd/5/reference/testingandtuning.mdx index ad0e2b60e0d..05af18905a4 100644 --- a/product_docs/docs/pgd/5/reference/testingandtuning.mdx +++ b/product_docs/docs/pgd/5/reference/testingandtuning.mdx @@ -20,7 +20,7 @@ pgd_bench [OPTION]... [DBNAME] [DBNAME2] `DBNAME` may be a conninfo string of the format: `"host=10.1.1.2 user=postgres dbname=master"` -Consult the [Testing and Tuning - Pgd_bench](../testingandtuning#pgd_bench)] section for examples +Consult the [Testing and Tuning - Pgd_bench](../testingandtuning#pgd_bench) section for examples of `pgd_bench` options and usage. ### Options @@ -49,8 +49,8 @@ This option is followed by `NAME=VALUE` entries, which will be applied using the Postgresql [`SET`](https://www.postgresql.org/docs/current/sql-set.html) command on each server, and only those servers, that `pgd_bench` connects to. The other options are identical to the Community PostgreSQL `pgbench`. For more -details, consult the [official documentation on -`pgbench`](https://www.postgresql.org/docs/current/pgbench.html). +details, consult the official documentation on +[`pgbench`](https://www.postgresql.org/docs/current/pgbench.html). We list all the options (`pgd_bench` and `pgbench`) below for completeness. diff --git a/product_docs/docs/pgd/5/testingandtuning.mdx b/product_docs/docs/pgd/5/testingandtuning.mdx index 80ba43519c1..85849cda39a 100644 --- a/product_docs/docs/pgd/5/testingandtuning.mdx +++ b/product_docs/docs/pgd/5/testingandtuning.mdx @@ -32,7 +32,7 @@ The Postgres benchmarking application [`pgbench`](https://www.postgresql.org/docs/current/pgbench.html) has been extended in PGD 5.0 in the form of a new applications: `pgd_bench`. -`pgd_bench` is a regular command-line utility that's added to PostgreSQL's bin +[`pgd_bench`](/pgd/latest/reference/testingandtuning#pgd_bench) is a regular command-line utility that's added to PostgreSQL's bin directory. The utility is based on the Community PostgreSQL `pgbench` tool bit supports benchmarking CAMO transactions and PGD specific workloads. From d91fdf2c6b78a573ce7fbee76fb69f98fca8fca4 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Tue, 5 Sep 2023 12:24:11 +0100 Subject: [PATCH 060/255] Update product_docs/docs/pgd/5/testingandtuning.mdx Co-authored-by: Nick Babadzhanian <33933459+pgnickb@users.noreply.github.com> --- product_docs/docs/pgd/5/testingandtuning.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/testingandtuning.mdx b/product_docs/docs/pgd/5/testingandtuning.mdx index 85849cda39a..06931bee105 100644 --- a/product_docs/docs/pgd/5/testingandtuning.mdx +++ b/product_docs/docs/pgd/5/testingandtuning.mdx @@ -33,7 +33,7 @@ The Postgres benchmarking application extended in PGD 5.0 in the form of a new applications: `pgd_bench`. [`pgd_bench`](/pgd/latest/reference/testingandtuning#pgd_bench) is a regular command-line utility that's added to PostgreSQL's bin -directory. The utility is based on the Community PostgreSQL `pgbench` tool bit +directory. The utility is based on the Community PostgreSQL `pgbench` tool but supports benchmarking CAMO transactions and PGD specific workloads. Functionality of the `pgd_bench` is a superset of those of `pgbench` but From e9d8a27830ef21cb2abb07d40a1c3eb8d54763d7 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Tue, 5 Sep 2023 12:24:46 +0100 Subject: [PATCH 061/255] Update product_docs/docs/pgd/5/reference/testingandtuning.mdx Co-authored-by: Nick Babadzhanian <33933459+pgnickb@users.noreply.github.com> --- product_docs/docs/pgd/5/reference/testingandtuning.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/reference/testingandtuning.mdx b/product_docs/docs/pgd/5/reference/testingandtuning.mdx index 05af18905a4..317b6746400 100644 --- a/product_docs/docs/pgd/5/reference/testingandtuning.mdx +++ b/product_docs/docs/pgd/5/reference/testingandtuning.mdx @@ -34,7 +34,7 @@ of `pgd_bench` options and usage. Which can be set to `regular`, `camo`, or `failover`. It defaults to `regular`. * regular — Only a single node is needed to run `pgd_bench` -* camo — A second node must be specified to act as the camo partner +* camo — A second node must be specified to act as the CAMO-partner (CAMO should be set up) * failover — A second node must be specified to act as the failover. When using `-m failover`, an additional option `--retry` is available. This will From 531ad64527d37e9915c3f4bbef305d14f34ac71c Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Mon, 4 Sep 2023 10:03:35 +0100 Subject: [PATCH 062/255] Essential fix and relocate of information Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/known_issues.mdx | 2 -- product_docs/docs/pgd/5/limitations.mdx | 21 +++++++++++++++++++++ 2 files changed, 21 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pgd/5/known_issues.mdx b/product_docs/docs/pgd/5/known_issues.mdx index 072f22d8c02..a6314e90a4e 100644 --- a/product_docs/docs/pgd/5/known_issues.mdx +++ b/product_docs/docs/pgd/5/known_issues.mdx @@ -44,8 +44,6 @@ release. - Transactions using Eager Replication can't yet execute DDL. The TRUNCATE command is allowed. -- Not all DDL can run when either CAMO or Group Commit is used. - - Parallel apply isn't currently supported in combination with Group Commit. Make sure to disable it when using Group Commit by either: - Setting `num_writers` to 1 for the node group using [`bdr.alter_node_group_config`](/pgd/latest/reference/nodes-management-interfaces/#bdralter_node_group_config). - Using the GUC `bdr.writers_per_subscription`. See [Configuration of generic replication](/pgd/latest/reference/pgd-settings/#generic-replication). diff --git a/product_docs/docs/pgd/5/limitations.mdx b/product_docs/docs/pgd/5/limitations.mdx index 286c2829b5b..06590444dbc 100644 --- a/product_docs/docs/pgd/5/limitations.mdx +++ b/product_docs/docs/pgd/5/limitations.mdx @@ -108,6 +108,27 @@ Be sure to disable transaction streaming when planning to use CAMO. You can configure this option globally or in the PGD node group. See [Transaction streaming configuration](../transaction-streaming#configuration). +- Not all DDL can run when CAMO is used. The only supported DDL operations are: + - non-concurrent CREATE INDEX + - non-concurrent DROP INDEX + - non-concurrent REINDEX of an individual table or index + - CLUSTER (of a single relation or index only) + - ANALYZE + - TRUNCATE + +## Group Commit + +[Group Commit](durability/group-commit) is a feature which enables configurable synchronous commits over +nodes in a group. If you use this feature, take the following limitations into account: + +- Not all DDL can run when Group Commit is used. The only supported DDL operations are: + - non-concurrent CREATE INDEX + - non-concurrent DROP INDEX + - non-concurrent REINDEX of an individual table or index + - CLUSTER (of a single relation or index only) + - ANALYZE + - TRUNCATE + ## Other limitations This noncomprehensive list includes other limitations that are expected and From aa84e08a7c924209827d35d961cd4d1bfa47ed58 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Wed, 6 Sep 2023 10:32:57 +0100 Subject: [PATCH 063/255] Update camo DDL for more precision. --- product_docs/docs/pgd/5/limitations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/limitations.mdx b/product_docs/docs/pgd/5/limitations.mdx index 06590444dbc..b621d1ac587 100644 --- a/product_docs/docs/pgd/5/limitations.mdx +++ b/product_docs/docs/pgd/5/limitations.mdx @@ -108,7 +108,7 @@ Be sure to disable transaction streaming when planning to use CAMO. You can configure this option globally or in the PGD node group. See [Transaction streaming configuration](../transaction-streaming#configuration). -- Not all DDL can run when CAMO is used. The only supported DDL operations are: +- Not all DDL can run when CAMO is used. If unsupported DDL is used a warning will be logged and the transactions commit scope will be set to local only. The only supported DDL operations are: - non-concurrent CREATE INDEX - non-concurrent DROP INDEX - non-concurrent REINDEX of an individual table or index From 6876d0109d7a222e060a22489cfa765b366bc85d Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 6 Sep 2023 10:56:30 +0100 Subject: [PATCH 064/255] Expanded CAMO DDL text and repeated for GC and Eager Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/limitations.mdx | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pgd/5/limitations.mdx b/product_docs/docs/pgd/5/limitations.mdx index b621d1ac587..87c3db87415 100644 --- a/product_docs/docs/pgd/5/limitations.mdx +++ b/product_docs/docs/pgd/5/limitations.mdx @@ -108,7 +108,8 @@ Be sure to disable transaction streaming when planning to use CAMO. You can configure this option globally or in the PGD node group. See [Transaction streaming configuration](../transaction-streaming#configuration). -- Not all DDL can run when CAMO is used. If unsupported DDL is used a warning will be logged and the transactions commit scope will be set to local only. The only supported DDL operations are: +- Not all DDL can run when CAMO is used. If unsupported DDL is used a warning is logged +and the transactions commit scope is set to local only. The only supported DDL operations are: - non-concurrent CREATE INDEX - non-concurrent DROP INDEX - non-concurrent REINDEX of an individual table or index @@ -121,7 +122,8 @@ CAMO. You can configure this option globally or in the PGD node group. See [Group Commit](durability/group-commit) is a feature which enables configurable synchronous commits over nodes in a group. If you use this feature, take the following limitations into account: -- Not all DDL can run when Group Commit is used. The only supported DDL operations are: +- Not all DDL can run when Group Commit is used. If unsupported DDL is used a warning is logged +and the transactions commit scope is set to local only. The only supported DDL operations are: - non-concurrent CREATE INDEX - non-concurrent DROP INDEX - non-concurrent REINDEX of an individual table or index @@ -129,6 +131,10 @@ nodes in a group. If you use this feature, take the following limitations into a - ANALYZE - TRUNCATE +## Eager + +[Eager](consistency/eager) is a feature which is available in Group Commit which enables conflicts to be avoided by eagerly aborting transactions that may clash. It is subject to the same limitations as Group Commit. + ## Other limitations This noncomprehensive list includes other limitations that are expected and From 775498eacc39739c86fe56d7e3d6a6e2e641e70f Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Thu, 7 Sep 2023 10:48:18 -0400 Subject: [PATCH 065/255] EPAS: Fix note formatting --- .../sql_reference/02_data_types/02_character_types.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/epas/15/reference/sql_reference/02_data_types/02_character_types.mdx b/product_docs/docs/epas/15/reference/sql_reference/02_data_types/02_character_types.mdx index 984bb6b15cb..1a0746f45ac 100644 --- a/product_docs/docs/epas/15/reference/sql_reference/02_data_types/02_character_types.mdx +++ b/product_docs/docs/epas/15/reference/sql_reference/02_data_types/02_character_types.mdx @@ -39,8 +39,9 @@ VARCHAR, VARCHAR2, NVARCHAR and NVARCHAR2 If the string to assign is shorter than `n`, values of type `VARCHAR`, `VARCHAR2`, `NVARCHAR`, and `NVARCHAR2` store the shorter string without padding. - !!! Note - The trailing spaces are semantically significant in `VARCHAR` values. +!!! Note +The trailing spaces are semantically significant in `VARCHAR` values. +!!! If you explicitly cast a value to a `VARCHAR` type, an over-length value is truncated to `n` characters without raising an error (as specified by the SQL standard). @@ -55,4 +56,4 @@ VARCHAR, VARCHAR2, NVARCHAR and NVARCHAR2 Thus, use of the `CLOB` type is limited by what can be done for `TEXT`, such as a maximum size of approximately 1 GB. - For larger amounts of data, instead of using the `CLOB` data type, use the PostgreSQL *large objects* feature that relies on the `pg_largeobject` system catalog. For information on large objects, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/largeobjects.html). \ No newline at end of file + For larger amounts of data, instead of using the `CLOB` data type, use the PostgreSQL *large objects* feature that relies on the `pg_largeobject` system catalog. For information on large objects, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/largeobjects.html). From de057a033c13c72f354b1d75b2ffcac2042d7803 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 7 Sep 2023 13:02:27 -0400 Subject: [PATCH 066/255] Kasten by Veeam rename edits --- .../02-PartnerInformation.mdx | 2 +- .../partner_docs/KastenbyVeeam/03-SolutionSummary.mdx | 10 ++++++++++ .../04-ConfiguringVeeamKasten.mdx | 9 +++++---- .../05-UsingVeeamKasten.mdx | 2 +- .../06-CertificationEnvironment.mdx | 2 +- .../07-SupportandLogging.mdx | 4 ++-- .../Images/KastenBackupPolicywithHooks.png | 0 .../Images/KastenRestorePoint.png | 0 .../Images/KastenSolutionSummaryImagenew.png | 0 .../Images/LaunchaBackup.png | 0 .../Images/PartnerProgram.jpg.png | 0 .../Images/VeeamKastenLogging.png | 0 .../{VeeamKasten => KastenbyVeeam}/index.mdx | 4 ++-- .../partner_docs/VeeamKasten/03-SolutionSummary.mdx | 10 ---------- src/pages/index.js | 4 ++-- 15 files changed, 24 insertions(+), 23 deletions(-) rename advocacy_docs/partner_docs/{VeeamKasten => KastenbyVeeam}/02-PartnerInformation.mdx (92%) create mode 100644 advocacy_docs/partner_docs/KastenbyVeeam/03-SolutionSummary.mdx rename advocacy_docs/partner_docs/{VeeamKasten => KastenbyVeeam}/04-ConfiguringVeeamKasten.mdx (93%) rename advocacy_docs/partner_docs/{VeeamKasten => KastenbyVeeam}/05-UsingVeeamKasten.mdx (92%) rename advocacy_docs/partner_docs/{VeeamKasten => KastenbyVeeam}/06-CertificationEnvironment.mdx (87%) rename advocacy_docs/partner_docs/{VeeamKasten => KastenbyVeeam}/07-SupportandLogging.mdx (92%) rename advocacy_docs/partner_docs/{VeeamKasten => KastenbyVeeam}/Images/KastenBackupPolicywithHooks.png (100%) rename advocacy_docs/partner_docs/{VeeamKasten => KastenbyVeeam}/Images/KastenRestorePoint.png (100%) rename advocacy_docs/partner_docs/{VeeamKasten => KastenbyVeeam}/Images/KastenSolutionSummaryImagenew.png (100%) rename advocacy_docs/partner_docs/{VeeamKasten => KastenbyVeeam}/Images/LaunchaBackup.png (100%) rename advocacy_docs/partner_docs/{VeeamKasten => KastenbyVeeam}/Images/PartnerProgram.jpg.png (100%) rename advocacy_docs/partner_docs/{VeeamKasten => KastenbyVeeam}/Images/VeeamKastenLogging.png (100%) rename advocacy_docs/partner_docs/{VeeamKasten => KastenbyVeeam}/index.mdx (81%) delete mode 100644 advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx diff --git a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/02-PartnerInformation.mdx similarity index 92% rename from advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx rename to advocacy_docs/partner_docs/KastenbyVeeam/02-PartnerInformation.mdx index c6deb89af54..509aaaba12c 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/02-PartnerInformation.mdx @@ -5,7 +5,7 @@ description: 'Details of the Partner' --- |   |   | | ----------- | ----------- | -| **Partner Name** | Veeam Kasten | +| **Partner Name** | Kasten by Veeam | | **Web Site** | https://www.kasten.io/ | | **Partner Product** | Kasten K10 | | **Version** | Kasten 6.0 | diff --git a/advocacy_docs/partner_docs/KastenbyVeeam/03-SolutionSummary.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/03-SolutionSummary.mdx new file mode 100644 index 00000000000..9e2d3a5a7de --- /dev/null +++ b/advocacy_docs/partner_docs/KastenbyVeeam/03-SolutionSummary.mdx @@ -0,0 +1,10 @@ +--- +title: 'Solution Summary' +description: 'Explanation of the solution and its purpose' +--- + +Kasten by Veeam is a data management platform built for Kubernetes that can provide enterprise operations teams with an easy-to-use and secure system for backup and restore of Kubernetes applications. Kasten can be used in conjunction with EDB Postgres for Kubernetes and the EDB external backup adapter to successfully backup and restore data. + +The EDB Postgres for Kubernetes [external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) allows for a third party tool, such as Kasten by Veeam, to discover an API that is needed in order to create a successful backup. + +![Kasten K10 Architecture](Images/KastenSolutionSummaryImagenew.png) diff --git a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx similarity index 93% rename from advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx rename to advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx index 4b092088874..9f45430a2aa 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx @@ -3,21 +3,22 @@ title: 'Configuration' description: 'Walkthrough on configuring the integration' --- -Implementing EDB Postgres for Kubernetes with Veeam Kasten requires the following components: +Implementing EDB Postgres for Kubernetes with Kasten by Veeam requires the following components: - [EDB Postgres for Kubernetes](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/) - [EDB Postgres for Kubernetes external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) -- [Veeam Kasten K10](https://docs.kasten.io/latest/index.html) +- [Kasten K10](https://docs.kasten.io/latest/index.html) ## Prerequisites - EDB Postgres for Kubernetes configured and running - EDB Postgres for Kubernetes external backup adapter configured per your system requirements -- Veeam Kasten K10 installed on your system +- Kasten K10 installed on your system !!! Note For this integration, use the **example.yaml** files provided in each section for the appropriate Kasten configuration pieces, and change any environment variables per your specific needs. - The **Add the Backup Decorator Annotations to the Cluster** section is the important section for the Kasten addon integration. + The **Add the Backup Decorator Annotations to the Cluster** section is the important section for the Kasten addon integration. + Refer to the EDB docs for more information on the [EDB Postgres for Kubernetes external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) to view more detailed information on the EDB Postgres for Kubernetes backup adaptor addon functionality and additional details on its configuraton parameters. ## Install the Operator diff --git a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx similarity index 92% rename from advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx rename to advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx index 606dc049a3d..79f2dde19b6 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/05-UsingVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx @@ -29,7 +29,7 @@ When you have configured your Kubernetes environment per the `Configuring` secti ## Restore Database -1. To get ready for a Kasten K10 to complete a restore, we will remove the EDB namespace in this example. +1. To get ready for Kasten K10 to complete a restore, we will remove the EDB namespace in this example. ```bash kubectl delete ns edb diff --git a/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/06-CertificationEnvironment.mdx similarity index 87% rename from advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx rename to advocacy_docs/partner_docs/KastenbyVeeam/06-CertificationEnvironment.mdx index 8dac87a7df8..2f1d83e235b 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/06-CertificationEnvironment.mdx @@ -8,4 +8,4 @@ description: 'Overview of the certification environment' | **Certification Test Date** | August 28, 2023 | | **EDB Postgres for Kubernetes** | 1.20.2 | | **EDB Postgres for Kubernetes External Backup Adapter** | -| **Veeam Kasten** | 6.0 | +| **Kasten by Veeam Kasten K10** | 6.0 | diff --git a/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/07-SupportandLogging.mdx similarity index 92% rename from advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx rename to advocacy_docs/partner_docs/KastenbyVeeam/07-SupportandLogging.mdx index 4ba382d07b7..630405dd64c 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/07-SupportandLogging.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/07-SupportandLogging.mdx @@ -23,7 +23,7 @@ The default log directories for PostgreSQL logs vary depending on the operating - Windows: `C:\Program Files\PostgreSQL\9.3\data\pg_log` -**Veeam Logs** +**Kasten by Veeam Logs** -On the Kasten UI you need to navigate to `Settings` then `Support` then you will click `Download Logs`. +On the Kasten K10 UI navigate to `Settings` then `Support` then click `Download Logs`. ![Veeam Kasten Logs](Images/VeeamKastenLogging.png) diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/KastenBackupPolicywithHooks.png b/advocacy_docs/partner_docs/KastenbyVeeam/Images/KastenBackupPolicywithHooks.png similarity index 100% rename from advocacy_docs/partner_docs/VeeamKasten/Images/KastenBackupPolicywithHooks.png rename to advocacy_docs/partner_docs/KastenbyVeeam/Images/KastenBackupPolicywithHooks.png diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/KastenRestorePoint.png b/advocacy_docs/partner_docs/KastenbyVeeam/Images/KastenRestorePoint.png similarity index 100% rename from advocacy_docs/partner_docs/VeeamKasten/Images/KastenRestorePoint.png rename to advocacy_docs/partner_docs/KastenbyVeeam/Images/KastenRestorePoint.png diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImagenew.png b/advocacy_docs/partner_docs/KastenbyVeeam/Images/KastenSolutionSummaryImagenew.png similarity index 100% rename from advocacy_docs/partner_docs/VeeamKasten/Images/KastenSolutionSummaryImagenew.png rename to advocacy_docs/partner_docs/KastenbyVeeam/Images/KastenSolutionSummaryImagenew.png diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/LaunchaBackup.png b/advocacy_docs/partner_docs/KastenbyVeeam/Images/LaunchaBackup.png similarity index 100% rename from advocacy_docs/partner_docs/VeeamKasten/Images/LaunchaBackup.png rename to advocacy_docs/partner_docs/KastenbyVeeam/Images/LaunchaBackup.png diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/PartnerProgram.jpg.png b/advocacy_docs/partner_docs/KastenbyVeeam/Images/PartnerProgram.jpg.png similarity index 100% rename from advocacy_docs/partner_docs/VeeamKasten/Images/PartnerProgram.jpg.png rename to advocacy_docs/partner_docs/KastenbyVeeam/Images/PartnerProgram.jpg.png diff --git a/advocacy_docs/partner_docs/VeeamKasten/Images/VeeamKastenLogging.png b/advocacy_docs/partner_docs/KastenbyVeeam/Images/VeeamKastenLogging.png similarity index 100% rename from advocacy_docs/partner_docs/VeeamKasten/Images/VeeamKastenLogging.png rename to advocacy_docs/partner_docs/KastenbyVeeam/Images/VeeamKastenLogging.png diff --git a/advocacy_docs/partner_docs/VeeamKasten/index.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/index.mdx similarity index 81% rename from advocacy_docs/partner_docs/VeeamKasten/index.mdx rename to advocacy_docs/partner_docs/KastenbyVeeam/index.mdx index a054806aef1..c5b88448b4d 100644 --- a/advocacy_docs/partner_docs/VeeamKasten/index.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/index.mdx @@ -1,5 +1,5 @@ --- -title: 'Veeam Kasten Implementation Guide' +title: 'Kasten by Veeam Implementation Guide' indexCards: simple directoryDefaults: iconName: handshake @@ -9,6 +9,6 @@ directoryDefaults:

EDB GlobalConnect Technology Partner Implementation Guide

-

Veeam Kasten

+

Kasten by Veeam for Kasten K10

This document is intended to augment each vendor’s product documentation in order to guide the reader in getting the products working together. It is not intended to show the optimal configuration for the certified integration.

\ No newline at end of file diff --git a/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx b/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx deleted file mode 100644 index 0d079d0a6c3..00000000000 --- a/advocacy_docs/partner_docs/VeeamKasten/03-SolutionSummary.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: 'Solution Summary' -description: 'Explanation of the solution and its purpose' ---- - -Veeam Kasten is a data management platform built for Kubernetes that can provide enterprise operations teams with an easy-to-use and secure system for backup and restore of Kubernetes applications. Veeam Kasten can be used in conjunction with EDB Postgres for Kubernetes and the EDB external backup adapter to successfully backup and restore data. - -The EDB Postgres for Kubernetes [external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) allows for a third party tool such as Veeam Kasten to discover an API that is needed in order to create a successful backup. - -![Kasten K10 Architecture](Images/KastenSolutionSummaryImagenew.png) diff --git a/src/pages/index.js b/src/pages/index.js index 82d40c8787c..2efd46d417f 100644 --- a/src/pages/index.js +++ b/src/pages/index.js @@ -343,8 +343,8 @@ const Page = () => ( Repostor Data Protector for PostgresSQL - - Veeam Kasten + + Kasten by Veeam for Kasten K10 Veritas NetBackup for PostgreSQL From 5d4bd86b69e6b9cf25e41f788cfba50f5853cfe5 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 7 Sep 2023 13:18:55 -0400 Subject: [PATCH 067/255] Updated Spacing --- .../partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx index 9f45430a2aa..864f91e4ede 100644 --- a/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx @@ -17,7 +17,9 @@ Implementing EDB Postgres for Kubernetes with Kasten by Veeam requires the follo !!! Note For this integration, use the **example.yaml** files provided in each section for the appropriate Kasten configuration pieces, and change any environment variables per your specific needs. + The **Add the Backup Decorator Annotations to the Cluster** section is the important section for the Kasten addon integration. + Refer to the EDB docs for more information on the [EDB Postgres for Kubernetes external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) to view more detailed information on the EDB Postgres for Kubernetes backup adaptor addon functionality and additional details on its configuraton parameters. ## Install the Operator From f40b0f426227ed85299eb1f38e67302ce9099255 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 7 Sep 2023 13:22:18 -0400 Subject: [PATCH 068/255] Few More Kasten Edits --- .../partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx index 79f2dde19b6..665df53f8ea 100644 --- a/advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx @@ -9,14 +9,14 @@ When you have configured your Kubernetes environment per the `Configuring` secti 1. Launch your Kasten K10 interface. -2. Use Veeam Kasten K10 launch a backup that creates two restore points, a local and a remote. +2. Use Kasten K10 to launch a backup that creates two restore points, a local and a remote. 3. You now have a backup we can use to validate a restore in the next section ![Launch a Backup](Images/LaunchaBackup.png) !!! Note - The Veeam backup process is explained below: + The Kasten by Veeam backup process is explained below: 1. EDB elects a replica for the backup. 2. Kasten will discover the replica. 3. Kasten calls the EDB pre-backup command on the discovered replica. @@ -35,11 +35,11 @@ When you have configured your Kubernetes environment per the `Configuring` secti kubectl delete ns edb ``` -2. In the Kasten interface go to your remote restore point. +2. In the Kasten K10 interface go to your remote restore point. 3. On the remote restore point select `restore`. -4. After you have restored all of your data will be present. +4. After the restore is complete, all of your data will be present. ![Kasten Data Restore Point](Images/KastenRestorePoint.png) From f7d3341b3e1666aaa224ab42c17f97870c25d07a Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Thu, 7 Sep 2023 13:31:23 -0400 Subject: [PATCH 069/255] Wording change --- .../partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx index 864f91e4ede..fc6a1fbfcef 100644 --- a/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx @@ -20,7 +20,7 @@ Implementing EDB Postgres for Kubernetes with Kasten by Veeam requires the follo The **Add the Backup Decorator Annotations to the Cluster** section is the important section for the Kasten addon integration. - Refer to the EDB docs for more information on the [EDB Postgres for Kubernetes external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) to view more detailed information on the EDB Postgres for Kubernetes backup adaptor addon functionality and additional details on its configuraton parameters. + Refer to the [EDB Postgres for Kubernetes external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) docs to view more detailed information on the EDB Postgres for Kubernetes backup adaptor addon functionality and additional details on its configuraton parameters. ## Install the Operator From bc367ac44dafc4468f673615e5e09ee95293d870 Mon Sep 17 00:00:00 2001 From: Arthur Nascimento Date: Thu, 7 Sep 2023 15:33:50 -0300 Subject: [PATCH 070/255] Update 06_configuring_for_eager_failover.mdx The safest way for end users to edit service files is using `systemctl edit`. Alternatively, we can instruct them on how to edit the overrides files in `/etc/systemd/system/.d/override.conf`. But creating a new file and `.include` shouldn't have been an option. Moreover, the `.include` feature has been removed from recent systemd versions, so it must be changed before it starts erroring out in the customer's hands. --- .../06_configuring_for_eager_failover.mdx | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx b/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx index 5d55cccb262..af73de8805b 100644 --- a/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx +++ b/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx @@ -29,18 +29,17 @@ You can set up Eager Failover by performing the following steps. The example us - Ensure that the database server and the local Failover Manager agent are running. -- As root, create `/etc/systemd/system/edb-as-12.service` file and include: +- As root, edit the service `edb-as-12.service` file using the command: - ```ini - .include /lib/systemd/system/edb-as-12.service - [Unit] - BindsTo=edb-efm-4.5.service + ```shell + systemctl edit edb-as-12.service ``` -- Run the following command to reload the configuration files: +- Add the following lines into the text editor, then save: - ```shell - systemctl daemon-reload + ```ini + [Unit] + BindsTo=edb-efm-4.5.service ``` With these changes, when the Failover Manager agent is stopped or ended, the rest of the cluster treats this situation as a failure and attempts a failover. From 3e23fc93a6cb4b7b77ae0abaeefa2949f8838392 Mon Sep 17 00:00:00 2001 From: Fran Coughlin <132373434+francoughlin@users.noreply.github.com> Date: Thu, 7 Sep 2023 15:09:54 -0400 Subject: [PATCH 071/255] Update managing_clusters.mdx Fixed file reference error: changed conf_file to config_file. --- .../biganimal/release/reference/cli/managing_clusters.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx index 2707e232191..83e9bab41b2 100644 --- a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx @@ -293,7 +293,7 @@ The syntax of the command is: biganimal pgd create --config-file ``` -Where `` is a valid path to a YAML configuration file. For example: +Where `` is a valid path to a YAML configuration file. For example: ``` clusterName: pgd-cli-name @@ -347,7 +347,7 @@ The syntax of the command is: biganimal pgd add-group --config-file ``` -Where `` is a valid path to a YAML configuration file. For example: +Where `` is a valid path to a YAML configuration file. For example: ``` clusterId: clusterID @@ -385,7 +385,7 @@ The syntax of the command is: pgd update [--config-file] ``` -Where `` is a valid path to a YAML configuration file with the same format as a configuration file for creating a distributed high-availability cluster. See [Create a distributed high-availability cluster](#create-a-distributed-high-availability-cluster). +Where `` is a valid path to a YAML configuration file with the same format as a configuration file for creating a distributed high-availability cluster. See [Create a distributed high-availability cluster](#create-a-distributed-high-availability-cluster). ### Show distributed high-availability clusters @@ -407,7 +407,7 @@ The syntax of the command is: pgd restore [--config-file] ``` -Where `` is a valid path to a YAML configuration file. For example: +Where `` is a valid path to a YAML configuration file. For example: ``` clusterName: pgd-restore-name From 7cdc2e62aff0eab9541a0b7439815fda8d5bd6d5 Mon Sep 17 00:00:00 2001 From: Arthur Nascimento Date: Thu, 7 Sep 2023 17:06:38 -0300 Subject: [PATCH 072/255] Update 05_using_efm.mdx This changes the instructions on how to customize systemd service files. The instructions were directing the reader to edit files in /usr/lib/systemd/system, which is not the adequate location. Whenever a system administrator edits service files, they should always do so in /etc/systemd/system, either with systemctl edit or editing the files directly, but never editing anything in /lib or /usr. --- product_docs/docs/efm/4/05_using_efm.mdx | 30 ++++++++++++++++-------- 1 file changed, 20 insertions(+), 10 deletions(-) diff --git a/product_docs/docs/efm/4/05_using_efm.mdx b/product_docs/docs/efm/4/05_using_efm.mdx index fe797d2ee82..0ade30d911d 100644 --- a/product_docs/docs/efm/4/05_using_efm.mdx +++ b/product_docs/docs/efm/4/05_using_efm.mdx @@ -265,27 +265,37 @@ 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 `edb-efm-4.` unit file to a new file with a name that is unique for each cluster. For example, if you have two clusters named acctg and sales, the unit file names might be: +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..service` to `/etc/systemd/system` with a new name that is unique for each cluster. -```text -/usr/lib/systemd/system/efm-acctg.service +For example, if you have two clusters named `acctg` and `sales` managed by EFM 4.7, the unit file names might be `efm-acctg.service` and `efm-sales.service`, and they can be created with: -/usr/lib/systemd/system/efm-sales.service +```shell +cp /usr/lib/systemd/system/edb-efm-4.7.service /etc/systemd/system/efm-acctg.service +cp /usr/lib/systemd/system/edb-efm-4.7.service /etc/systemd/system/efm-sales.service ``` -Then, edit the `CLUSTER` variable in each unit file, changing the specified cluster name from `efm` to the new cluster name. For example, for a cluster named `acctg`, the value specifies: +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. -```text +In our 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 ``` -Also update the value of the `PIDfile` parameter to specify the new cluster name. For example: +And edit the `sales` cluster by running `systemctl edit efm-sales.service` and write: ```ini -PIDFile=/var/run/efm-4.7/acctg.pid +[Service] +Environment=CLUSTER=sales +PIDFile=/run/efm-4.7/sales.pid ``` -After copying the service scripts, enable the services: +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. + +After saving the changes, enable the services: ```text # systemctl enable efm-acctg.service @@ -296,7 +306,7 @@ After copying the service scripts, enable the services: Then, use the new service scripts to start the agents. For example, to start the `acctg` agent: ```text -# systemctl start efm-acctg` +# systemctl start efm-acctg ``` For information about customizing a unit file, see [Understanding and administering systemd](https://docs.fedoraproject.org/en-US/quick-docs/understanding-and-administering-systemd/index.html). From c9a129c08b2f95344130aa6f5fd6567f51ec6aa2 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 24 Aug 2023 15:37:09 -0400 Subject: [PATCH 073/255] edits to PGD CLI content --- .../docs/pgd/5/cli/discover_connections.mdx | 40 ++++++++++++------- product_docs/docs/pgd/5/cli/index.mdx | 6 +-- .../docs/pgd/5/cli/installing_cli.mdx | 9 ++--- product_docs/docs/pgd/5/cli/using_cli.mdx | 24 +++++------ 4 files changed, 45 insertions(+), 34 deletions(-) diff --git a/product_docs/docs/pgd/5/cli/discover_connections.mdx b/product_docs/docs/pgd/5/cli/discover_connections.mdx index 61bde0b5ed4..84c468b3638 100644 --- a/product_docs/docs/pgd/5/cli/discover_connections.mdx +++ b/product_docs/docs/pgd/5/cli/discover_connections.mdx @@ -1,23 +1,27 @@ --- -title: "Discovering Connection Strings" -navTitle: "Discovering Connection Strings" +title: "Discovering connection strings" +navTitle: "Discovering connection strings" indexdepth: 2 deepToC: true --- -PGD CLI can be installed on any system which is able to connect to the PGD cluster. You will require a user with PGD superuser privileges - the [bdr_superuser role](../security) - or equivalent (e.g. edb_admin on BigAnimal distributed high-availability) to use PGD CLI. +You can install PGD CLI on any system that can connect to the PGD cluster. To use PGD CLI, you need a user with PGD superuser privileges or equivalent. The PGD user with superuser privileges is the [bdr_superuser role](../security). An example of an equivalent user is edb_admin on a BigAnimal distributed high-availability cluster. ## PGD CLI and database connection strings -You may not need a database connection string. For example, when Trusted Postgres Architect installs the PGD CLI on a system, it also configures the connection to the PGD cluster. This means that PGD CLI will automatically connect when run. +You might not need a database connection string. For example, when Trusted Postgres Architect installs the PGD CLI on a system, it also configures the connection to the PGD cluster. This means that PGD CLI can connect to the cluster when run. ## Getting your database connection string -Every deployment method has a different way of deriving a connection string for it. This is because of the range of different configurations that PGD supports. Generally, you can obtain the required information from the configuration of your deployment; this section provides a guide of how to assemble that information into connection strings. +Because of the range of different configurations that PGD supports, every deployment method has a different way of deriving a connection string for it. Generally, you can obtain the required information from the configuration of your deployment. You can then assemble that information into connection strings. ### For a TPA-deployed PGD cluster -Because TPA is so flexible, you will have to derive your connection string from your cluster configuration file (config.yml). You will need the name or IP address of a host with the role pgd-proxy listed for it. This host will have a proxy you can connect to. Usually the proxy will be listening on port 6432 (check the setting for `default_pgd_proxy_options` and `listen_port` in the config to confirm). The default database name is `bdrdb` (check the setting `bdr_database` in the config to confirm) and the default PGD superuser will be `enterprisedb` for EPAS and `postgres` for Postgres and Postgres Extended. +Because TPA is so flexible, you have to derive your connection string from your cluster configuration file (`config.yml`). + +- You need the name or IP address of a host with the role pgd-proxy listed for it. This host has a proxy you can connect to. Usually the proxy listens on port 6432. (Check the setting for `default_pgd_proxy_options` and `listen_port` in the config to confirm.) +- The default database name is `bdrdb`. (Check the setting `bdr_database` in the config to confirm.) +- The default PGD superuser is enterprisedb for EDB Postgres Advanced Server and postgres for Postgres and Postgres Extended. You can then assemble a connection string based on that information: @@ -25,7 +29,7 @@ You can then assemble a connection string based on that information: "host= port= dbname= user= sslmode=require" ``` -To illustrate this, here's some excerpts of a config.yml file for a cluster: +To illustrate this, here are some excerpts of a `config.yml` file for a cluster: ```yaml ... @@ -51,26 +55,34 @@ instances: ... ``` -The connection string for this cluster would be: +The connection string for this cluster is: ``` "host=192.168.100.2 port=6432 dbname=bdrdb user=enterprisedb sslmode=require" ``` !!! Note Host name versus IP address -In our example, we use the IP address because the configuration is from a Docker TPA install with no name resolution available. Generally, you should be able to use the host name as configured. +The example uses the IP address because the configuration is from a Docker TPA install with no name resolution available. Generally, you can use the host name as configured. !!! ### For a BigAnimal distributed high-availability cluster -1. Log into the [BigAnimal Clusters](https://portal.biganimal.com/clusters) view. +1. Log in to the [BigAnimal clusters](https://portal.biganimal.com/clusters) view. 1. Select your cluster. -1. In the view of your cluster, select the Connect tab. -1. Copy the Read/Write URI from the connection info. This is your connection string. +1. In the view of your cluster, select the **Connect** tab. +1. Copy the read/write URI from the connection info. This is your connection string. ### For an EDB PGD for Kubernetes deployed cluster -As with TPA, EDB PGD for Kubernetes is very flexible and there is no one way to obtain a connection string. It depends, in large part, on how the [Services](https://www.enterprisedb.com/docs/postgres_distributed_for_kubernetes/latest/connectivity/#services) have been configured for the deployment. If the Node Service Template is used, there should be direct connectivity to each node and proxy service available. If the Group Service Template, there will be a gateway service to each group. Finally, if the Proxy Service Template has been used, there should be a single proxy providing an entry point to the cluster for all applications. Consult your configuration file to determine this information. You should be able to establish a host name or IP address, port, database name (default: `bdrdb`) and username (`enterprisedb` for EPAS and `postgres` for Postgres and Postgres Extended.). +As with TPA, EDB PGD for Kubernetes is very flexible, and there are multiple ways to obtain a connection string. It depends, in large part, on how the [services](/postgres_distributed_for_kubernetes/latest/connectivity/#services) were configured for the deployment: + +- If you use the Node Service Template, direct connectivity to each node and proxy service is available. +- If you use the Group Service Template, there's a gateway service to each group. +- If you use the Proxy Service Template, a single proxy provides an entry point to the cluster for all applications. + +Consult your configuration file to determine this information. + +Establish a host name or IP address, port, database name, and username. The default database name is `bdrdb`, and the default username is enterprisedb for EDB Postgres Advanced Server and postgres for Postgres and Postgres Extended.). You can then assemble a connection string based on that information: @@ -78,6 +90,6 @@ You can then assemble a connection string based on that information: "host= port= dbname= user=" ``` -You may need to add `sslmode=` if the deployment's configuration requires it. +If the deployment's configuration requires it, add `sslmode=`. diff --git a/product_docs/docs/pgd/5/cli/index.mdx b/product_docs/docs/pgd/5/cli/index.mdx index 443ec13d74e..bf8a00d1b39 100644 --- a/product_docs/docs/pgd/5/cli/index.mdx +++ b/product_docs/docs/pgd/5/cli/index.mdx @@ -13,9 +13,9 @@ directoryDefaults: description: "The PGD Command Line Interface (CLI) is a tool to manage your EDB Postgres Distributed cluster" --- -The EDB Postgres Distributed Command Line Interface (PGD CLI) is a tool for managing your EDB Postgres Distributed cluster. It allows you to run commands against EDB Postgres Distributed clusters. It may be installed automatically on systems within a TPA-deployed PGD cluster or it can be installed manually on systems that can connect to any PGD cluster, including BigAnimal Distributed High Availability PGD clusters or PGD clusters deployed using the EDB PGD for Kubernetes operator. +The EDB Postgres Distributed Command Line Interface (PGD CLI) is a tool for managing your EDB Postgres Distributed cluster. It allows you to run commands against EDB Postgres Distributed clusters. It can be installed automatically on systems in a TPA-deployed PGD cluster. Or it can be installed manually on systems that can connect to any PGD cluster, including BigAnimal distributed high-availability PGD clusters or PGD clusters deployed using the EDB PGD for Kubernetes operator. -See [Installing PGD CLI](installing_cli) for information about how to install PGD CLI, both automatically with Trusted Postgres Architect and manually. +See [Installing PGD CLI](installing_cli) for information about how to install PGD CLI automatically with Trusted Postgres Architect and manually. See [Using PGD CLI](using_cli) for an introduction to using the PGD CLI and connecting to your PGD cluster. @@ -23,5 +23,5 @@ See [Configuring PGD CLI](configuring_cli) for details on creating persistent co See the [Command reference](command_ref) for the available commands to inspect, manage, and get information about cluster resources. -There is also a guide to [discovering connection strings](discover_connections). It shows how to obtain the correct connection strings for your PGD-powered deployment. +See [Discovering connection strings](discover_connections) to learn how to obtain the correct connection strings for your PGD-powered deployment. diff --git a/product_docs/docs/pgd/5/cli/installing_cli.mdx b/product_docs/docs/pgd/5/cli/installing_cli.mdx index 2ec709cf331..c72e436f58b 100644 --- a/product_docs/docs/pgd/5/cli/installing_cli.mdx +++ b/product_docs/docs/pgd/5/cli/installing_cli.mdx @@ -3,14 +3,15 @@ title: "Installing PGD CLI" navTitle: "Installing PGD CLI" --- -PGD CLI can be installed on any system which is able to connect to the PGD cluster. You will require a user with PGD superuser privileges - the [bdr_superuser role](../security) - or equivalent (e.g. edb_admin on BigAnimal distributed high-availability) to use PGD CLI. +You can install PGD CLI on any system that can connect to the PGD cluster. To use PGD CLI, you need a user with PGD superuser privileges or equivalent. The PGD user with superuser privileges is the [bdr_superuser role](../security). An example of an equivalent user is edb_admin on a BigAnimal distributed high-availability cluster. ## Installing automatically with Trusted Postgres Architect (TPA) + By default, Trusted Postgres Architect installs and configures PGD CLI on each PGD node. If you want to install PGD CLI on any non-PGD instance in the cluster, attach the pgdcli role to that instance in Trusted Postgres Architect's configuration file before deploying. See [Trusted Postgres Architect](/tpa/latest/) for more information. ## Installing manually on Linux -PGD CLI is installable from the EDB Repositories. These repositories require a token to enable downloads from them. You will need to login to [EDB Repos 2.0](https://www.enterprisedb.com/repos-downloads) to obtain your token. Then execute the following command, substituting +PGD CLI is installable from the EDB repositories. These repositories require a token to enable downloads from them. Log in to [EDB Repos 2.0](https://www.enterprisedb.com/repos-downloads) to obtain your token. Then execute the command shown for your operating system, substituting your token for ``. ### Add repository and install PGD CLI on Debian or Ubuntu @@ -20,7 +21,7 @@ curl -1sLf 'https://downloads.enterprisedb.com//postgres_distributed sudo apt-get install edb-pgd5-cli ``` -### Add repository and install PGD CLI on RHEL, Rocky, AlmaLinux or Oracle Linux +### Add repository and install PGD CLI on RHEL, Rocky, AlmaLinux, or Oracle Linux ```bash curl -1sLf 'https://downloads.enterprisedb.com//postgres_distributed/setup.rpm.sh' | sudo -E bash @@ -28,5 +29,3 @@ sudo yum install edb-pgd5-cli ``` [Next: Using PGD CLI](using_cli) - - diff --git a/product_docs/docs/pgd/5/cli/using_cli.mdx b/product_docs/docs/pgd/5/cli/using_cli.mdx index 3ea54d77ce3..ee992a9c828 100644 --- a/product_docs/docs/pgd/5/cli/using_cli.mdx +++ b/product_docs/docs/pgd/5/cli/using_cli.mdx @@ -3,27 +3,27 @@ title: "Using PGD CLI" navTitle: "Using PGD CLI" --- -## What is the PGD CLI +## What is the PGD CLI? -The PGD CLI is a convenient way to connect to and manage your PGD cluster. You will need the credentials of a Postgres users with PGD superuser privileges - the [bdr_superuser role](../security) - or equivalent (e.g. edb_admin on BigAnimal distributed high availability) to use it. +The PGD CLI is a convenient way to connect to and manage your PGD cluster. To use it, you need a user with PGD superuser privileges or equivalent. The PGD user with superuser privileges is the [bdr_superuser role](../security). An example of an equivalent user is edb_admin on a BigAnimal distributed high-availability cluster. !!! Important Setting passwords -PGD CLI does not interactively prompt for your user's password. You must pass your password using one of the following methods: +PGD CLI doesn't interactively prompt for your password. You must pass your password using one of the following methods: - 1. Adding an entry to your [`.pgpass` password file](https://www.postgresql.org/docs/current/libpq-pgpass.html) which includes the host, port, database name, user name, and password. - 1. Setting the password in the `PGPASSWORD` environment variable. - 1. Including the password in the connection string. + - Adding an entry to your [`.pgpass` password file](https://www.postgresql.org/docs/current/libpq-pgpass.html), which includes the host, port, database name, user name, and password. + - Setting the password in the `PGPASSWORD` environment variable. + - Including the password in the connection string. -We recommend the first option, as the other options don't scale well with multiple databases or compromise password confidentiality. +We recommend the first option, as the other options don't scale well with multiple databases, or they compromise password confidentiality. !!! ## Running the PGD CLI -Once you have [installed pgd-cli](installing_cli), run the `pgd` command to access the PGD command line interface. The `pgd` command will need details of which host, port, and database to connect to, along with your username and password. +Once you have [installed pgd-cli](installing_cli), run the `pgd` command to access the PGD command line interface. The `pgd` command needs details about the host, port, and database to connect to, along with your username and password. ## Passing a database connection string -Use the `--dsn` flag to pass a database connection string to the `pgd` command. You don't need a configuration file when you pass the connection string with the `--dsn` flag. The flag takes precedence even if a configuration file is present. For example: +Use the `--dsn` flag to pass a database connection string to the `pgd` command. When you pass the connection string with the `--dsn` flag, you don't need a configuration file. The flag takes precedence even if a configuration file is present. For example: ```sh pgd show-nodes --dsn "host=bdr-a1 port=5432 dbname=bdrdb user=enterprisedb" @@ -33,7 +33,7 @@ See [pgd](command_ref) in the command reference for a description of the command ## Specifying a configuration file -If a `pgd-cli-config.yml` file is in `/etc/edb/pgd-cli` or `$HOME/.edb/pgd-cli`, `pgd` will automatically use it. You can override +If a `pgd-cli-config.yml` file is in `/etc/edb/pgd-cli` or `$HOME/.edb/pgd-cli`, `pgd` uses it. You can override this behavior using the optional `-f` or `--config-file` flag. For example: ```sh @@ -75,13 +75,13 @@ pgd show-nodes -o json ] ``` -The PGD CLI supports the following output formats: +The PGD CLI supports the following output formats. | Setting | Format | Considerations | | ------- | ------ | --------- | | none | Tabular | Default format. This setting presents the data in tabular form.| | `json` | JSON | Presents the raw data with no formatting. For some commands, the JSON output might show more data than the tabular output, such as extra fields and more detailed messages. | -| `yaml` | YAML |Similar to the JSON output, but as YAML and with the fields ordered alphabetically. Experimental and may not be fully supported in future versions. | +| `yaml` | YAML | Similar to the JSON output but as YAML and with the fields ordered alphabetically. Experimental and might not be fully supported in future versions. | ## Accessing the command line help From d0761417b640f1dd9be42d019e81ea45997431b6 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 24 Aug 2023 15:47:23 -0400 Subject: [PATCH 074/255] Update discover_connections.mdx --- product_docs/docs/pgd/5/cli/discover_connections.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/cli/discover_connections.mdx b/product_docs/docs/pgd/5/cli/discover_connections.mdx index 84c468b3638..fb4cd2fbbd4 100644 --- a/product_docs/docs/pgd/5/cli/discover_connections.mdx +++ b/product_docs/docs/pgd/5/cli/discover_connections.mdx @@ -72,7 +72,7 @@ The example uses the IP address because the configuration is from a Docker TPA i 1. In the view of your cluster, select the **Connect** tab. 1. Copy the read/write URI from the connection info. This is your connection string. -### For an EDB PGD for Kubernetes deployed cluster +### For a cluster deployed with EDB PGD for Kubernetes As with TPA, EDB PGD for Kubernetes is very flexible, and there are multiple ways to obtain a connection string. It depends, in large part, on how the [services](/postgres_distributed_for_kubernetes/latest/connectivity/#services) were configured for the deployment: From 4feb40e72190750b1e114d1799cfe0ccca9a3ab8 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Fri, 8 Sep 2023 08:50:27 +0100 Subject: [PATCH 075/255] Applying changes as per @kelpoole comments --- product_docs/docs/pgd/5/cli/discover_connections.mdx | 7 ++++--- product_docs/docs/pgd/5/cli/index.mdx | 4 ++-- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/pgd/5/cli/discover_connections.mdx b/product_docs/docs/pgd/5/cli/discover_connections.mdx index fb4cd2fbbd4..ce04e3af495 100644 --- a/product_docs/docs/pgd/5/cli/discover_connections.mdx +++ b/product_docs/docs/pgd/5/cli/discover_connections.mdx @@ -21,7 +21,7 @@ Because TPA is so flexible, you have to derive your connection string from your - You need the name or IP address of a host with the role pgd-proxy listed for it. This host has a proxy you can connect to. Usually the proxy listens on port 6432. (Check the setting for `default_pgd_proxy_options` and `listen_port` in the config to confirm.) - The default database name is `bdrdb`. (Check the setting `bdr_database` in the config to confirm.) -- The default PGD superuser is enterprisedb for EDB Postgres Advanced Server and postgres for Postgres and Postgres Extended. +- The default PGD superuser is `enterprisedb` for EDB Postgres Advanced Server and `postgres` for Postgres and Postgres Extended. You can then assemble a connection string based on that information: @@ -65,9 +65,10 @@ The connection string for this cluster is: The example uses the IP address because the configuration is from a Docker TPA install with no name resolution available. Generally, you can use the host name as configured. !!! -### For a BigAnimal distributed high-availability cluster +### For an EDB BigAnimal Distributed High Availability cluster 1. Log in to the [BigAnimal clusters](https://portal.biganimal.com/clusters) view. +1. In the filter, set the Cluster Type to "Distributed High Availability" to only show clusters which work with PGD CLI. 1. Select your cluster. 1. In the view of your cluster, select the **Connect** tab. 1. Copy the read/write URI from the connection info. This is your connection string. @@ -82,7 +83,7 @@ As with TPA, EDB PGD for Kubernetes is very flexible, and there are multiple way Consult your configuration file to determine this information. -Establish a host name or IP address, port, database name, and username. The default database name is `bdrdb`, and the default username is enterprisedb for EDB Postgres Advanced Server and postgres for Postgres and Postgres Extended.). +Establish a host name or IP address, port, database name, and username. The default database name is `bdrdb`, and the default username is `enterprisedb` for EDB Postgres Advanced Server and `postgres` for Postgres and Postgres Extended.). You can then assemble a connection string based on that information: diff --git a/product_docs/docs/pgd/5/cli/index.mdx b/product_docs/docs/pgd/5/cli/index.mdx index bf8a00d1b39..1b87d879919 100644 --- a/product_docs/docs/pgd/5/cli/index.mdx +++ b/product_docs/docs/pgd/5/cli/index.mdx @@ -13,9 +13,9 @@ directoryDefaults: description: "The PGD Command Line Interface (CLI) is a tool to manage your EDB Postgres Distributed cluster" --- -The EDB Postgres Distributed Command Line Interface (PGD CLI) is a tool for managing your EDB Postgres Distributed cluster. It allows you to run commands against EDB Postgres Distributed clusters. It can be installed automatically on systems in a TPA-deployed PGD cluster. Or it can be installed manually on systems that can connect to any PGD cluster, including BigAnimal distributed high-availability PGD clusters or PGD clusters deployed using the EDB PGD for Kubernetes operator. +The EDB Postgres Distributed Command Line Interface (PGD CLI) is a tool for managing your EDB Postgres Distributed cluster. It allows you to run commands against EDB Postgres Distributed clusters. It is installed automatically on systems in a TPA-deployed PGD cluster. Or it can be installed manually on systems that can connect to any PGD cluster, such as EDB BigAnimal Distributed High Availability clusters or PGD clusters deployed using the EDB PGD for Kubernetes operator. -See [Installing PGD CLI](installing_cli) for information about how to install PGD CLI automatically with Trusted Postgres Architect and manually. +See [Installing PGD CLI](installing_cli) for information about how to manually install PGD CLI on systems. See [Using PGD CLI](using_cli) for an introduction to using the PGD CLI and connecting to your PGD cluster. From 02fee01ef58659969903175bdbd96f98e49efbfd Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Fri, 8 Sep 2023 01:26:20 -0700 Subject: [PATCH 076/255] Update product_docs/docs/pgd/5/cli/discover_connections.mdx Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> --- product_docs/docs/pgd/5/cli/discover_connections.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/cli/discover_connections.mdx b/product_docs/docs/pgd/5/cli/discover_connections.mdx index ce04e3af495..5a24b8a63e9 100644 --- a/product_docs/docs/pgd/5/cli/discover_connections.mdx +++ b/product_docs/docs/pgd/5/cli/discover_connections.mdx @@ -5,7 +5,7 @@ indexdepth: 2 deepToC: true --- -You can install PGD CLI on any system that can connect to the PGD cluster. To use PGD CLI, you need a user with PGD superuser privileges or equivalent. The PGD user with superuser privileges is the [bdr_superuser role](../security). An example of an equivalent user is edb_admin on a BigAnimal distributed high-availability cluster. +You can install PGD CLI on any system that can connect to the PGD cluster. To use PGD CLI, you need a user with PGD superuser privileges or equivalent. The PGD user with superuser privileges is the [bdr_superuser role](../security). An example of an equivalent user is `edb_admin` on an EDB BigAnimal Distributed High Availability cluster. ## PGD CLI and database connection strings From 8112ae5025ac813634ea6ebb63a29d80c7c2ee22 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Fri, 8 Sep 2023 10:55:34 +0100 Subject: [PATCH 077/255] Update product_docs/docs/efm/4/13_troubleshooting.mdx --- product_docs/docs/efm/4/13_troubleshooting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/efm/4/13_troubleshooting.mdx b/product_docs/docs/efm/4/13_troubleshooting.mdx index ff558cdb8bc..1652ac10269 100644 --- a/product_docs/docs/efm/4/13_troubleshooting.mdx +++ b/product_docs/docs/efm/4/13_troubleshooting.mdx @@ -52,4 +52,4 @@ OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode) `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, e.g. `dnf install tzdata-java` + If so, the workaround is to manually install the missing package using the command `sudo dnf install tzdata-java` From 85f19c018b5c2c13c6fd83400e825e56ec349b0f Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Fri, 8 Sep 2023 10:55:43 +0100 Subject: [PATCH 078/255] Update product_docs/docs/efm/4/installing/prerequisites.mdx --- product_docs/docs/efm/4/installing/prerequisites.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/efm/4/installing/prerequisites.mdx b/product_docs/docs/efm/4/installing/prerequisites.mdx index b4dc1bac48f..8b74021e55c 100644 --- a/product_docs/docs/efm/4/installing/prerequisites.mdx +++ b/product_docs/docs/efm/4/installing/prerequisites.mdx @@ -22,7 +22,7 @@ Before using Failover Manager, you must first install Java (version 1.8 or later `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, e.g. `dnf install tzdata-java` + If so, the workaround is to manually install the missing package using the command `sudo dnf install tzdata-java` ## Provide an SMTP server From 49497d5ac592ac1ebfc294bfbe1607c66a83e6a9 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Fri, 8 Sep 2023 06:29:56 -0400 Subject: [PATCH 079/255] minor copyedits --- product_docs/docs/efm/4/05_using_efm.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/efm/4/05_using_efm.mdx b/product_docs/docs/efm/4/05_using_efm.mdx index 0ade30d911d..6a7c7601131 100644 --- a/product_docs/docs/efm/4/05_using_efm.mdx +++ b/product_docs/docs/efm/4/05_using_efm.mdx @@ -267,7 +267,7 @@ After creating the `acctg.properties` and `sales.properties` files, create a ser 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..service` to `/etc/systemd/system` with a new name that is unique for each cluster. -For example, if you have two clusters named `acctg` and `sales` managed by EFM 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`, and they can be created with: ```shell cp /usr/lib/systemd/system/edb-efm-4.7.service /etc/systemd/system/efm-acctg.service @@ -293,7 +293,9 @@ Environment=CLUSTER=sales 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. +!!!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. +!!! After saving the changes, enable the services: From 3bc5ed95126f3b133350de5855ba1a8822dc7ba2 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Fri, 8 Sep 2023 09:59:46 +0100 Subject: [PATCH 080/255] Fixed bad lists (line break in earlier line) Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/limitations.mdx | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/product_docs/docs/pgd/5/limitations.mdx b/product_docs/docs/pgd/5/limitations.mdx index 87c3db87415..e89f4faccfa 100644 --- a/product_docs/docs/pgd/5/limitations.mdx +++ b/product_docs/docs/pgd/5/limitations.mdx @@ -108,22 +108,20 @@ Be sure to disable transaction streaming when planning to use CAMO. You can configure this option globally or in the PGD node group. See [Transaction streaming configuration](../transaction-streaming#configuration). -- Not all DDL can run when CAMO is used. If unsupported DDL is used a warning is logged -and the transactions commit scope is set to local only. The only supported DDL operations are: - - non-concurrent CREATE INDEX - - non-concurrent DROP INDEX - - non-concurrent REINDEX of an individual table or index - - CLUSTER (of a single relation or index only) - - ANALYZE - - TRUNCATE +- Not all DDL can run when CAMO is used. If unsupported DDL is used a warning is logged and the transactions commit scope is set to local only. The only supported DDL operations are: + - non-concurrent `CREATE INDEX` + - non-concurrent `DROP INDEX` + - non-concurrent `REINDEX` of an individual table or index + - `CLUSTER` (of a single relation or index only) + - `ANALYZE` + - `TRUNCATE` ## Group Commit [Group Commit](durability/group-commit) is a feature which enables configurable synchronous commits over nodes in a group. If you use this feature, take the following limitations into account: -- Not all DDL can run when Group Commit is used. If unsupported DDL is used a warning is logged -and the transactions commit scope is set to local only. The only supported DDL operations are: +- Not all DDL can run when Group Commit is used. If unsupported DDL is used a warning is logged and the transactions commit scope is set to local only. The only supported DDL operations are: - non-concurrent CREATE INDEX - non-concurrent DROP INDEX - non-concurrent REINDEX of an individual table or index From 39b00221af63a3e263fc2e6d1d90bd64a7fde797 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Fri, 8 Sep 2023 10:00:29 +0100 Subject: [PATCH 081/255] Added backticks Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/limitations.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/pgd/5/limitations.mdx b/product_docs/docs/pgd/5/limitations.mdx index e89f4faccfa..2ef3dc96b64 100644 --- a/product_docs/docs/pgd/5/limitations.mdx +++ b/product_docs/docs/pgd/5/limitations.mdx @@ -122,12 +122,12 @@ CAMO. You can configure this option globally or in the PGD node group. See nodes in a group. If you use this feature, take the following limitations into account: - Not all DDL can run when Group Commit is used. If unsupported DDL is used a warning is logged and the transactions commit scope is set to local only. The only supported DDL operations are: - - non-concurrent CREATE INDEX - - non-concurrent DROP INDEX - - non-concurrent REINDEX of an individual table or index - - CLUSTER (of a single relation or index only) - - ANALYZE - - TRUNCATE + - non-concurrent `CREATE INDEX` + - non-concurrent `DROP INDEX` + - non-concurrent `REINDEX` of an individual table or index + - `CLUSTER` (of a single relation or index only) + - `ANALYZE` + - `TRUNCATE` ## Eager From 1c6baff06105b6749b9169494f4119321c1cc6ea Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Fri, 8 Sep 2023 11:23:36 +0100 Subject: [PATCH 082/255] Update product_docs/docs/pgd/5/limitations.mdx Co-authored-by: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> --- product_docs/docs/pgd/5/limitations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/limitations.mdx b/product_docs/docs/pgd/5/limitations.mdx index 2ef3dc96b64..6468f04f77f 100644 --- a/product_docs/docs/pgd/5/limitations.mdx +++ b/product_docs/docs/pgd/5/limitations.mdx @@ -108,7 +108,7 @@ Be sure to disable transaction streaming when planning to use CAMO. You can configure this option globally or in the PGD node group. See [Transaction streaming configuration](../transaction-streaming#configuration). -- Not all DDL can run when CAMO is used. If unsupported DDL is used a warning is logged and the transactions commit scope is set to local only. The only supported DDL operations are: +- Not all DDL can run when you use CAMO. If you use unsupported DDL, a warning is logged and the transactions commit scope is set to local only. The only supported DDL operations are: - non-concurrent `CREATE INDEX` - non-concurrent `DROP INDEX` - non-concurrent `REINDEX` of an individual table or index From 264203c80e79f523d283ac11982920909e78cdba Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Fri, 8 Sep 2023 11:23:45 +0100 Subject: [PATCH 083/255] Update product_docs/docs/pgd/5/limitations.mdx Co-authored-by: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> --- product_docs/docs/pgd/5/limitations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/limitations.mdx b/product_docs/docs/pgd/5/limitations.mdx index 6468f04f77f..2ea6a437a25 100644 --- a/product_docs/docs/pgd/5/limitations.mdx +++ b/product_docs/docs/pgd/5/limitations.mdx @@ -121,7 +121,7 @@ CAMO. You can configure this option globally or in the PGD node group. See [Group Commit](durability/group-commit) is a feature which enables configurable synchronous commits over nodes in a group. If you use this feature, take the following limitations into account: -- Not all DDL can run when Group Commit is used. If unsupported DDL is used a warning is logged and the transactions commit scope is set to local only. The only supported DDL operations are: +- Not all DDL can run when you use Group Commit. If you use unsupported DDL, a warning is logged and the transactions commit scope is set to local. The only supported DDL operations are: - non-concurrent `CREATE INDEX` - non-concurrent `DROP INDEX` - non-concurrent `REINDEX` of an individual table or index From da21b4afe06212db6966a30d31197d1ea6243256 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 31 Aug 2023 14:06:29 -0400 Subject: [PATCH 084/255] PostgreSQL: Mac uninstall --- .../postgresql/uninstalling.mdx | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx b/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx index c48f49210f6..a127af90d75 100644 --- 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,15 +52,21 @@ 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: +1. Assume the identity of an operating system superuser. - `/Library/PostgreSQL/` +1. Navigate into the folder where the uninstaller resides: - Where `version` is the version of PostgreSQL you installed. + ``` + cd /Library/PostgreSQL/ + ``` + + Where `version` is the version of PostgreSQL you installed. 1. Invoke the uninstaller: - `open uninstall-postgresql.app` + ``` + open uninstall-postgresql.app + ``` 1. If prompted, provide a password that allows the uninstaller to make changes to your system. From 83a23d10d5f4151e95a915dbac46fabd14ea1f89 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 6 Sep 2023 10:18:25 -0400 Subject: [PATCH 085/255] updating the command for MacOS --- .../postgresql/uninstalling.mdx | 14 +++----------- 1 file changed, 3 insertions(+), 11 deletions(-) diff --git a/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx b/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx index a127af90d75..4a8b999ac8a 100644 --- a/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx +++ b/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx @@ -52,22 +52,14 @@ 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. - -1. Navigate into the folder where the uninstaller resides: - - ``` - cd /Library/PostgreSQL/ - ``` - - Where `version` is the version of PostgreSQL you installed. - 1. Invoke the uninstaller: ``` - open uninstall-postgresql.app + sudo /Library/PostgreSQL//uninstall-postgresql.app/Contents/MacOS/installbuilder.sh ``` + Where `` is the version of PostgreSQL you installed. + 1. If prompted, provide a password that allows the uninstaller to make changes to your system. The uninstaller opens and asks if you want to uninstall the entire application or individual components. From cf383cfa61c90f6ac569aac23b84ae7d75c3804d Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 8 Sep 2023 08:24:11 -0400 Subject: [PATCH 086/255] incorporated Dj's comments --- .../supported-open-source/postgresql/uninstalling.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx b/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx index 4a8b999ac8a..865f095d106 100644 --- a/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx +++ b/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx @@ -55,12 +55,12 @@ To uninstall PostgreSQL on a Mac system: 1. Invoke the uninstaller: ``` - sudo /Library/PostgreSQL//uninstall-postgresql.app/Contents/MacOS/installbuilder.sh + open /Library/PostgreSQL//uninstall-postgresql.app/Contents/MacOS/installbuilder.sh ``` Where `` 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. From 4980cdba7fb4ebb30251eb91ac2c1e06c3aa793e Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Fri, 8 Sep 2023 14:52:00 +0100 Subject: [PATCH 087/255] Update advocacy_docs/supported-open-source/postgresql/uninstalling.mdx --- advocacy_docs/supported-open-source/postgresql/uninstalling.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx b/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx index 865f095d106..df6b223a12f 100644 --- a/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx +++ b/advocacy_docs/supported-open-source/postgresql/uninstalling.mdx @@ -55,7 +55,7 @@ To uninstall PostgreSQL on a Mac system: 1. Invoke the uninstaller: ``` - open /Library/PostgreSQL//uninstall-postgresql.app/Contents/MacOS/installbuilder.sh + open /Library/PostgreSQL//uninstall-postgresql.app ``` Where `` is the version of PostgreSQL you installed. From 0eedc8ee30f8b85dc202b91fce812590b682266b Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 8 Sep 2023 10:05:27 -0400 Subject: [PATCH 088/255] BigAnimal: pricing fix --- .../docs/biganimal/release/pricing_and_billing/index.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx b/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx index ffc41414e80..29b6ab62547 100644 --- a/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx +++ b/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx @@ -30,8 +30,8 @@ This table shows the cost breakdown. | Database type | Hourly price | Monthly price\* | | ---------------------------- | -------------- | --------------- | -| EDB Postgres Extended Server | $0.2511 / vCPU | $188.33 / vCPU | -| EDB Postgres Advanced Server | $0.3424 / vCPU | $256.80 / vCPU | +| EDB Postgres Extended Server | $0.2511 / vCPU | $183.30 / vCPU | +| EDB Postgres Advanced Server | $0.3424 / vCPU | $249.95 / vCPU | \* The monthly cost is approximate and assumes 730 hours in a month. From bc7296a99a2b928cfcba768a9fed96fe2c0d6f84 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 8 Sep 2023 10:56:45 -0400 Subject: [PATCH 089/255] edits to limitations --- product_docs/docs/pgd/5/limitations.mdx | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/product_docs/docs/pgd/5/limitations.mdx b/product_docs/docs/pgd/5/limitations.mdx index 2ea6a437a25..4e9690d6c4b 100644 --- a/product_docs/docs/pgd/5/limitations.mdx +++ b/product_docs/docs/pgd/5/limitations.mdx @@ -109,29 +109,29 @@ CAMO. You can configure this option globally or in the PGD node group. See [Transaction streaming configuration](../transaction-streaming#configuration). - Not all DDL can run when you use CAMO. If you use unsupported DDL, a warning is logged and the transactions commit scope is set to local only. The only supported DDL operations are: - - non-concurrent `CREATE INDEX` - - non-concurrent `DROP INDEX` - - non-concurrent `REINDEX` of an individual table or index + - Nonconcurrent `CREATE INDEX` + - Nonconcurrent `DROP INDEX` + - Nonconcurrent `REINDEX` of an individual table or index - `CLUSTER` (of a single relation or index only) - `ANALYZE` - `TRUNCATE` ## Group Commit -[Group Commit](durability/group-commit) is a feature which enables configurable synchronous commits over +[Group Commit](durability/group-commit) enables configurable synchronous commits over nodes in a group. If you use this feature, take the following limitations into account: -- Not all DDL can run when you use Group Commit. If you use unsupported DDL, a warning is logged and the transactions commit scope is set to local. The only supported DDL operations are: - - non-concurrent `CREATE INDEX` - - non-concurrent `DROP INDEX` - - non-concurrent `REINDEX` of an individual table or index +- Not all DDL can run when you use Group Commit. If you use unsupported DDL, a warning is logged, and the transactions commit scope is set to local. The only supported DDL operations are: + - Nonconcurrent `CREATE INDEX` + - Nonconcurrent `DROP INDEX` + - Nonconcurrent `REINDEX` of an individual table or index - `CLUSTER` (of a single relation or index only) - `ANALYZE` - `TRUNCATE` ## Eager -[Eager](consistency/eager) is a feature which is available in Group Commit which enables conflicts to be avoided by eagerly aborting transactions that may clash. It is subject to the same limitations as Group Commit. +[Eager](consistency/eager) is available in Group Commit. It avoids conflicts by eagerly aborting transactions that might clash. It's subject to the same limitations as Group Commit. ## Other limitations From 60808c5e157f781719b1b5bef791b5c2eb3b58e8 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 8 Sep 2023 11:18:58 -0400 Subject: [PATCH 090/255] edits to repli server pr 4705 --- .../03_certified_supported_versions.mdx | 2 +- .../03_xdb_cli_commands/52_reload_conf_file.mdx | 2 +- .../01_controlling_logging_level.mdx | 2 +- .../7/eprs_rel_notes/eprs_rel_notes_7.6.0.mdx | 16 ++++++++-------- 4 files changed, 11 insertions(+), 11 deletions(-) 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 index 6c6cefbddc8..4a239de10d4 100644 --- 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 index a95c78c6c34..a7a1088dba7 100644 --- 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/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx index 90931a7714a..3a3889145af 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_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 index b9db5af9199..184dded1bb5 100644 --- 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. | From 3124a5bb3b8c076036dd59fb1b8f6c98b3d022f5 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 8 Sep 2023 11:27:45 -0400 Subject: [PATCH 091/255] small edit to biganimal pr4680 Grammatical issue --- .../docs/biganimal/release/reference/cli/managing_clusters.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx index 2707e232191..5824256b13f 100644 --- 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 From 349af1ca0cf18ca56e7d804f4a077751a392b69a Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Thu, 7 Sep 2023 21:12:41 -0700 Subject: [PATCH 092/255] Updated index to align to CNPG and move things out of Enhanced --- .../docs/postgres_for_kubernetes/1/index.mdx | 27 +++++++++++-------- 1 file changed, 16 insertions(+), 11 deletions(-) diff --git a/product_docs/docs/postgres_for_kubernetes/1/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/index.mdx index 523dbc4964d..3205201a371 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/index.mdx @@ -21,8 +21,8 @@ navigation: - samples - '#Using' - bootstrap - - security - database_import + - security - instance_manager - scheduling - resource_management @@ -30,6 +30,7 @@ navigation: - rolling_update - replication - backup_recovery + - declarative_role_management - storage - labels_annotations - monitoring @@ -41,21 +42,25 @@ navigation: - replica_cluster - kubernetes_upgrade - expose_pg_services - - troubleshooting - - fencing + - kubectl-plugin - failover - - e2e + - fencing + - declarative_hibernation + - postgis - container_images + - controller + - networking + - benchmarking + - '#EDB Enhancements' + - evaluation + - license_keys + - openshift + - tde + - '#Reference' - operator_capability_levels - - commercial_support - faq - - wait_for_apply_queue + - troubleshooting - api_reference - - '#Enhanced' - - cnp-plugin - - openshift - - evaluation - - license_keys --- From 30abbd491883199dafd06ab26b0d1e91429d8df2 Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Thu, 7 Sep 2023 21:40:53 -0700 Subject: [PATCH 093/255] Update index.mdx --- product_docs/docs/postgres_for_kubernetes/1/index.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/product_docs/docs/postgres_for_kubernetes/1/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/index.mdx index 3205201a371..554cedde64e 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/index.mdx @@ -18,6 +18,7 @@ navigation: - '#Configuration' - postgresql_conf - operator_conf + - cluster_conf - samples - '#Using' - bootstrap @@ -56,6 +57,7 @@ navigation: - license_keys - openshift - tde + - addons - '#Reference' - operator_capability_levels - faq From e2327fe2f0449570cfd6d169913ec9ec99525ac1 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 8 Sep 2023 11:49:28 -0400 Subject: [PATCH 094/255] Edits to PGD edits in PR 4688 --- product_docs/docs/pgd/5/cli/discover_connections.mdx | 10 +++++----- product_docs/docs/pgd/5/cli/index.mdx | 2 +- product_docs/docs/pgd/5/cli/installing_cli.mdx | 2 +- product_docs/docs/pgd/5/cli/using_cli.mdx | 2 +- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/product_docs/docs/pgd/5/cli/discover_connections.mdx b/product_docs/docs/pgd/5/cli/discover_connections.mdx index 5a24b8a63e9..61f29ac0a4b 100644 --- a/product_docs/docs/pgd/5/cli/discover_connections.mdx +++ b/product_docs/docs/pgd/5/cli/discover_connections.mdx @@ -5,7 +5,7 @@ indexdepth: 2 deepToC: true --- -You can install PGD CLI on any system that can connect to the PGD cluster. To use PGD CLI, you need a user with PGD superuser privileges or equivalent. The PGD user with superuser privileges is the [bdr_superuser role](../security). An example of an equivalent user is `edb_admin` on an EDB BigAnimal Distributed High Availability cluster. +You can install PGD CLI on any system that can connect to the PGD cluster. To use PGD CLI, you need a user with PGD superuser privileges or equivalent. The PGD user with superuser privileges is the [bdr_superuser role](../security). An example of an equivalent user is edb_admin on an EDB BigAnimal distributed high-availability cluster. ## PGD CLI and database connection strings @@ -21,7 +21,7 @@ Because TPA is so flexible, you have to derive your connection string from your - You need the name or IP address of a host with the role pgd-proxy listed for it. This host has a proxy you can connect to. Usually the proxy listens on port 6432. (Check the setting for `default_pgd_proxy_options` and `listen_port` in the config to confirm.) - The default database name is `bdrdb`. (Check the setting `bdr_database` in the config to confirm.) -- The default PGD superuser is `enterprisedb` for EDB Postgres Advanced Server and `postgres` for Postgres and Postgres Extended. +- The default PGD superuser is enterprisedb for EDB Postgres Advanced Server and postgres for Postgres and Postgres Extended. You can then assemble a connection string based on that information: @@ -65,10 +65,10 @@ The connection string for this cluster is: The example uses the IP address because the configuration is from a Docker TPA install with no name resolution available. Generally, you can use the host name as configured. !!! -### For an EDB BigAnimal Distributed High Availability cluster +### For an EDB BigAnimal distributed high-availability cluster 1. Log in to the [BigAnimal clusters](https://portal.biganimal.com/clusters) view. -1. In the filter, set the Cluster Type to "Distributed High Availability" to only show clusters which work with PGD CLI. +1. In the filter, set **Cluster Type** to **Distributed High Availability** to show only clusters that work with PGD CLI. 1. Select your cluster. 1. In the view of your cluster, select the **Connect** tab. 1. Copy the read/write URI from the connection info. This is your connection string. @@ -83,7 +83,7 @@ As with TPA, EDB PGD for Kubernetes is very flexible, and there are multiple way Consult your configuration file to determine this information. -Establish a host name or IP address, port, database name, and username. The default database name is `bdrdb`, and the default username is `enterprisedb` for EDB Postgres Advanced Server and `postgres` for Postgres and Postgres Extended.). +Establish a host name or IP address, port, database name, and username. The default database name is `bdrdb`, and the default username is enterprisedb for EDB Postgres Advanced Server and postgres for Postgres and Postgres Extended.). You can then assemble a connection string based on that information: diff --git a/product_docs/docs/pgd/5/cli/index.mdx b/product_docs/docs/pgd/5/cli/index.mdx index 1b87d879919..66a60be0b08 100644 --- a/product_docs/docs/pgd/5/cli/index.mdx +++ b/product_docs/docs/pgd/5/cli/index.mdx @@ -13,7 +13,7 @@ directoryDefaults: description: "The PGD Command Line Interface (CLI) is a tool to manage your EDB Postgres Distributed cluster" --- -The EDB Postgres Distributed Command Line Interface (PGD CLI) is a tool for managing your EDB Postgres Distributed cluster. It allows you to run commands against EDB Postgres Distributed clusters. It is installed automatically on systems in a TPA-deployed PGD cluster. Or it can be installed manually on systems that can connect to any PGD cluster, such as EDB BigAnimal Distributed High Availability clusters or PGD clusters deployed using the EDB PGD for Kubernetes operator. +The EDB Postgres Distributed Command Line Interface (PGD CLI) is a tool for managing your EDB Postgres Distributed cluster. It allows you to run commands against EDB Postgres Distributed clusters. It's installed automatically on systems in a TPA-deployed PGD cluster. Or it can be installed manually on systems that can connect to any PGD cluster, such as EDB BigAnimal distributed high-availability clusters or PGD clusters deployed using the EDB PGD for Kubernetes operator. See [Installing PGD CLI](installing_cli) for information about how to manually install PGD CLI on systems. diff --git a/product_docs/docs/pgd/5/cli/installing_cli.mdx b/product_docs/docs/pgd/5/cli/installing_cli.mdx index c72e436f58b..5c4b442e9bf 100644 --- a/product_docs/docs/pgd/5/cli/installing_cli.mdx +++ b/product_docs/docs/pgd/5/cli/installing_cli.mdx @@ -3,7 +3,7 @@ title: "Installing PGD CLI" navTitle: "Installing PGD CLI" --- -You can install PGD CLI on any system that can connect to the PGD cluster. To use PGD CLI, you need a user with PGD superuser privileges or equivalent. The PGD user with superuser privileges is the [bdr_superuser role](../security). An example of an equivalent user is edb_admin on a BigAnimal distributed high-availability cluster. +You can install PGD CLI on any system that can connect to the PGD cluster. To use PGD CLI, you need a user with PGD superuser privileges or equivalent. The PGD user with superuser privileges is the [bdr_superuser role](../security). An example of an equivalent user is edb_admin on an EDB BigAnimal distributed high-availability cluster. ## Installing automatically with Trusted Postgres Architect (TPA) diff --git a/product_docs/docs/pgd/5/cli/using_cli.mdx b/product_docs/docs/pgd/5/cli/using_cli.mdx index ee992a9c828..fa1c89e3c71 100644 --- a/product_docs/docs/pgd/5/cli/using_cli.mdx +++ b/product_docs/docs/pgd/5/cli/using_cli.mdx @@ -5,7 +5,7 @@ navTitle: "Using PGD CLI" ## What is the PGD CLI? -The PGD CLI is a convenient way to connect to and manage your PGD cluster. To use it, you need a user with PGD superuser privileges or equivalent. The PGD user with superuser privileges is the [bdr_superuser role](../security). An example of an equivalent user is edb_admin on a BigAnimal distributed high-availability cluster. +The PGD CLI is a convenient way to connect to and manage your PGD cluster. To use it, you need a user with PGD superuser privileges or equivalent. The PGD user with superuser privileges is the [bdr_superuser role](../security). An example of an equivalent user is edb_admin on an EDB BigAnimal distributed high-availability cluster. !!! Important Setting passwords PGD CLI doesn't interactively prompt for your password. You must pass your password using one of the following methods: From c5d927bc2ecc1f57da50a2e1ad8208a5f288f5df Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 8 Sep 2023 12:03:55 -0400 Subject: [PATCH 095/255] PostgreSQL: fix link to language pack doc --- advocacy_docs/supported-open-source/postgresql/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/supported-open-source/postgresql/overview.mdx b/advocacy_docs/supported-open-source/postgresql/overview.mdx index 961a9964e12..71f7dcac37c 100644 --- 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/). From 49e8eaad23a1a348d0585f9c53618fbd9782a3c8 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 8 Sep 2023 12:07:08 -0400 Subject: [PATCH 096/255] Edits to efm PR4788 --- product_docs/docs/efm/4/05_using_efm.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/efm/4/05_using_efm.mdx b/product_docs/docs/efm/4/05_using_efm.mdx index 6a7c7601131..e12d056f786 100644 --- 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
` @@ -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..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..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,7 +277,7 @@ 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] @@ -285,7 +285,7 @@ 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: From f2470c11b64ad89d6625321d3e3bb832e86b623f Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 8 Sep 2023 12:14:45 -0400 Subject: [PATCH 097/255] minor edits to efm pr4520 --- product_docs/docs/efm/4/13_troubleshooting.mdx | 4 ++-- product_docs/docs/efm/4/installing/prerequisites.mdx | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/efm/4/13_troubleshooting.mdx b/product_docs/docs/efm/4/13_troubleshooting.mdx index 1652ac10269..b7242de3b7c 100644 --- 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 index 8b74021e55c..a4206bac8c0 100644 --- 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 From 6698ab52788cdf1153f47b00be2a048ec1b5b244 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 8 Sep 2023 13:09:44 -0400 Subject: [PATCH 098/255] Update index.mdx --- .../7/installing/upgrading_replication_server/index.mdx | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx index f0e949a0905..30d71015fa9 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx @@ -12,12 +12,17 @@ You can install Replication Server 7 when you have existing single-master or mul It is assumed that you are installing Replication Server 7.x on the same host machine that is currently running the earlier version of Replication Server you are upgrading from and that you will then manage the existing replication systems using Replication Server 7.x. -If you are using a version of Replication Server earlier than 6.2.x on Linux, first upgrade to 6.2.x, and then upgrade to version 7.x. See: -- [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package) +If you are using a version of Replication Server earlier than 6.2.15, first upgrade to 6.2.15 or a later 6.2.x point version before upgrading to 7.x. + +!!!note + Version 7.x provides a non-breaking upgrade path for existing 6.2.x based cluster deployments; however, we strongly recommended that you verify the upgrade in a staging or nonproduction environment before applying the upgrade in a production environment. There is no downgrade path from version 7.x to version 6.2.x so it is essential to test the upgrade first before applying it to the production environment. + + For more details on upgrading Replication Server, see: - [Updating the publication and subscription server](updating_sub_and_pub_ports) +- [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package) - [Upgrading from a Replication Server 7.x installation on Linux](upgrading_linux) - [Upgrading with the graphical user interface installer](upgrading_with_gui_installer) From da9867d73dc7f95a47e4c283ad4254e48d2df87b Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Fri, 8 Sep 2023 13:35:51 -0400 Subject: [PATCH 099/255] changed to proper product names --- product_docs/docs/pgd/5/cli/discover_connections.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/cli/discover_connections.mdx b/product_docs/docs/pgd/5/cli/discover_connections.mdx index 61f29ac0a4b..54670cf50a4 100644 --- a/product_docs/docs/pgd/5/cli/discover_connections.mdx +++ b/product_docs/docs/pgd/5/cli/discover_connections.mdx @@ -21,7 +21,7 @@ Because TPA is so flexible, you have to derive your connection string from your - You need the name or IP address of a host with the role pgd-proxy listed for it. This host has a proxy you can connect to. Usually the proxy listens on port 6432. (Check the setting for `default_pgd_proxy_options` and `listen_port` in the config to confirm.) - The default database name is `bdrdb`. (Check the setting `bdr_database` in the config to confirm.) -- The default PGD superuser is enterprisedb for EDB Postgres Advanced Server and postgres for Postgres and Postgres Extended. +- The default PGD superuser is enterprisedb for EDB Postgres Advanced Server and postgres for PostgreSQL and EDB Postgres Extended Server. You can then assemble a connection string based on that information: From 93e0e5a968469e772a430412dea402de257502bb Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Fri, 8 Sep 2023 13:36:16 -0400 Subject: [PATCH 100/255] changed to proper product names --- product_docs/docs/pgd/5/cli/discover_connections.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/cli/discover_connections.mdx b/product_docs/docs/pgd/5/cli/discover_connections.mdx index 54670cf50a4..04e2a3689d8 100644 --- a/product_docs/docs/pgd/5/cli/discover_connections.mdx +++ b/product_docs/docs/pgd/5/cli/discover_connections.mdx @@ -83,7 +83,7 @@ As with TPA, EDB PGD for Kubernetes is very flexible, and there are multiple way Consult your configuration file to determine this information. -Establish a host name or IP address, port, database name, and username. The default database name is `bdrdb`, and the default username is enterprisedb for EDB Postgres Advanced Server and postgres for Postgres and Postgres Extended.). +Establish a host name or IP address, port, database name, and username. The default database name is `bdrdb`, and the default username is enterprisedb for EDB Postgres Advanced Server and postgres for PostgreSQL and EDB Postgres Extended Server. You can then assemble a connection string based on that information: From 81c0b89e17403510e70bb6251183854b79e4f4d7 Mon Sep 17 00:00:00 2001 From: jkitchens32 Date: Fri, 8 Sep 2023 15:49:29 -0400 Subject: [PATCH 101/255] Punctuation Edit --- .../partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx index 665df53f8ea..0f9ea225747 100644 --- a/advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx @@ -11,7 +11,7 @@ When you have configured your Kubernetes environment per the `Configuring` secti 2. Use Kasten K10 to launch a backup that creates two restore points, a local and a remote. -3. You now have a backup we can use to validate a restore in the next section +3. You now have a backup we can use to validate a restore in the next section. ![Launch a Backup](Images/LaunchaBackup.png) From 5765738107e0b6475ea653f36b8da0aa81e6d74b Mon Sep 17 00:00:00 2001 From: Arthur Nascimento Date: Fri, 8 Sep 2023 19:25:44 -0300 Subject: [PATCH 102/255] pg_extensions/ASP/using: improve examples The example for refdata was improved to show the different locking pattern that replaces the row locks for a table lock, leading to a stronger lock when the reference table is changed, but a lower overhead when the referenced rows are accessed. The demonstration uses pgrowlocks, which is available for heap, and will be available in a future version of our custom TAMs. The example for autocluster was maintained. The advanced example that uses both TAMs was improved to show the effect that autocluster has on the query plan, leading to fewer pages touched. Previously it showed the ctid of the rows, but that is already displayed in the autocluster example, so showing the different query plans fills a gap in the overall explanation of autocluster. The examples were reworked to not need external data, through the usage of artificial data generated on the fly. --- .../advanced_storage_pack/using.mdx | 293 ++++++++++++------ 1 file changed, 192 insertions(+), 101 deletions(-) diff --git a/advocacy_docs/pg_extensions/advanced_storage_pack/using.mdx b/advocacy_docs/pg_extensions/advanced_storage_pack/using.mdx index bf377e4df00..e97f24674aa 100644 --- a/advocacy_docs/pg_extensions/advanced_storage_pack/using.mdx +++ b/advocacy_docs/pg_extensions/advanced_storage_pack/using.mdx @@ -3,20 +3,119 @@ title: Using EDB Advanced Storage Pack navTitle: Using --- -The following are scenarios where the EDB Advances Storage Pack TAMs are useful. +The following are scenarios where the EDB Advanced Storage Pack TAMs are useful. ## Refdata example -A scenario where Refdata is useful is when creating a reference table of all the New York Stock Exchange (NYSE) stock symbols and their corporate names. This data is expected to change very rarely and be referenced frequently from a table tracking all stock trades for the entire market (like in the [Advanced Autocluster example](#advanced-autocluster-example)). You can use Refdata instead of heap to increase performance. +A scenario where Refdata is useful is when creating a reference table of all +the New York Stock Exchange (NYSE) stock symbols and their corporate names. +This data is expected to change very rarely and be referenced frequently from a +table tracking all stock trades for the entire market. + +Consider the following two tables: + +```sql +CREATE TABLE nyse_symbol ( + nyse_symbol_id INTEGER PRIMARY KEY GENERATED ALWAYS AS IDENTITY, + symbol TEXT NOT NULL, + name TEXT NOT NULL +); + +CREATE TABLE nyse_trade ( + nyse_symbol_id INTEGER NOT NULL REFERENCES nyse_symbol(nyse_symbol_id), + trade_time TIMESTAMPTZ NOT NULL DEFAULT NOW(), + trade_price FLOAT8 NOT NULL CHECK(trade_price >= 0.0), + trade_volume BIGINT NOT NULL CHECK(trade_volume >= 1) +); + +CREATE INDEX ON nyse_trade USING BTREE(nyse_symbol_id); +``` + +When `heap` is used for `nyse_symbol`, manipulating rows in `nyse_trade` causes +row locks to be created in `nyse_symbol`, but only row locks are used in +`nyse_symbol`: + +```sql +=# BEGIN; +BEGIN +=*# +=*# INSERT INTO nyse_symbol (symbol, name) +-*# VALUES ('A', 'A'); +INSERT 0 1 +=*# +=*# SELECT locktype, mode FROM pg_locks +-*# WHERE relation = 'nyse_symbol'::regclass; + locktype | mode +----------+------------------ + relation | RowExclusiveLock +(1 row) +=*# +=*# COMMIT; +COMMIT +=# +=# BEGIN; +BEGIN +=*# -- insert data into a table that has a foreign key to nyse_symbol +=*# INSERT INTO nyse_trade (nyse_symbol_id, trade_price, trade_volume) +-*# VALUES (1, 1, 1); +INSERT 0 1 +=*# +=*# -- display the row locks in nyse_symbol +=*# SELECT * FROM pgrowlocks('nyse_symbol'); +-[ RECORD 1 ]----------------- +locked_row | (0,1) +locker | 778 +multi | f +xids | {778} +modes | {"For Key Share"} +pids | {21480} +=*# +``` + +However, when `refdata` is used for `nyse_symbol`, the locking pattern changes. The table is created with the `USING refdata` clause: ```sql -CREATE SEQUENCE nyse_symbol_id_seq; CREATE TABLE nyse_symbol ( - nyse_symbol_id INTEGER NOT NULL PRIMARY KEY DEFAULT NEXTVAL('nyse_symbol_id_seq'), - symbol TEXT NOT NULL, - name TEXT NOT NULL + nyse_symbol_id INTEGER PRIMARY KEY GENERATED ALWAYS AS IDENTITY, + symbol TEXT NOT NULL, + name TEXT NOT NULL ) USING refdata; ``` + +In this case, manipulating data in `nyse_trade` does not generate row locks in `nyse_symbol`. But manipulating `nyse_symbol` directly cause an `EXCLUSIVE` lock to be acquired on the entire relation: + +```sql +=# BEGIN; +BEGIN +=*# +=*# INSERT INTO nyse_symbol (symbol, name) +-*# VALUES ('A', 'A'); +INSERT 0 1 +=*# +=*# SELECT locktype, mode FROM pg_locks +-*# WHERE relation = 'nyse_symbol'::regclass; + locktype | mode +----------+------------------ + relation | RowExclusiveLock + relation | ExclusiveLock +(2 rows) +=*# +=*# COMMIT; +COMMIT +=# +=# BEGIN; +BEGIN +=*# -- insert data into a table that has a foreign key to nyse_symbol +=*# INSERT INTO nyse_trade (nyse_symbol_id, trade_price, trade_volume) +-*# VALUES (1, 1, 1); +INSERT 0 1 +=*# +=*# -- display the row locks in nyse_symbol +=*# SELECT * FROM refdata.pgrowlocks('nyse_symbol'); +(0 rows) +=*# +``` + ## Autocluster example A scenario where Autocluster is useful is with Internet of Things (IoT) data, which are usually inserted with many rows that relate to each other and often use append-only data. When using heap instead of Autocluster, Postgres can't cluster together these related rows, so access to the set of rows touches many data blocks, can be very slow, and is input/output heavy. @@ -25,10 +124,10 @@ This example is for an IoT thermostat that reports house temperatures and temper ```sql CREATE TABLE iot ( - thermostat_id bigint NOT NULL, - recordtime timestamp NOT NULL, - measured_temperature float4, - temperature_setting float4 + thermostat_id BIGINT NOT NULL, + recordtime TIMESTAMPTZ NOT NULL, + measured_temperature FLOAT4, + temperature_setting FLOAT4 ) USING autocluster; ``` @@ -74,128 +173,120 @@ ctid | thermostat_id | recordtime (6 rows) ``` - ## Advanced example +## Advanced example -This is an advanced example where Refdata and Autocluster are used together. It involves referencing the NYSE table from the [Refdata example](#refdata) and clustering together the rows based on the stock symbol. This approach makes it easier to find the latest number of trades. +This is an advanced example where Refdata and Autocluster are used together. It involves referencing the NYSE table from the [Refdata example](#refdata-example) and clustering together the rows in the trade table based on the stock symbol. This approach makes it easier to find the latest number of trades. -Start with the NYSE table from the Refdata example: +Start with the NYSE table from the Refdata example: ```sql -CREATE SEQUENCE nyse_symbol_id_seq; CREATE TABLE nyse_symbol ( - nyse_symbol_id INTEGER NOT NULL PRIMARY KEY DEFAULT NEXTVAL('nyse_symbol_id_seq'), - symbol TEXT NOT NULL, - name TEXT NOT NULL + nyse_symbol_id INTEGER PRIMARY KEY GENERATED ALWAYS AS IDENTITY, + symbol TEXT NOT NULL, + name TEXT NOT NULL ) USING refdata; ``` -Create a highly updated table containing NYSE trades, referencing the mostly static stock symbols in the Refdata table. Cluster the rows on the stock symbol to make it easier to look up the last x trades for a given stock: +Create a highly updated table containing NYSE trades, referencing the mostly +static stock symbols in the Refdata table. Cluster the rows on the stock symbol +to make it easier to look up the last x trades for a given stock: ```sql CREATE TABLE nyse_trade ( - nyse_symbol_id INTEGER NOT NULL REFERENCES nyse_symbol(nyse_symbol_id), - trade_time TIMESTAMP NOT NULL DEFAULT NOW(), - trade_price FLOAT8 NOT NULL CHECK(trade_price >= 0.0), - trade_volume BIGINT NOT NULL CHECK(trade_volume >= 1) -); -- USING autocluster; + nyse_symbol_id INTEGER NOT NULL REFERENCES nyse_symbol(nyse_symbol_id), + trade_time TIMESTAMPTZ NOT NULL DEFAULT NOW(), + trade_price FLOAT8 NOT NULL CHECK(trade_price >= 0.0), + trade_volume BIGINT NOT NULL CHECK(trade_volume >= 1) +) USING autocluster; + CREATE INDEX ON nyse_trade USING BTREE(nyse_symbol_id); SELECT autocluster.autocluster( - rel := 'nyse_trade'::regclass, - cols := '{1}', - max_objects := 3000 + rel := 'nyse_trade'::regclass, + cols := '{1}', + max_objects := 3000 ); - autocluster + autocluster ------------- - -(1 row) -``` - -Create a view to facilitate inserting by symbol name rather than id: -```sql -CREATE VIEW nyse_trade_symbol AS - SELECT ns.symbol, nt.trade_time, nt.trade_price, nt.trade_volume - FROM nyse_symbol ns - JOIN nyse_trade nt - ON ns.nyse_symbol_id = nt.nyse_symbol_id; -CREATE RULE stock_insert AS ON INSERT TO nyse_trade_symbol - DO INSTEAD INSERT INTO nyse_trade - (SELECT ns.nyse_symbol_id, NEW.trade_time, NEW.trade_price, NEW.trade_volume - FROM nyse_symbol ns - WHERE ns.symbol = NEW.symbol - ); +(1 row) ``` -For more information on creating a view, see the [PostgreSQL documentation](https://www.postgresql.org/docs/current/sql-createview.html). - -Prepopulate the static data (shortened for brevity): +Prepopulate the static data (shortened for brevity): ```sql INSERT INTO nyse_symbol (symbol, name) VALUES ('A', 'Agilent Technologies'), - ('AA', 'Alcoa Corp'), - ('AAC', 'Ares Acquisition Corp Cl A'), - ('AAIC', 'Arlington Asset Investment Corp'), - ('AAIN', 'Arlington Asset Investment Corp 6.000%'), - ('AAN', 'Aarons Holdings Company'), - ('AAP', 'Advance Auto Parts Inc'), - ('AAQC', 'Accelerate Acquisition Corp Cl A'), + ('AA', 'Alcoa Corp'), + ('AAC', 'Ares Acquisition Corp Cl A'), + ('AAIC', 'Arlington Asset Investment Corp'), + ('AAIN', 'Arlington Asset Investment Corp 6.000%'), + ('AAN', 'Aarons Holdings Company'), + ('AAP', 'Advance Auto Parts Inc'), + ('AAQC', 'Accelerate Acquisition Corp Cl A'), ('ZTR', 'Virtus Total Return Fund Inc'), - ('ZTS', 'Zoetis Inc Cl A'), - ('ZUO', 'Zuora Inc'), - ('ZVIA', 'Zevia Pbc Cl A'), - ('ZWS', 'Zurn Elkay Water Solutions Corp'), - ('ZYME', 'Zymeworks Inc'); + ('ZTS', 'Zoetis Inc Cl A'), + ('ZUO', 'Zuora Inc'), + ('ZVIA', 'Zevia Pbc Cl A'), + ('ZWS', 'Zurn Elkay Water Solutions Corp'), + ('ZYME', 'Zymeworks Inc'); ANALYZE nyse_symbol; ``` -Insert stock trades over a given time range on Friday, November 18, 2022 (shortened for brevity): - -```sql -\timing -INSERT INTO nyse_trade_symbol VALUES ('NSC', 'Fri Nov 18 09:51:32 2022', 248.100000, 98778); -Time: 32.349 ms -INSERT INTO nyse_trade_symbol VALUES ('BOE', 'Fri Nov 18 09:51:32 2022', 9.640000, 72973); -Time: 1.055 ms -INSERT INTO nyse_trade_symbol VALUES ('LOMA', 'Fri Nov 18 09:51:32 2022', 6.180000, 41632); -Time: 0.927 ms -INSERT INTO nyse_trade_symbol VALUES ('LXP', 'Fri Nov 18 09:51:32 2022', 10.670000, 85768); -Time: 0.941 ms -INSERT INTO nyse_trade_symbol VALUES ('ABBV', 'Fri Nov 18 09:51:32 2022', 155.000000, 46842); -Time: 0.916 ms -INSERT INTO nyse_trade_symbol VALUES ('AGD', 'Fri Nov 18 09:51:32 2022', 9.360000, 90684); -Time: 0.669 ms -INSERT INTO nyse_trade_symbol VALUES ('PAGS', 'Fri Nov 18 11:14:31 2022', 12.985270, 34734); -Time: 0.849 ms -INSERT INTO nyse_trade_symbol VALUES ('KTF', 'Fri Nov 18 11:14:31 2022', 8.435753, 73719); -Time: 0.679 ms -INSERT INTO nyse_trade_symbol VALUES ('AES', 'Fri Nov 18 11:14:31 2022', 28.072732, 549); -Time: 0.667 ms -INSERT INTO nyse_trade_symbol VALUES ('LIN', 'Fri Nov 18 11:14:31 2022', 334.617829, 39838); -Time: 0.665 ms -INSERT INTO nyse_trade_symbol VALUES ('DTB', 'Fri Nov 18 11:14:31 2022', 18.679245, 55863); -Time: 0.680 ms +Insert artificial stock trades, one trade per stock symbol, repeating the +pattern multiple times: + +```sql +INSERT INTO nyse_trade + SELECT nyse_symbol_id, now(), i, i + FROM nyse_symbol, generate_series(1,1000000) AS i; ANALYZE nyse_trade; -Time: 73.832 ms ``` -Select the ctid from the data for a given stock symbol to see in the output how it was clustered together: +Given that the inserts intercalated `nyse_symbol_id`, a query that consults one +stock would touch most pages if the table used `heap`, but would touch far +fewer pages using Autocluster. + +The following query operates on attributes that must be fetched from the table +after an index scan, and shows the number of buffers touched: ```sql -SELECT ctid, * FROM nyse_trade WHERE nyse_symbol_id = 1000 ORDER BY trade_time DESC LIMIT 10; -__OUTPUT__ -ctid | nyse_symbol_id | trade_time | trade_price | trade_volume ------------+----------------+--------------------------+-------------+-------------- - (729,71) | 1000 | Fri Nov 18 11:13:51 2022 | 11.265938 | 72662 - (729,22) | 1000 | Fri Nov 18 11:08:39 2022 | 11.262747 | 50897 - (729,20) | 1000 | Fri Nov 18 11:08:30 2022 | 11.267203 | 37120 - (729,9) | 1000 | Fri Nov 18 11:07:21 2022 | 11.269852 | 792 - (729,6) | 1000 | Fri Nov 18 11:07:02 2022 | 11.268067 | 46221 - (632,123) | 1000 | Fri Nov 18 11:04:46 2022 | 11.272623 | 97874 - (632,118) | 1000 | Fri Nov 18 11:04:28 2022 | 11.271794 | 65579 - (632,14) | 1000 | Fri Nov 18 10:55:45 2022 | 11.268543 | 8557 - (632,2) | 1000 | Fri Nov 18 10:54:45 2022 | 11.26414 | 94078 - (506,126) | 1000 | Fri Nov 18 10:54:01 2022 | 11.264657 | 89641 +EXPLAIN (ANALYZE, BUFFERS, TIMING OFF, SUMMARY OFF, COSTS OFF) + SELECT AVG(trade_volume * trade_price) + FROM nyse_trade WHERE nyse_symbol_id = 10; +``` + +This is the query plan using `autocluster`: + +``` + QUERY PLAN +---------------------------------------------------------------------------------------------- + Aggregate (actual rows=1 loops=1) + **Buffers: shared read=59609** + -> Bitmap Heap Scan on nyse_trade (actual rows=1000000 loops=1) + Recheck Cond: (nyse_symbol_id = 10) + Heap Blocks: exact=58824 + Buffers: shared read=59609 + -> Bitmap Index Scan on nyse_trade_nyse_symbol_id_idx (actual rows=1000000 loops=1) + Index Cond: (nyse_symbol_id = 10) + Buffers: shared read=785 +(9 rows) +``` + +For contrast, this is the query plan using `heap`: + +``` + QUERY PLAN +---------------------------------------------------------------------------------------------- + Aggregate (actual rows=1 loops=1) + **Buffers: shared read=103727** + -> Bitmap Heap Scan on nyse_trade (actual rows=1000000 loops=1) + Recheck Cond: (nyse_symbol_id = 10) + Rows Removed by Index Recheck: 8325053 + Heap Blocks: exact=37020 lossy=65922 + Buffers: shared read=103727 + -> Bitmap Index Scan on nyse_trade_nyse_symbol_id_idx (actual rows=1000000 loops=1) + Index Cond: (nyse_symbol_id = 10) + Buffers: shared read=785 (10 rows) ``` From b404aeeadd1d2bb53dcf085bacb49054f1c5879a Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 11 Sep 2023 11:29:01 +0530 Subject: [PATCH 103/255] Update 01_object_type_specification_syntax.mdx --- .../01_object_type_specification_syntax.mdx | 6 ------ 1 file changed, 6 deletions(-) diff --git a/product_docs/docs/epas/11/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx b/product_docs/docs/epas/11/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx index a205868915f..0b937920376 100644 --- a/product_docs/docs/epas/11/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx +++ b/product_docs/docs/epas/11/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx @@ -113,12 +113,6 @@ The following points should be noted about an object type specification: - There may be none, one, or more methods defined in the object type. -- For each member method there is an implicit, built-in parameter named `SELF`, whose data type is that of the object type being defined. - - `SELF` refers to the object instance that is currently invoking the method. `SELF` can be explicitly declared as an `IN` or `IN OUT` parameter in the parameter list (for example as `MEMBER FUNCTION (SELF IN OUT object_type ...)).` - - If `SELF` is explicitly declared, `SELF` must be the first parameter in the parameter list. If `SELF` is not explicitly declared, its parameter mode defaults to `IN OUT` for member procedures and `IN` for member functions. - - A static method cannot be overridden (`OVERRIDING` and `STATIC` cannot be specified together in `method_spec`). - A static method must be instantiable (`NOT INSTANTIABLE` and `STATIC` cannot be specified together in `method_spec`). From cb50970d702d89d435900170c89898d85b7cc70d Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 11 Sep 2023 11:29:47 +0530 Subject: [PATCH 104/255] Update 01_object_type_specification_syntax.mdx --- .../01_object_type_specification_syntax.mdx | 6 ------ 1 file changed, 6 deletions(-) diff --git a/product_docs/docs/epas/12/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx b/product_docs/docs/epas/12/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx index a205868915f..0b937920376 100644 --- a/product_docs/docs/epas/12/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx +++ b/product_docs/docs/epas/12/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx @@ -113,12 +113,6 @@ The following points should be noted about an object type specification: - There may be none, one, or more methods defined in the object type. -- For each member method there is an implicit, built-in parameter named `SELF`, whose data type is that of the object type being defined. - - `SELF` refers to the object instance that is currently invoking the method. `SELF` can be explicitly declared as an `IN` or `IN OUT` parameter in the parameter list (for example as `MEMBER FUNCTION (SELF IN OUT object_type ...)).` - - If `SELF` is explicitly declared, `SELF` must be the first parameter in the parameter list. If `SELF` is not explicitly declared, its parameter mode defaults to `IN OUT` for member procedures and `IN` for member functions. - - A static method cannot be overridden (`OVERRIDING` and `STATIC` cannot be specified together in `method_spec`). - A static method must be instantiable (`NOT INSTANTIABLE` and `STATIC` cannot be specified together in `method_spec`). From 4a6479ccc96263cb6fbcfa94ae3b97f5c5d2c015 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 11 Sep 2023 11:30:22 +0530 Subject: [PATCH 105/255] Update 01_object_type_specification_syntax.mdx --- .../01_object_type_specification_syntax.mdx | 6 ------ 1 file changed, 6 deletions(-) diff --git a/product_docs/docs/epas/13/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx b/product_docs/docs/epas/13/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx index 05e797abf97..34628c1404f 100644 --- a/product_docs/docs/epas/13/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx +++ b/product_docs/docs/epas/13/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx @@ -116,12 +116,6 @@ The following points should be noted about an object type specification: - There may be none, one, or more methods defined in the object type. -- For each member method there is an implicit, built-in parameter named `SELF`, whose data type is that of the object type being defined. - - `SELF` refers to the object instance that is currently invoking the method. `SELF` can be explicitly declared as an `IN` or `IN OUT` parameter in the parameter list (for example as `MEMBER FUNCTION (SELF IN OUT object_type ...)).` - - If `SELF` is explicitly declared, `SELF` must be the first parameter in the parameter list. If `SELF` is not explicitly declared, its parameter mode defaults to `IN OUT` for member procedures and `IN` for member functions. - - A static method cannot be overridden (`OVERRIDING` and `STATIC` cannot be specified together in `method_spec`). - A static method must be instantiable (`NOT INSTANTIABLE` and `STATIC` cannot be specified together in `method_spec`). From e0d9e571c1263ceab68dbdfb4114b34bb9d8f5f7 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 6 Sep 2023 14:13:44 +0100 Subject: [PATCH 106/255] Update scripts for next import Signed-off-by: Dj Walker-Morgan --- scripts/source/process-tpa-docs-auto.sh | 12 ++++++------ scripts/source/{tpaexec.js => tpa.js} | 0 2 files changed, 6 insertions(+), 6 deletions(-) rename scripts/source/{tpaexec.js => tpa.js} (100%) diff --git a/scripts/source/process-tpa-docs-auto.sh b/scripts/source/process-tpa-docs-auto.sh index 3c7ea5eb87f..e67d00291ef 100755 --- a/scripts/source/process-tpa-docs-auto.sh +++ b/scripts/source/process-tpa-docs-auto.sh @@ -8,16 +8,16 @@ then exit 1 fi -SOURCE_CHECKOUT="/tmp/tpaexecforimport" +SOURCE_CHECKOUT="/tmp/tpaforimport" rm -rf $SOURCE_CHECKOUT if [ -z $2 ] then -# Get the TPAexec tree into /tmp/tpaexecforimport - git clone https://github.com/EnterpriseDB/tpaexec.git $SOURCE_CHECKOUT +# Get the TPA tree into /tmp/tpaforimport + git clone https://github.com/EnterpriseDB/tpa.git $SOURCE_CHECKOUT else - # Get specific branch of the TPAexec tree into /tmp/tpaexecforimport - git clone -b $2 https://github.com/EnterpriseDB/tpaexec.git $SOURCE_CHECKOUT + # Get specific branch of the TPA tree into /tmp/tpaforimport + git clone -b $2 https://github.com/EnterpriseDB/tpa.git $SOURCE_CHECKOUT fi # convert inputs to actual directory names, in case a relative path is passed in. @@ -30,7 +30,7 @@ node $DESTINATION_CHECKOUT/scripts/source/files-to-ignore.mjs \ cd $SOURCE_CHECKOUT/docs/ -node $DESTINATION_CHECKOUT/scripts/source/tpaexec.js src +node $DESTINATION_CHECKOUT/scripts/source/tpa.js src node $DESTINATION_CHECKOUT/scripts/source/merge-indexes.mjs \ "$SOURCE_CHECKOUT/docs/src/index.mdx" \ diff --git a/scripts/source/tpaexec.js b/scripts/source/tpa.js similarity index 100% rename from scripts/source/tpaexec.js rename to scripts/source/tpa.js From a5a6dc4e50793c1ecfa342ef7fcd6d1daece9623 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 6 Sep 2023 15:17:08 +0100 Subject: [PATCH 107/255] Updated pages for new repo name Signed-off-by: Dj Walker-Morgan --- .../docs/tpa/23/reference/INSTALL-docker.mdx | 4 ++-- product_docs/docs/tpa/23/reference/INSTALL-repo.mdx | 12 ++++++------ 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/product_docs/docs/tpa/23/reference/INSTALL-docker.mdx b/product_docs/docs/tpa/23/reference/INSTALL-docker.mdx index 85616c177b8..34b1b2be4cd 100644 --- a/product_docs/docs/tpa/23/reference/INSTALL-docker.mdx +++ b/product_docs/docs/tpa/23/reference/INSTALL-docker.mdx @@ -22,8 +22,8 @@ Run the following commands to clone the tpaexec source repository from Github and build a new Docker image named `tpa/tpaexec`: ```bash -$ git clone ssh://git@github.com/EnterpriseDB/tpaexec.git -$ cd tpaexec +$ git clone ssh://git@github.com/EnterpriseDB/tpa.git +$ cd tpa $ docker build -t tpa/tpaexec . ``` diff --git a/product_docs/docs/tpa/23/reference/INSTALL-repo.mdx b/product_docs/docs/tpa/23/reference/INSTALL-repo.mdx index 6d762c6d8a7..63d1b3f5010 100644 --- a/product_docs/docs/tpa/23/reference/INSTALL-repo.mdx +++ b/product_docs/docs/tpa/23/reference/INSTALL-repo.mdx @@ -41,9 +41,9 @@ $ brew install python@3 openvpn flock coreutils gpatch git Next, install TPA itself: ```bash -$ git clone ssh://git@github.com/EnterpriseDB/tpaexec.git -$ ./tpaexec/bin/tpaexec setup -$ ./tpaexec/bin/tpaexec selftest +$ git clone ssh://git@github.com/EnterpriseDB/tpa.git +$ ./tpa/bin/tpaexec setup +$ ./tpa/bin/tpaexec selftest ``` ## Step-by-step @@ -54,13 +54,13 @@ If your system does not have Python 3.6+ packages, you can use `pyenv` to install a more recent Python in your home directory (see below), or you can [run TPA in a Docker container](INSTALL-docker/). -Next, clone the TPA repository into, say, `~/tpaexec`. (It doesn't +Next, clone the TPA repository into, say, `~/tpa`. (It doesn't matter where you put it, but don't use `/opt/EDB/TPA` or `/opt/2ndQuadrant/TPA`, to avoid conflicts if you install the TPA packages in future.) ```bash -$ git clone ssh://git@github.com/EnterpriseDB/tpaexec.git ~/tpaexec +$ git clone ssh://git@github.com/EnterpriseDB/tpa.git ~/tpa ``` (If you're installing from source, please clone the repository instead @@ -71,7 +71,7 @@ The remaining steps are the same as if you had installed the package. ```bash # Add tpaexec to your PATH for convenience # (Put this in your ~/.bashrc too) -$ export PATH=$PATH:$HOME/tpaexec/bin +$ export PATH=$PATH:$HOME/tpa/bin $ tpaexec setup $ tpaexec selftest From 75c7a1cacd301a9a412cd773c462714182a8c1fb Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Fri, 8 Sep 2023 18:42:37 +0000 Subject: [PATCH 108/255] update other script references to tpaexec --- scripts/source/dispatch_product.py | 2 +- scripts/source/process-tpa-docs.sh | 2 +- scripts/source/tpa.js | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/source/dispatch_product.py b/scripts/source/dispatch_product.py index ce829b4c6a9..9f374788903 100755 --- a/scripts/source/dispatch_product.py +++ b/scripts/source/dispatch_product.py @@ -18,7 +18,7 @@ "EnterpriseDB/bdr": f"node {args.workspace}/destination/scripts/source/bdr.js {args.workspace}/source {args.workspace}/destination --unhandled-rejections=strict", "EnterpriseDB/pglogical": f"node {args.workspace}/destination/scripts/source/pglogical.js {args.workspace}/source {args.workspace}/destination --unhandled-rejections=strict", "EnterpriseDB/harp": f"rsync -a --delete {args.workspace}/source/docs/user_guide/ {args.workspace}/destination/product_docs/docs/harp/2.0/", - "EnterpriseDB/tpaexec": f"{args.workspace}/destination/scripts/source/process-tpa-docs.sh {args.workspace}/source {args.workspace}/destination", + "EnterpriseDB/tpa": f"{args.workspace}/destination/scripts/source/process-tpa-docs.sh {args.workspace}/source {args.workspace}/destination", } ret = os.system( diff --git a/scripts/source/process-tpa-docs.sh b/scripts/source/process-tpa-docs.sh index 9f16993cd5f..fba0e81587d 100755 --- a/scripts/source/process-tpa-docs.sh +++ b/scripts/source/process-tpa-docs.sh @@ -19,7 +19,7 @@ node $DESTINATION_CHECKOUT/scripts/source/files-to-ignore.mjs \ cd $SOURCE_CHECKOUT/docs/ -node $DESTINATION_CHECKOUT/scripts/source/tpaexec.js src +node $DESTINATION_CHECKOUT/scripts/source/tpa.js src node $DESTINATION_CHECKOUT/scripts/source/merge-indexes.mjs \ "$SOURCE_CHECKOUT/docs/src/index.mdx" \ diff --git a/scripts/source/tpa.js b/scripts/source/tpa.js index 98db309ed45..17287a256f8 100644 --- a/scripts/source/tpa.js +++ b/scripts/source/tpa.js @@ -1,4 +1,4 @@ -// run: node scripts/source/tpaexec.js source_path" +// run: node scripts/source/tpa.js source_path" // purpose: // Import and convert the tpa docs to EDB Docs -style MDX // From 7ed2dd1c64b0ee11735df474a342a925a5038ebb Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 11 Sep 2023 10:25:02 -0400 Subject: [PATCH 109/255] BigAnimal: some cpu/memory is reserved by the system --- .../release/getting_started/creating_a_cluster/index.mdx | 3 +++ 1 file changed, 3 insertions(+) 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 index 931630f5e0f..1f53e92d5ad 100644 --- 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 @@ -90,6 +90,9 @@ The following options aren't available when creating your cluster: - Compute optimized for compute bound applications - General purpose if you don't require memory or compute optimization 1. Select the instance series and size. See [Sizes for virtual machines in Azure](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes), [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/), or the [Google Cloud Machine families resource and comparison guide](https://cloud.google.com/compute/docs/machine-resource) for information to help you choose the appropriate instance type. + !!!note + Some CPU/memory is reserved by BigAnimal. + !!!tip To maximize your disk size for AWS, select Rb5 as your instance and then io2 Block Express as your storage to get a maximum disk size of 64 TB and 256,000 IOPS. From f71e2f56758de4b6da8a758e6fad4935581b654a Mon Sep 17 00:00:00 2001 From: Lenz Grimmer Date: Mon, 11 Sep 2023 14:38:39 +0200 Subject: [PATCH 110/255] Update BDR 3.7 Upgrading chapter Improved document title to be more precise. BDR-4081 --- product_docs/docs/pgd/3.7/bdr/upgrades/index.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pgd/3.7/bdr/upgrades/index.mdx b/product_docs/docs/pgd/3.7/bdr/upgrades/index.mdx index 53fdb230e87..ee3fdfefaa7 100644 --- a/product_docs/docs/pgd/3.7/bdr/upgrades/index.mdx +++ b/product_docs/docs/pgd/3.7/bdr/upgrades/index.mdx @@ -1,6 +1,6 @@ --- -navTitle: Upgrades -title: Application Schema Upgrades +navTitle: Upgrading +title: Upgrading originalFilePath: upgrades.md --- From d131a3dc6aca76fa2d4266c6653af2544f6a3bb5 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 31 Aug 2023 10:35:16 -0400 Subject: [PATCH 111/255] BigAnimal: planning section --- .../02_connecting_to_your_cloud/index.mdx | 2 +- .../creating_a_cluster/index.mdx | 2 +- .../01_preparing_azure/index.mdx | 2 +- .../02_preparing_aws.mdx | 2 +- .../preparing_cloud_account/index.mdx | 2 +- .../preparing_gcp/index.mdx | 2 +- product_docs/docs/biganimal/release/index.mdx | 1 + .../release/overview/02_high_availability.mdx | 39 ++++--------------- .../release/overview/03_security/index.mdx | 2 +- .../overview/03a_region_support/index.mdx | 2 +- .../planning/choosing_cluster_type.mdx | 19 +++++++++ .../planning/choosing_postgres_distro.mdx | 15 +++++++ .../deployment_options/index.mdx | 4 +- .../docs/biganimal/release/planning/index.mdx | 8 ++++ 14 files changed, 61 insertions(+), 41 deletions(-) create mode 100644 product_docs/docs/biganimal/release/planning/choosing_cluster_type.mdx create mode 100644 product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx rename product_docs/docs/biganimal/release/{overview => planning}/deployment_options/index.mdx (87%) create mode 100644 product_docs/docs/biganimal/release/planning/index.mdx diff --git a/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/index.mdx b/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/index.mdx index 14338bd0226..3b5c33740cc 100644 --- a/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/index.mdx @@ -6,7 +6,7 @@ redirects: - /biganimal/release/getting_started/02_connecting_to_your_cloud/01_connecting_your_own_cloud --- -Use these techniques to connect your cloud if you're using your own cloud account as your [deployment option](/biganimal/release/overview/deployment_options). +Use these techniques to connect your cloud if you're using your own cloud account as your [deployment option](/biganimal/release/planning/deployment_options). ## BigAnimal access requirements 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 index 1f53e92d5ad..0daf3917b52 100644 --- 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 @@ -52,7 +52,7 @@ The following options aren't available when creating your cluster: 1. Select the number of standby replicas for your primary/standby high-availability cluster. -1. Select the type of cloud account for your cluster. You can choose BigAnimal's cloud account or set up your own. For more information, see [Deployment options](../../overview/deployment_options). +1. Select the type of cloud account for your cluster. You can choose BigAnimal's cloud account or set up your own. For more information, see [Deployment options](../../planning/deployment_options). !!! Note If you use BigAnimal's cloud account, your estimated cloud infrastructure costs are calculated into your cluster's estimated monthly price shown at the bottom of the page. diff --git a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/index.mdx b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/index.mdx index bf9074b3549..a23cbaa4a9e 100644 --- a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/index.mdx @@ -4,7 +4,7 @@ redirects: - /biganimal/latest/getting_started/01_preparing_azure/ --- -BigAnimal requires you to check the readiness of your Azure subscription before you deploy your clusters. (You don't need to perform this check if you're using BigAnimal's cloud account as your [deployment option](/biganimal/release/overview/deployment_options).) The checks that you perform ensure that your Azure subscription is prepared to meet your clusters' requirements and resource limits, such as: +BigAnimal requires you to check the readiness of your Azure subscription before you deploy your clusters. (You don't need to perform this check if you're using BigAnimal's cloud account as your [deployment option](/biganimal/release/planning/deployment_options).) The checks that you perform ensure that your Azure subscription is prepared to meet your clusters' requirements and resource limits, such as: - Are the necessary Azure resource providers registered for your subscription? - Is there a restriction on SKUs for the standard Esv3 family and standard D2_v4 VM size? diff --git a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/02_preparing_aws.mdx b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/02_preparing_aws.mdx index d18c95557a6..0cbc6a6c5d5 100644 --- a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/02_preparing_aws.mdx +++ b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/02_preparing_aws.mdx @@ -3,7 +3,7 @@ title: "Preparing your AWS account" --- -BigAnimal requires you to check the readiness of your AWS account before you deploy your clusters. (You don't need to perform this check if you're using BigAnimal's cloud account as your [deployment option](/biganimal/release/overview/deployment_options).) The checks that you perform ensure that your AWS account is prepared to meet your clusters' requirements and resource limits, such as: +BigAnimal requires you to check the readiness of your AWS account before you deploy your clusters. (You don't need to perform this check if you're using BigAnimal's cloud account as your [deployment option](/biganimal/release/planning/deployment_options).) The checks that you perform ensure that your AWS account is prepared to meet your clusters' requirements and resource limits, such as: - Is the AWS CLI configured to access your AWS account? - Is there a sufficient limit on the number of vCPUs and Network Load Balancers (NLBs) left in your region? diff --git a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/index.mdx b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/index.mdx index 4364ed631ae..4139aaf601e 100644 --- a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/index.mdx @@ -10,4 +10,4 @@ navigation: - preparing_gcp --- -When using your cloud account, each time you create a cluster, you must ensure the readiness of your cloud to work with BigAnimal. You need to perform this check only if you're not using BigAnimal's cloud account as your [deployment option](/biganimal/release/overview/deployment_options). +When using your cloud account, each time you create a cluster, you must ensure the readiness of your cloud to work with BigAnimal. You need to perform this check only if you're not using BigAnimal's cloud account as your [deployment option](/biganimal/release/planning/deployment_options). diff --git a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/index.mdx b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/index.mdx index d6b2aa61c90..b90f5b0a2eb 100644 --- a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/preparing_gcp/index.mdx @@ -2,7 +2,7 @@ title: Preparing your Google Cloud account --- -BigAnimal requires you to check the readiness of your Google Cloud (GCP) account before you deploy your clusters. (You don't need to perform this check if you're using BigAnimal's cloud account as your [deployment option](/biganimal/release/overview/deployment_options).) The checks that you perform ensure that your Google Cloud account is prepared to meet your clusters' requirements and resource limits. +BigAnimal requires you to check the readiness of your Google Cloud (GCP) account before you deploy your clusters. (You don't need to perform this check if you're using BigAnimal's cloud account as your [deployment option](/biganimal/release/planning/deployment_options).) The checks that you perform ensure that your Google Cloud account is prepared to meet your clusters' requirements and resource limits. !!! Note Before proceeding, see [Understanding requirements in Google Cloud](understanding_quotas_in_gcp) for details on planning for your clusters' requirements and resource limits in Google Cloud. diff --git a/product_docs/docs/biganimal/release/index.mdx b/product_docs/docs/biganimal/release/index.mdx index 62c0b513a92..abf79c38d8b 100644 --- a/product_docs/docs/biganimal/release/index.mdx +++ b/product_docs/docs/biganimal/release/index.mdx @@ -10,6 +10,7 @@ directoryDefaults: navigation: - free_trial - overview + - planning - getting_started - using_cluster - administering_cluster diff --git a/product_docs/docs/biganimal/release/overview/02_high_availability.mdx b/product_docs/docs/biganimal/release/overview/02_high_availability.mdx index 29b134f018a..22502abe6e1 100644 --- a/product_docs/docs/biganimal/release/overview/02_high_availability.mdx +++ b/product_docs/docs/biganimal/release/overview/02_high_availability.mdx @@ -8,37 +8,12 @@ redirects: BigAnimal supports three cluster types: - Single node - Primary/standby high availability -- Distributed high availability) +- Distributed high availability You choose the type of cluster you want on the [Create Cluster](https://portal.biganimal.com/create-cluster) page in the [BigAnimal](https://portal.biganimal.com) portal. -## Choosing your Postgres distribution -Postgres distribution and version support varies by [cluster](#choosing-your-cluster-type-and-configuration) and [deployment](deployment_options) type. - -| Postgres distribution | Versions | Cluster type | Deployment type | -| ---------------------------- | -------- | ------------------------------ | ----------------------- | -| PostgreSQL | 11–15 | Single-node, primary/standby high-availability | Your cloud account | -| PostgreSQL | 12–15 | Single-node, primary/standby high-availability | BigAnimal cloud account | -| EDB Postgres Advanced Server | 12–15 | Single-node, primary/standby high-availability | Your cloud account | -| EDB Postgres Advanced Server | 14–15 | Single node, primary/standby high availability | BigAnimal cloud account | -| EDB Postgres Advanced Server | 14–15 | Distributed high-availability | Your cloud account | -| EDB Postgres Extended Server | 14-15 | Distributed high-availability | Your cloud account | - -## Choosing your cluster type and configuration - -| Consideration | [Single node](#single-node) |[Primary/standby HA](#primarystandby-high-availability) | [HA + standby replica](#standby-replicas) | [Distributed HA single region](#single-data-location) | [Distributed HA multi-region](#two-data-locations-and-witness) | -|--------------------------|-----------|------------------|--------------------|----------------------------|---------------------------| -| Data replication | None | Physical | Physical | Logical | Logical | -| Region | Single | Single | Multi | Single | Multi | -| VM failure tolerance | ✅ | ✅ | ✅ | ✅ | ✅ | -| AZ failure tolerance | TBD | ✅ | ✅ | ✅ | ✅ | -| Region failure tolerance | TBD | TBD | ✅ | TBD | ✅ | -| Recovery time objective | varies | 35s-60s | varies | 0 | 0 | -| Recovery point objective | <5 min | 0 | <5 min | 0 | 30s (configurable) | -| Service level agreement | 99.5% | 99.99% | 99.99% | 99.99% | 99.995% | - -### Single node +## Single node For nonproduction use cases where high availability isn't a primary concern, a cluster deployment with high availability not enabled provides one primary with no standby replicas for failover or read-only workloads. @@ -46,7 +21,7 @@ In case of unrecoverable failure of the primary, a restore from a backup is requ ![BigAnimal Cluster4](images/single-node.png) -### Primary/standby high availability +## Primary/standby high availability The Primary/Standby High Availability option is provided to minimize downtime in cases of failures. Primary/standby high-availability clusters—one *primary* and one or two *standby replicas*—are configured automatically, with standby replicas staying up to date through physical streaming replication. @@ -60,7 +35,7 @@ In case of temporary or permanent unavailability of the primary, a standby repli Incoming client connections are always routed to the current primary. In case of failure of the primary, a standby replica is promoted to primary, and new connections are routed to the new primary. When the old primary recovers, it rejoins the cluster as a standby replica. -#### Standby replicas +### Standby replicas By default, replication is synchronous to one standby replica and asynchronous to the other. That is, one standby replica must confirm that a transaction record was written to disk before the client receives acknowledgment of a successful commit. @@ -87,11 +62,11 @@ The witness node/witness group doesn't host data but exists for management purpo !!!Note Operations against a distributed high-availability cluster leverage the [EDB Postgres Distributed switchover](/pgd/latest/cli/command_ref/pgd_switchover/) feature which provides sub-second interruptions during planned lifecycle operations. -#### Single data location +### Single data location A single data location configuration has three data nodes with one lead and two shadow nodes each in separate availability zones. -#### Two data locations and witness +### Two data locations and witness A true active-active solution that protects against regional failures, a two data locations configuration has: @@ -103,7 +78,7 @@ A true active-active solution that protects against regional failures, a two dat -### For more information +## For more information For instructions on creating a distributed high-availability cluster using the BigAnimal portal, see [Creating a distributed high-availability cluster](../getting_started/creating_a_cluster/creating_an_eha_cluster/). diff --git a/product_docs/docs/biganimal/release/overview/03_security/index.mdx b/product_docs/docs/biganimal/release/overview/03_security/index.mdx index 7850723ff0a..32c6eaf56ce 100644 --- a/product_docs/docs/biganimal/release/overview/03_security/index.mdx +++ b/product_docs/docs/biganimal/release/overview/03_security/index.mdx @@ -2,7 +2,7 @@ title: "Security" --- -BigAnimal runs in your own cloud account or BigAnimal's cloud account. Every BigAnimal cluster is logically isolated from other BigAnimal clusters, but the security properties of the system are different in each [deployment option](/biganimal/release/overview/deployment_options). The key security features are: +BigAnimal runs in your own cloud account or BigAnimal's cloud account. Every BigAnimal cluster is logically isolated from other BigAnimal clusters, but the security properties of the system are different in each [deployment option](/biganimal/release/planning/deployment_options). The key security features are: - **Data isolation:** With both deployment options, data is fully isolated between separate clusters. No two BigAnimal clusters share a Postgres process, virtual machine, or storage volume. The implementation of this isolation depends on the deployment option. - **Your own cloud account:** Clusters are installed and managed on virtual machines and storage volumes deployed by BigAnimal on your behalf in your cloud environment. Complete segregation of your data is assured. Your data never leaves your cloud account, and your clusters don't share network segments with other customers' clusters. diff --git a/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx b/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx index 19b20fafd22..cb1b41582ef 100644 --- a/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx +++ b/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx @@ -3,7 +3,7 @@ title: "Supported regions" deepToC: true --- -Region support varies by whether you're using [your cloud account](#your-cloud-account) or [Biganimal's cloud account](#biganimals-cloud-account) as your [deployment option](/biganimal/release/overview/deployment_options). +Region support varies by whether you're using [your cloud account](#your-cloud-account) or [Biganimal's cloud account](#biganimals-cloud-account) as your [deployment option](/biganimal/release/planning/deployment_options). See [Country and geographical region reference](country_reference) for information on geographical region short names and the countries that are in each geographical region. diff --git a/product_docs/docs/biganimal/release/planning/choosing_cluster_type.mdx b/product_docs/docs/biganimal/release/planning/choosing_cluster_type.mdx new file mode 100644 index 00000000000..3fd76d7e8db --- /dev/null +++ b/product_docs/docs/biganimal/release/planning/choosing_cluster_type.mdx @@ -0,0 +1,19 @@ +--- +title: Choosing your cluster type +description: Choose the cluster type and configuration that meets your availability requirements. +--- + +Choose the cluster type and configuration that meets your availability requirements. + +Select the cluster type names in the table heading for more information on each type and configuration. + +| Consideration | [Single node](../overview/02_high_availability/#single-node) | [Primary/Standby HA](../overview/02_high_availability/#primarystandby-high-availability) | [HA + standby replica](../overview/02_high_availability/#standby-replicas) | [Distributed HA single region](../overview/02_high_availability/#single-data-location) | [Distributed HA multi-region](../overview/02_high_availability/#two-data-locations-and-witness) | +| ------------------------ | --------------------------- | ------------------------------------------------------ | ----------------------------------------- | ----------------------------------------------------- | -------------------------------------------------------------- | +| Data replication | None | Physical | Physical | Logical | Logical | +| Region | Single | Single | Multi | Single | Multi | +| VM failure tolerance | ✅ | ✅ | ✅ | ✅ | ✅ | +| AZ failure tolerance | TBD | ✅ | ✅ | ✅ | ✅ | +| Region failure tolerance | TBD | TBD | ✅ | TBD | ✅ | +| Recovery time objective | varies | 35s-60s | varies | 0 | 0 | +| Recovery point objective | <5 min | 0 | <5 min | 0 | 30s (configurable) | +| Service level agreement | 99.5% | 99.99% | 99.99% | 99.99% | 99.995% | diff --git a/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx b/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx new file mode 100644 index 00000000000..b0699f1272e --- /dev/null +++ b/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx @@ -0,0 +1,15 @@ +--- +title: Choosing your Postgres distribution +description: See what Postgres distributions and versions are available based on your deployment and availability choices. +--- + +Postgres distribution and version support varies by [cluster](../overview/02_high_availability) and [deployment](deployment_options) type. + +| Postgres distribution | Versions | Cluster type | Deployment type | +| ---------------------------- | -------- | ------------------------------ | ----------------------- | +| PostgreSQL | 11–15 | Single-node, primary/standby high-availability | Your cloud account | +| PostgreSQL | 12–15 | Single-node, primary/standby high-availability | BigAnimal cloud account | +| EDB Postgres Advanced Server | 12–15 | Single-node, primary/standby high-availability | Your cloud account | +| EDB Postgres Advanced Server | 14–15 | Single node, primary/standby high availability | BigAnimal cloud account | +| EDB Postgres Advanced Server | 14–15 | Distributed high-availability | Your cloud account | + diff --git a/product_docs/docs/biganimal/release/overview/deployment_options/index.mdx b/product_docs/docs/biganimal/release/planning/deployment_options/index.mdx similarity index 87% rename from product_docs/docs/biganimal/release/overview/deployment_options/index.mdx rename to product_docs/docs/biganimal/release/planning/deployment_options/index.mdx index 30cdb020c27..0be0c798587 100644 --- a/product_docs/docs/biganimal/release/overview/deployment_options/index.mdx +++ b/product_docs/docs/biganimal/release/planning/deployment_options/index.mdx @@ -1,5 +1,7 @@ --- -title: Deployment options +title: Choosing your deployment option +description: Choose to use either your cloud account or BigAnimal's. +redirect: ../overview/deployment_options --- You have two deployment options with BigAnimal. You can deploy clusters in your cloud account, or you can deploy in BigAnimal's cloud account. diff --git a/product_docs/docs/biganimal/release/planning/index.mdx b/product_docs/docs/biganimal/release/planning/index.mdx new file mode 100644 index 00000000000..47f23a4f467 --- /dev/null +++ b/product_docs/docs/biganimal/release/planning/index.mdx @@ -0,0 +1,8 @@ +--- +title: Planning +indexCards: simple +navigation: +- deployment_options +- choosing_cluster_type +- choosing_postgres_distro +--- \ No newline at end of file From 255017c3c554679f426b4d18fb9d81e6f565d482 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 1 Sep 2023 08:02:14 -0400 Subject: [PATCH 112/255] Broke up Postgres table --- .../planning/choosing_postgres_distro.mdx | 20 ++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx b/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx index b0699f1272e..d14ee07593a 100644 --- a/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx +++ b/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx @@ -5,11 +5,17 @@ description: See what Postgres distributions and versions are available based on Postgres distribution and version support varies by [cluster](../overview/02_high_availability) and [deployment](deployment_options) type. -| Postgres distribution | Versions | Cluster type | Deployment type | -| ---------------------------- | -------- | ------------------------------ | ----------------------- | -| PostgreSQL | 11–15 | Single-node, primary/standby high-availability | Your cloud account | -| PostgreSQL | 12–15 | Single-node, primary/standby high-availability | BigAnimal cloud account | -| EDB Postgres Advanced Server | 12–15 | Single-node, primary/standby high-availability | Your cloud account | -| EDB Postgres Advanced Server | 14–15 | Single node, primary/standby high availability | BigAnimal cloud account | -| EDB Postgres Advanced Server | 14–15 | Distributed high-availability | Your cloud account | +## Postgres distribution using your cloud account +| Postgres distribution | Versions | Cluster type | +|------------------------------|----------|------------------------------------------------| +| PostgreSQL | 11–15 | Single-node, primary/standby high-availability | +| EDB Postgres Advanced Server | 12–15 | Single-node, primary/standby high-availability | +| EDB Postgres Advanced Server | 14–15 | Distributed high-availability | + +## Postgres distribution using the BigAnimal cloud account + +| Postgres distribution | Versions | Cluster type | +|------------------------------|----------|------------------------------------------------| +| PostgreSQL | 12–15 | Single-node, primary/standby high-availability | +| EDB Postgres Advanced Server | 14–15 | Single node, primary/standby high availability | From 1451fefdaa020933fed68affc0cd218a3290c0ef Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 11 Sep 2023 15:58:42 -0400 Subject: [PATCH 113/255] fixed redirect command --- .../biganimal/release/planning/deployment_options/index.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/planning/deployment_options/index.mdx b/product_docs/docs/biganimal/release/planning/deployment_options/index.mdx index 0be0c798587..b6a91bed1b3 100644 --- a/product_docs/docs/biganimal/release/planning/deployment_options/index.mdx +++ b/product_docs/docs/biganimal/release/planning/deployment_options/index.mdx @@ -1,7 +1,8 @@ --- title: Choosing your deployment option description: Choose to use either your cloud account or BigAnimal's. -redirect: ../overview/deployment_options +redirects: + - /biganimal/release/overview/deployment_options/ --- You have two deployment options with BigAnimal. You can deploy clusters in your cloud account, or you can deploy in BigAnimal's cloud account. From ade5344dbb58d79a53460bed954a30b71581197d Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 11 Sep 2023 16:26:10 -0400 Subject: [PATCH 114/255] BigAnimal: Adding PGE distro for BAH --- .../docs/biganimal/release/planning/choosing_postgres_distro.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx b/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx index d14ee07593a..0c38d064140 100644 --- a/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx +++ b/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx @@ -18,4 +18,5 @@ Postgres distribution and version support varies by [cluster](../overview/02_hig | Postgres distribution | Versions | Cluster type | |------------------------------|----------|------------------------------------------------| | PostgreSQL | 12–15 | Single-node, primary/standby high-availability | +| EDB Postgres Extended Server | 14–15 | Distributed high-availability | | EDB Postgres Advanced Server | 14–15 | Single node, primary/standby high availability | From e79b170ef2a51f383f4a6e256c27d123713dba95 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 11 Sep 2023 16:51:09 -0400 Subject: [PATCH 115/255] added PGE for BYOA and EPAS for BAH --- .../biganimal/release/planning/choosing_postgres_distro.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx b/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx index 0c38d064140..fe6b8197fbc 100644 --- a/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx +++ b/product_docs/docs/biganimal/release/planning/choosing_postgres_distro.mdx @@ -11,6 +11,7 @@ Postgres distribution and version support varies by [cluster](../overview/02_hig |------------------------------|----------|------------------------------------------------| | PostgreSQL | 11–15 | Single-node, primary/standby high-availability | | EDB Postgres Advanced Server | 12–15 | Single-node, primary/standby high-availability | +| EDB Postgres Extended Server | 14–15 | Distributed high-availability | | EDB Postgres Advanced Server | 14–15 | Distributed high-availability | ## Postgres distribution using the BigAnimal cloud account @@ -18,5 +19,6 @@ Postgres distribution and version support varies by [cluster](../overview/02_hig | Postgres distribution | Versions | Cluster type | |------------------------------|----------|------------------------------------------------| | PostgreSQL | 12–15 | Single-node, primary/standby high-availability | -| EDB Postgres Extended Server | 14–15 | Distributed high-availability | | EDB Postgres Advanced Server | 14–15 | Single node, primary/standby high availability | +| EDB Postgres Extended Server | 14–15 | Distributed high-availability | +| EDB Postgres Advanced Server | 14–15 | Distributed high-availability | From 4ab14fef1506bcd892e306b3d048600de5de4c4d Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 11 Sep 2023 17:15:08 -0400 Subject: [PATCH 116/255] BigAnimal: commit scopes recommendation --- .../docs/biganimal/release/overview/02_high_availability.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/overview/02_high_availability.mdx b/product_docs/docs/biganimal/release/overview/02_high_availability.mdx index 22502abe6e1..a2dd68bd6a6 100644 --- a/product_docs/docs/biganimal/release/overview/02_high_availability.mdx +++ b/product_docs/docs/biganimal/release/overview/02_high_availability.mdx @@ -53,7 +53,7 @@ Distributed high-availability clusters are powered by [EDB Postgres Distributed] Distributed high-availability clusters support both EDB Postgres Advanced Server and EDB Postgres Extended Server database distributions. -Distributed high-availability clusters contain one or two data groups. Your data groups can contain either three data nodes or two data nodes and one witness node. One of these data nodes is the leader at any given time, while the rest are shadow nodes. +Distributed high-availability clusters contain one or two data groups. Your data groups can contain either three data nodes or two data nodes and one witness node. One of these data nodes is the leader at any given time, while the rest are shadow nodes. We don't recommend you use two data nodes and one witness node in production unless you use asynchronous [commit scopes](/pgd/latest/durability/commit-scopes/). [PGD Proxy](/pgd/latest/routing/proxy) routes all application traffic to the leader node, which acts as the principal write target to reduce the potential for data conflicts. PGD Proxy leverages a distributed consensus model to determine availability of the data nodes in the cluster. On failure or unavailability of the leader, PGD Proxy elects a new leader and redirects application traffic. Together with the core capabilities of EDB Postgres Distributed, this mechanism of routing application traffic to the leader node enables fast failover and switchover. From 3dfd475b7a4b5f4e589ca4c6a5a18968045cdb33 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Sep 2023 10:32:17 -0400 Subject: [PATCH 117/255] First edits to implement Betsy's copy edits --- install_template/templates/platformBase/base.njk | 2 +- install_template/templates/platformBase/redhat-family.njk | 4 ++-- install_template/templates/platformBase/rhel-7-or-ol-7.njk | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/install_template/templates/platformBase/base.njk b/install_template/templates/platformBase/base.njk index a07a2b4902e..15bfe645bd4 100644 --- a/install_template/templates/platformBase/base.njk +++ b/install_template/templates/platformBase/base.njk @@ -14,7 +14,7 @@ title: Installing {{ product.name }} on {{ platform.name }} {{ platform.arch }} Before you begin the installation process: {% block product_prerequisites %} -- Set up the EDB repository +- Set up the EDB repository. {% block postgresql_preamble %}{% endblock postgresql_preamble %} Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/install_template/templates/platformBase/redhat-family.njk b/install_template/templates/platformBase/redhat-family.njk index 26cb2238d68..f0df9b28c7a 100644 --- a/install_template/templates/platformBase/redhat-family.njk +++ b/install_template/templates/platformBase/redhat-family.njk @@ -1,11 +1,11 @@ {% extends "platformBase/base.njk" %} {% block prerequisites %} -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo {{ packageManager }} {{ packageManagerNoninteractive }} install {{ epelRepo }} ``` {% if platform.arch == "ppc64le" -%} -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/install_template/templates/platformBase/rhel-7-or-ol-7.njk b/install_template/templates/platformBase/rhel-7-or-ol-7.njk index 8546541c049..dd0f955c85f 100644 --- a/install_template/templates/platformBase/rhel-7-or-ol-7.njk +++ b/install_template/templates/platformBase/rhel-7-or-ol-7.njk @@ -4,7 +4,7 @@ {% set epelRepo = "https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm" %} {% block prerequisites %} {{ super() }} -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` From 3acf2fd768b8fb35debaa43103be20ce700c9965 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Sep 2023 11:06:22 -0400 Subject: [PATCH 118/255] Changes needed for Betsy's edits to rhel_7 --- .../_centos-rhel-installcommand.njk | 2 +- .../edb-postgres-advanced-server/base.njk | 22 +++++++++---------- 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/install_template/templates/products/edb-postgres-advanced-server/_centos-rhel-installcommand.njk b/install_template/templates/products/edb-postgres-advanced-server/_centos-rhel-installcommand.njk index 47376f89cba..0c3c4a540e5 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/_centos-rhel-installcommand.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/_centos-rhel-installcommand.njk @@ -1 +1 @@ -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as{{ product.version }}`. \ No newline at end of file +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as{{ product.version }}`. \ No newline at end of file diff --git a/install_template/templates/products/edb-postgres-advanced-server/base.njk b/install_template/templates/products/edb-postgres-advanced-server/base.njk index c04b8572d23..8ad6b911bc4 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/base.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/base.njk @@ -16,7 +16,7 @@ redirects: {% block installCommand %} {{super()}}{% block slesoption %} -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version {{ product.version }}, the package name would be `edb-as{{ product.version }}-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version {{ product.version }}, the package name is `edb-as{{ product.version }}-server`. To install an individual component: @@ -29,11 +29,11 @@ Where `package_name` can be any of the available packages from the [available pa {% block postinstall %} ## Initial configuration {% block debian_ubuntu %} -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. {# this is kinda awful, but gotta deal with the reorg somehow... --jh #} {% set init_cluster_url = "../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode" if product.version >= 15 else "../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode" %} -First you need to initialize and start the database cluster. The `edb-as-{{ product.version | replace(".", "") }}-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode]({{ init_cluster_url }}). +First, you need to initialize and start the database cluster. The `edb-as-{{ product.version | replace(".", "") }}-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode]({{ init_cluster_url }}). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as{{ product.version }}/bin/edb-as-{{ product.version | replace(".", "") }}-setup initdb @@ -41,7 +41,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as{{ product.version }}/bin/edb- sudo systemctl start edb-as-{{ product.version }} ```{% endblock debian_ubuntu %} -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -53,7 +53,7 @@ The server runs with the `peer` or `ident` permission by default. You can change {# this is kinda awful, but gotta deal with the reorg somehow... --jh #} {% set config_doc_path = "database_administration/01_configuration_parameters/01_setting_new_parameters/" if product.version >= 15 else "epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/" %} -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../{{config_doc_path}}#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../{{config_doc_path}}#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -61,9 +61,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -72,7 +72,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -81,7 +81,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -91,7 +91,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -105,7 +105,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; From d69547a635eef596fb7e34fbc6c9d2be25ec0fbc Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Sep 2023 11:17:34 -0400 Subject: [PATCH 119/255] remaining edits from Betsy --- install_template/templates/platformBase/ppc64le_index.njk | 2 +- install_template/templates/platformBase/sles-12.njk | 4 ++-- install_template/templates/platformBase/x86_64_index.njk | 2 +- .../products/edb-postgres-advanced-server/rhel-8-or-ol-8.njk | 4 ++-- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/install_template/templates/platformBase/ppc64le_index.njk b/install_template/templates/platformBase/ppc64le_index.njk index 468a0145dce..d114bf79bd0 100644 --- a/install_template/templates/platformBase/ppc64le_index.njk +++ b/install_template/templates/platformBase/ppc64le_index.njk @@ -17,7 +17,7 @@ navigation: {% endblock navigation %} --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: {% block install %} {% if osVersions.hasFamily("RHEL") %} diff --git a/install_template/templates/platformBase/sles-12.njk b/install_template/templates/platformBase/sles-12.njk index f1cc221cfb3..eaf073a97f6 100644 --- a/install_template/templates/platformBase/sles-12.njk +++ b/install_template/templates/platformBase/sles-12.njk @@ -7,7 +7,7 @@ {% endblock repocheck %} {% block prerequisites %} {% block other_platform_prerequesites_shell %}{% endblock other_platform_prerequesites_shell %} -- Activate the required SUSE module +- Activate the required SUSE module: ```shell {%- filter indent(2) -%} {% block activateSUSEmodule %} @@ -16,7 +16,7 @@ sudo SUSEConnect -p sle-sdk/12.5/{{ platform.arch }} {% endblock activateSUSEmodule %} {%- endfilter %} ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/install_template/templates/platformBase/x86_64_index.njk b/install_template/templates/platformBase/x86_64_index.njk index 81a62b5d5a0..a1afaa42d22 100644 --- a/install_template/templates/platformBase/x86_64_index.njk +++ b/install_template/templates/platformBase/x86_64_index.njk @@ -26,7 +26,7 @@ navigation: {% endblock navigation %} --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: {% if osVersions.hasFamily("RHEL") %} ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/install_template/templates/products/edb-postgres-advanced-server/rhel-8-or-ol-8.njk b/install_template/templates/products/edb-postgres-advanced-server/rhel-8-or-ol-8.njk index ce23ce51d69..45e3e78251c 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/rhel-8-or-ol-8.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/rhel-8-or-ol-8.njk @@ -2,12 +2,12 @@ {% set platformBaseTemplate = "rhel-8-or-ol-8" %} {% block prerequisites %} {{ super() }} -- If you are also installing PostGIS, enable additional repositories to resolve dependencies: +- If you're also installing PostGIS, enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` !!!note - If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-8-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + If you're using a public cloud RHEL image, `subscription manager` might not be enabled. Enabling it might incur unnecessary charges. Equivalent packages might be available under a different name, such as `codeready-builder-for-rhel-8-rhui-rpms`. To determine how to install `codeready-builder`, consult the documentation for the RHEL image you're using. {% endblock prerequisites %} {% block installCommand %} {{ super() }} From 1f2051dc47c8f31c68ef4c7a229db92f75b5a6a4 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Sep 2023 11:59:55 -0400 Subject: [PATCH 120/255] minor edits for consistency across products in install topics --- install_template/templates/products/failover-manager/base.njk | 2 +- .../products/postgres-enterprise-manager-server/base.njk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/install_template/templates/products/failover-manager/base.njk b/install_template/templates/products/failover-manager/base.njk index 003ba4f8859..7004f34dd2d 100644 --- a/install_template/templates/products/failover-manager/base.njk +++ b/install_template/templates/products/failover-manager/base.njk @@ -13,7 +13,7 @@ redirects: {% endblock frontmatter %} {% block product_prerequisites %} -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) diff --git a/install_template/templates/products/postgres-enterprise-manager-server/base.njk b/install_template/templates/products/postgres-enterprise-manager-server/base.njk index dc748eda2e5..6bce2400b34 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/base.njk @@ -18,7 +18,7 @@ redirects: {% endblock frontmatter %} {% block product_prerequisites %} -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. {%- filter indent(2) -%} From f88cc3556de565ff000445b70baa5387e190a6ec Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 11 Sep 2023 10:23:15 -0400 Subject: [PATCH 121/255] Assorted changes to install templates to match Betsy's edits --- .../templates/platformBase/almalinux-8-or-rocky-linux-8.njk | 2 +- .../templates/platformBase/almalinux-9-or-rocky-linux-9.njk | 2 +- .../templates/products/migration-toolkit/rhel-7-or-ol-7.njk | 2 +- .../products/mysql-foreign-data-wrapper/centos-7.njk | 4 ++-- .../products/mysql-foreign-data-wrapper/debian-10.njk | 4 ++-- .../products/mysql-foreign-data-wrapper/debian-11.njk | 2 +- .../products/mysql-foreign-data-wrapper/rhel-7-or-ol-7.njk | 4 ++-- .../templates/products/mysql-foreign-data-wrapper/sles-12.njk | 4 ++-- .../templates/products/mysql-foreign-data-wrapper/sles-15.njk | 4 ++-- .../products/mysql-foreign-data-wrapper/ubuntu-18.04.njk | 2 +- .../products/postgresql/almalinux-8-or-rocky-linux-8.njk | 4 ++-- .../products/postgresql/almalinux-9-or-rocky-linux-9.njk | 4 ++-- .../templates/products/postgresql/rhel-8-or-ol-8.njk | 4 ++-- .../templates/products/postgresql/rhel-9-or-ol-9.njk | 4 ++-- 14 files changed, 23 insertions(+), 23 deletions(-) diff --git a/install_template/templates/platformBase/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/platformBase/almalinux-8-or-rocky-linux-8.njk index 0d19ec4d712..27240325451 100644 --- a/install_template/templates/platformBase/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/platformBase/almalinux-8-or-rocky-linux-8.njk @@ -4,7 +4,7 @@ {% set epelRepo = "epel-release" %} {% block prerequisites %} {{ super() }} -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/install_template/templates/platformBase/almalinux-9-or-rocky-linux-9.njk b/install_template/templates/platformBase/almalinux-9-or-rocky-linux-9.njk index 0d19ec4d712..27240325451 100644 --- a/install_template/templates/platformBase/almalinux-9-or-rocky-linux-9.njk +++ b/install_template/templates/platformBase/almalinux-9-or-rocky-linux-9.njk @@ -4,7 +4,7 @@ {% set epelRepo = "epel-release" %} {% block prerequisites %} {{ super() }} -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/install_template/templates/products/migration-toolkit/rhel-7-or-ol-7.njk b/install_template/templates/products/migration-toolkit/rhel-7-or-ol-7.njk index c57ac1397a8..8797e6d5da5 100644 --- a/install_template/templates/products/migration-toolkit/rhel-7-or-ol-7.njk +++ b/install_template/templates/products/migration-toolkit/rhel-7-or-ol-7.njk @@ -1,7 +1,7 @@ {% extends "products/migration-toolkit/base.njk" %} {% set platformBaseTemplate = "rhel-7-or-ol-7" %} {% block prerequisites %} -- Address other prerequisites +- Address other prerequisites: ```shell # Install the EPEL repository: sudo {{ packageManager }} -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/centos-7.njk b/install_template/templates/products/mysql-foreign-data-wrapper/centos-7.njk index 02a0ae1d5ba..a910a4bd21a 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/centos-7.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/centos-7.njk @@ -2,11 +2,11 @@ {% set platformBaseTemplate = "centos-7" %} {% block prerequisites %} {{ super() }} -- Download and install the MySQL repo +- Download and install the MySQL repo: ```shell sudo yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm ``` -- Enable the MySQL repo +- Enable the MySQL repo: ```shell # For MySQL 8: sudo yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as-mysql8_fdw diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk b/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk index 953a63f94af..17aef377faf 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk @@ -2,11 +2,11 @@ {% set platformBaseTemplate = "debian-10" %} {% block prerequisites %} {{ super() }} -- Download the GPG key to your APT keyring directly using the apt-key utility +- Download the GPG key to your APT keyring directly using the apt-key utility: ```shell sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 3A79BD29 ``` -- Install and configure the MySQL repo +- Install and configure the MySQL repo: ```shell # For MySQL 8: sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-8.0" | sudo tee /etc/apt/sources.list.d/mysql.list diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/debian-11.njk b/install_template/templates/products/mysql-foreign-data-wrapper/debian-11.njk index ca8a17a58a2..64b0aedfd29 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/debian-11.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/debian-11.njk @@ -2,7 +2,7 @@ {% set platformBaseTemplate = "debian-11" %} {% block prerequisites %} {{ super() }} -- Address other prerequisites +- Address other prerequisites: ```shell # Download the GPG key to your APT keyring directly using the apt-key utility: sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 3A79BD29 diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/rhel-7-or-ol-7.njk b/install_template/templates/products/mysql-foreign-data-wrapper/rhel-7-or-ol-7.njk index ed2f18695d5..99cd1b5c547 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/rhel-7-or-ol-7.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/rhel-7-or-ol-7.njk @@ -2,11 +2,11 @@ {% set platformBaseTemplate = "rhel-7-or-ol-7" %} {% block prerequisites %} {{ super() }} -- Download and install the MYSQL repo +- Download and install the MYSQL repo: ```shell sudo yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm ``` -- Enable the MYSQL repo +- Enable the MYSQL repo: ```shell # For MySQL 8: sudo yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as-mysql8_fdw diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/sles-12.njk b/install_template/templates/products/mysql-foreign-data-wrapper/sles-12.njk index b2b37c9fe1a..717f4a1069a 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/sles-12.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/sles-12.njk @@ -1,12 +1,12 @@ {% extends "products/mysql-foreign-data-wrapper/base.njk" %} {% set platformBaseTemplate = "sles-12" %} {% block other_platform_prerequesites_shell %} -- Install the MySQL community repository +- Install the MySQL community repository: ```shell sudo wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm rpm --import /etc/RPM-GPG-KEY-mysql-2022 ``` -- Enable the MySQL8 repository and disable the MySQL 5 repository +- Enable the MySQL8 repository and disable the MySQL 5 repository: ```shell sudo zypper modifyrepo -e mysql80-community sudo zypper modifyrepo -d mysql57-community diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/sles-15.njk b/install_template/templates/products/mysql-foreign-data-wrapper/sles-15.njk index 5f55a49d9b4..9f4eb01d190 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/sles-15.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/sles-15.njk @@ -1,12 +1,12 @@ {% extends "products/mysql-foreign-data-wrapper/base.njk" %} {% set platformBaseTemplate = "sles-15" %} {% block other_platform_prerequesites_shell %} -- Install the MySQL community repository +- Install the MySQL community repository: ```shell sudo wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm rpm --import /etc/RPM-GPG-KEY-mysql-2022 ``` -- Enable the MySQL8 repository and disable the MySQL 5 repository +- Enable the MySQL8 repository and disable the MySQL 5 repository: ```shell sudo zypper modifyrepo -e mysql80-community sudo zypper modifyrepo -d mysql57-community diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/ubuntu-18.04.njk b/install_template/templates/products/mysql-foreign-data-wrapper/ubuntu-18.04.njk index f8524f04a99..685ce6450ef 100644 --- a/install_template/templates/products/mysql-foreign-data-wrapper/ubuntu-18.04.njk +++ b/install_template/templates/products/mysql-foreign-data-wrapper/ubuntu-18.04.njk @@ -2,7 +2,7 @@ {% set platformBaseTemplate = "ubuntu-18.04" %} {% block prerequisites %} {{ super() }} -- Address other prerequisites +- Address other prerequisites: ```shell # Download the GPG key to your APT keyring directly using the apt-key utility: sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 3A79BD29 diff --git a/install_template/templates/products/postgresql/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/postgresql/almalinux-8-or-rocky-linux-8.njk index ffa6c0ec182..7b887f59c62 100644 --- a/install_template/templates/products/postgresql/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/postgresql/almalinux-8-or-rocky-linux-8.njk @@ -3,11 +3,11 @@ {% set packageManager = "dnf" %} {% block prerequisites %} {{ super() }} -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell dnf config-manager --set-enabled powertools ``` -- Disable the built-in PostgreSQL module +- Disable the built-in PostgreSQL module: ```shell dnf -qy module disable postgresql ``` diff --git a/install_template/templates/products/postgresql/almalinux-9-or-rocky-linux-9.njk b/install_template/templates/products/postgresql/almalinux-9-or-rocky-linux-9.njk index 66fbc3f403b..8ddeed61ba9 100644 --- a/install_template/templates/products/postgresql/almalinux-9-or-rocky-linux-9.njk +++ b/install_template/templates/products/postgresql/almalinux-9-or-rocky-linux-9.njk @@ -3,11 +3,11 @@ {% set packageManager = "dnf" %} {% block prerequisites %} {{ super() }} -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell dnf config-manager --set-enabled powertools ``` -- Disable the built-in PostgreSQL module +- Disable the built-in PostgreSQL module: ```shell dnf -qy module disable postgresql ``` diff --git a/install_template/templates/products/postgresql/rhel-8-or-ol-8.njk b/install_template/templates/products/postgresql/rhel-8-or-ol-8.njk index e0d423c0f84..ba6e166740e 100644 --- a/install_template/templates/products/postgresql/rhel-8-or-ol-8.njk +++ b/install_template/templates/products/postgresql/rhel-8-or-ol-8.njk @@ -2,11 +2,11 @@ {% set platformBaseTemplate = "rhel-8-or-ol-8" %} {% block prerequisites %} {{ super() }} -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` -- Disable the built-in PostgreSQL module +- Disable the built-in PostgreSQL module: ```shell dnf -qy module disable postgresql ``` diff --git a/install_template/templates/products/postgresql/rhel-9-or-ol-9.njk b/install_template/templates/products/postgresql/rhel-9-or-ol-9.njk index 6a1aaa0763e..7ecad143179 100644 --- a/install_template/templates/products/postgresql/rhel-9-or-ol-9.njk +++ b/install_template/templates/products/postgresql/rhel-9-or-ol-9.njk @@ -2,11 +2,11 @@ {% set platformBaseTemplate = "rhel-9-or-ol-9" %} {% block prerequisites %} {{ super() }} -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` -- Disable the built-in PostgreSQL module +- Disable the built-in PostgreSQL module: ```shell dnf -qy module disable postgresql ``` From 2a42046416d2f6f7416c00b982b097af8a81420a Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 11 Sep 2023 10:24:53 -0400 Subject: [PATCH 122/255] Deployed changes to install topics based on template changes --- .../installing/linux_ppc64le/index.mdx | 2 +- .../linux_ppc64le/postgresql_rhel_8.mdx | 10 +++--- .../linux_ppc64le/postgresql_rhel_9.mdx | 10 +++--- .../linux_ppc64le/postgresql_sles_12.mdx | 6 ++-- .../linux_ppc64le/postgresql_sles_15.mdx | 6 ++-- .../installing/linux_x86_64/index.mdx | 2 +- .../linux_x86_64/postgresql_centos_7.mdx | 4 +-- .../linux_x86_64/postgresql_debian_10.mdx | 2 +- .../linux_x86_64/postgresql_debian_11.mdx | 2 +- .../linux_x86_64/postgresql_other_linux_8.mdx | 10 +++--- .../linux_x86_64/postgresql_other_linux_9.mdx | 10 +++--- .../linux_x86_64/postgresql_rhel_7.mdx | 6 ++-- .../linux_x86_64/postgresql_rhel_8.mdx | 8 ++--- .../linux_x86_64/postgresql_rhel_9.mdx | 8 ++--- .../linux_x86_64/postgresql_sles_12.mdx | 6 ++-- .../linux_x86_64/postgresql_sles_15.mdx | 6 ++-- .../linux_x86_64/postgresql_ubuntu_18.mdx | 2 +- .../linux_x86_64/postgresql_ubuntu_20.mdx | 2 +- .../linux_x86_64/postgresql_ubuntu_22.mdx | 2 +- .../linux_ppc64le/edbplus_rhel_8.mdx | 2 +- .../linux_ppc64le/edbplus_rhel_9.mdx | 2 +- .../linux_ppc64le/edbplus_sles_12.mdx | 6 ++-- .../linux_ppc64le/edbplus_sles_15.mdx | 6 ++-- .../41/installing/linux_ppc64le/index.mdx | 2 +- .../linux_x86_64/edbplus_centos_7.mdx | 4 +-- .../linux_x86_64/edbplus_debian_10.mdx | 2 +- .../linux_x86_64/edbplus_debian_11.mdx | 2 +- .../linux_x86_64/edbplus_other_linux_8.mdx | 2 +- .../linux_x86_64/edbplus_other_linux_9.mdx | 2 +- .../linux_x86_64/edbplus_rhel_7.mdx | 6 ++-- .../linux_x86_64/edbplus_rhel_8.mdx | 2 +- .../linux_x86_64/edbplus_rhel_9.mdx | 2 +- .../linux_x86_64/edbplus_sles_12.mdx | 6 ++-- .../linux_x86_64/edbplus_sles_15.mdx | 6 ++-- .../linux_x86_64/edbplus_ubuntu_18.mdx | 2 +- .../linux_x86_64/edbplus_ubuntu_20.mdx | 2 +- .../linux_x86_64/edbplus_ubuntu_22.mdx | 2 +- .../41/installing/linux_x86_64/index.mdx | 2 +- .../4/installing/linux_ppc64le/efm_rhel_8.mdx | 8 ++--- .../4/installing/linux_ppc64le/efm_rhel_9.mdx | 8 ++--- .../installing/linux_ppc64le/efm_sles_12.mdx | 8 ++--- .../installing/linux_ppc64le/efm_sles_15.mdx | 8 ++--- .../efm/4/installing/linux_ppc64le/index.mdx | 2 +- .../installing/linux_x86_64/efm_centos_7.mdx | 6 ++-- .../installing/linux_x86_64/efm_debian_10.mdx | 4 +-- .../installing/linux_x86_64/efm_debian_11.mdx | 4 +-- .../linux_x86_64/efm_other_linux_8.mdx | 8 ++--- .../linux_x86_64/efm_other_linux_9.mdx | 8 ++--- .../4/installing/linux_x86_64/efm_rhel_7.mdx | 8 ++--- .../4/installing/linux_x86_64/efm_rhel_8.mdx | 6 ++-- .../4/installing/linux_x86_64/efm_rhel_9.mdx | 6 ++-- .../4/installing/linux_x86_64/efm_sles_12.mdx | 8 ++--- .../4/installing/linux_x86_64/efm_sles_15.mdx | 8 ++--- .../installing/linux_x86_64/efm_ubuntu_18.mdx | 4 +-- .../installing/linux_x86_64/efm_ubuntu_20.mdx | 4 +-- .../installing/linux_x86_64/efm_ubuntu_22.mdx | 4 +-- .../efm/4/installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_ppc64le/epas_rhel_7.mdx | 32 ++++++++--------- .../installing/linux_ppc64le/epas_rhel_8.mdx | 34 +++++++++---------- .../installing/linux_ppc64le/epas_rhel_9.mdx | 30 ++++++++-------- .../installing/linux_ppc64le/epas_sles_12.mdx | 26 +++++++------- .../installing/linux_ppc64le/epas_sles_15.mdx | 26 +++++++------- .../11/installing/linux_ppc64le/index.mdx | 2 +- .../installing/linux_x86_64/epas_centos_7.mdx | 28 +++++++-------- .../linux_x86_64/epas_debian_10.mdx | 20 +++++------ .../linux_x86_64/epas_debian_11.mdx | 20 +++++------ .../linux_x86_64/epas_other_linux_8.mdx | 30 ++++++++-------- .../linux_x86_64/epas_other_linux_9.mdx | 30 ++++++++-------- .../installing/linux_x86_64/epas_rhel_7.mdx | 30 ++++++++-------- .../installing/linux_x86_64/epas_rhel_8.mdx | 32 ++++++++--------- .../installing/linux_x86_64/epas_rhel_9.mdx | 28 +++++++-------- .../installing/linux_x86_64/epas_sles_12.mdx | 26 +++++++------- .../installing/linux_x86_64/epas_sles_15.mdx | 26 +++++++------- .../linux_x86_64/epas_ubuntu_18.mdx | 20 +++++------ .../linux_x86_64/epas_ubuntu_20.mdx | 20 +++++------ .../linux_x86_64/epas_ubuntu_22.mdx | 20 +++++------ .../epas/11/installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_ppc64le/epas_rhel_7.mdx | 32 ++++++++--------- .../installing/linux_ppc64le/epas_rhel_8.mdx | 34 +++++++++---------- .../installing/linux_ppc64le/epas_rhel_9.mdx | 30 ++++++++-------- .../installing/linux_ppc64le/epas_sles_12.mdx | 26 +++++++------- .../installing/linux_ppc64le/epas_sles_15.mdx | 26 +++++++------- .../12/installing/linux_ppc64le/index.mdx | 2 +- .../installing/linux_x86_64/epas_centos_7.mdx | 28 +++++++-------- .../linux_x86_64/epas_debian_10.mdx | 20 +++++------ .../linux_x86_64/epas_debian_11.mdx | 20 +++++------ .../linux_x86_64/epas_other_linux_8.mdx | 30 ++++++++-------- .../linux_x86_64/epas_other_linux_9.mdx | 30 ++++++++-------- .../installing/linux_x86_64/epas_rhel_7.mdx | 30 ++++++++-------- .../installing/linux_x86_64/epas_rhel_8.mdx | 32 ++++++++--------- .../installing/linux_x86_64/epas_rhel_9.mdx | 28 +++++++-------- .../installing/linux_x86_64/epas_sles_12.mdx | 26 +++++++------- .../installing/linux_x86_64/epas_sles_15.mdx | 26 +++++++------- .../linux_x86_64/epas_ubuntu_18.mdx | 20 +++++------ .../linux_x86_64/epas_ubuntu_20.mdx | 20 +++++------ .../linux_x86_64/epas_ubuntu_22.mdx | 20 +++++------ .../epas/12/installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_ppc64le/epas_rhel_7.mdx | 32 ++++++++--------- .../installing/linux_ppc64le/epas_rhel_8.mdx | 34 +++++++++---------- .../installing/linux_ppc64le/epas_rhel_9.mdx | 30 ++++++++-------- .../installing/linux_ppc64le/epas_sles_12.mdx | 26 +++++++------- .../installing/linux_ppc64le/epas_sles_15.mdx | 26 +++++++------- .../13/installing/linux_ppc64le/index.mdx | 2 +- .../installing/linux_x86_64/epas_centos_7.mdx | 28 +++++++-------- .../linux_x86_64/epas_debian_10.mdx | 20 +++++------ .../linux_x86_64/epas_debian_11.mdx | 20 +++++------ .../linux_x86_64/epas_other_linux_8.mdx | 30 ++++++++-------- .../linux_x86_64/epas_other_linux_9.mdx | 30 ++++++++-------- .../installing/linux_x86_64/epas_rhel_7.mdx | 30 ++++++++-------- .../installing/linux_x86_64/epas_rhel_8.mdx | 32 ++++++++--------- .../installing/linux_x86_64/epas_rhel_9.mdx | 28 +++++++-------- .../installing/linux_x86_64/epas_sles_12.mdx | 26 +++++++------- .../installing/linux_x86_64/epas_sles_15.mdx | 26 +++++++------- .../linux_x86_64/epas_ubuntu_18.mdx | 20 +++++------ .../linux_x86_64/epas_ubuntu_20.mdx | 20 +++++------ .../linux_x86_64/epas_ubuntu_22.mdx | 20 +++++------ .../epas/13/installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_ppc64le/epas_rhel_7.mdx | 32 ++++++++--------- .../installing/linux_ppc64le/epas_rhel_8.mdx | 34 +++++++++---------- .../installing/linux_ppc64le/epas_rhel_9.mdx | 30 ++++++++-------- .../installing/linux_ppc64le/epas_sles_12.mdx | 26 +++++++------- .../installing/linux_ppc64le/epas_sles_15.mdx | 26 +++++++------- .../14/installing/linux_ppc64le/index.mdx | 2 +- .../installing/linux_x86_64/epas_centos_7.mdx | 28 +++++++-------- .../linux_x86_64/epas_debian_10.mdx | 20 +++++------ .../linux_x86_64/epas_debian_11.mdx | 20 +++++------ .../linux_x86_64/epas_other_linux_8.mdx | 30 ++++++++-------- .../linux_x86_64/epas_other_linux_9.mdx | 30 ++++++++-------- .../installing/linux_x86_64/epas_rhel_7.mdx | 30 ++++++++-------- .../installing/linux_x86_64/epas_rhel_8.mdx | 32 ++++++++--------- .../installing/linux_x86_64/epas_rhel_9.mdx | 28 +++++++-------- .../installing/linux_x86_64/epas_sles_12.mdx | 26 +++++++------- .../installing/linux_x86_64/epas_sles_15.mdx | 26 +++++++------- .../linux_x86_64/epas_ubuntu_18.mdx | 20 +++++------ .../linux_x86_64/epas_ubuntu_20.mdx | 20 +++++------ .../linux_x86_64/epas_ubuntu_22.mdx | 20 +++++------ .../epas/14/installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_ppc64le/epas_rhel_7.mdx | 32 ++++++++--------- .../installing/linux_ppc64le/epas_rhel_8.mdx | 34 +++++++++---------- .../installing/linux_ppc64le/epas_rhel_9.mdx | 30 ++++++++-------- .../installing/linux_ppc64le/epas_sles_12.mdx | 26 +++++++------- .../installing/linux_ppc64le/epas_sles_15.mdx | 26 +++++++------- .../15/installing/linux_ppc64le/index.mdx | 2 +- .../installing/linux_x86_64/epas_centos_7.mdx | 28 +++++++-------- .../linux_x86_64/epas_debian_10.mdx | 20 +++++------ .../linux_x86_64/epas_debian_11.mdx | 20 +++++------ .../linux_x86_64/epas_other_linux_8.mdx | 30 ++++++++-------- .../linux_x86_64/epas_other_linux_9.mdx | 30 ++++++++-------- .../installing/linux_x86_64/epas_rhel_7.mdx | 30 ++++++++-------- .../installing/linux_x86_64/epas_rhel_8.mdx | 32 ++++++++--------- .../installing/linux_x86_64/epas_rhel_9.mdx | 28 +++++++-------- .../installing/linux_x86_64/epas_sles_12.mdx | 26 +++++++------- .../installing/linux_x86_64/epas_sles_15.mdx | 26 +++++++------- .../linux_x86_64/epas_ubuntu_18.mdx | 20 +++++------ .../linux_x86_64/epas_ubuntu_20.mdx | 20 +++++------ .../linux_x86_64/epas_ubuntu_22.mdx | 20 +++++------ .../epas/15/installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_ppc64le/eprs_rhel_8.mdx | 2 +- .../installing/linux_ppc64le/eprs_rhel_9.mdx | 2 +- .../installing/linux_ppc64le/eprs_sles_12.mdx | 6 ++-- .../installing/linux_ppc64le/eprs_sles_15.mdx | 6 ++-- .../eprs/7/installing/linux_ppc64le/index.mdx | 2 +- .../installing/linux_x86_64/eprs_centos_7.mdx | 4 +-- .../linux_x86_64/eprs_debian_10.mdx | 2 +- .../linux_x86_64/eprs_debian_11.mdx | 2 +- .../linux_x86_64/eprs_other_linux_8.mdx | 2 +- .../linux_x86_64/eprs_other_linux_9.mdx | 2 +- .../7/installing/linux_x86_64/eprs_rhel_7.mdx | 6 ++-- .../7/installing/linux_x86_64/eprs_rhel_8.mdx | 2 +- .../7/installing/linux_x86_64/eprs_rhel_9.mdx | 2 +- .../installing/linux_x86_64/eprs_sles_12.mdx | 6 ++-- .../installing/linux_x86_64/eprs_sles_15.mdx | 6 ++-- .../linux_x86_64/eprs_ubuntu_18.mdx | 2 +- .../linux_x86_64/eprs_ubuntu_20.mdx | 2 +- .../linux_x86_64/eprs_ubuntu_22.mdx | 2 +- .../eprs/7/installing/linux_x86_64/index.mdx | 2 +- .../linux_ppc64le/hadoop_rhel_8.mdx | 6 ++-- .../linux_ppc64le/hadoop_rhel_9.mdx | 6 ++-- .../linux_ppc64le/hadoop_sles_12.mdx | 6 ++-- .../linux_ppc64le/hadoop_sles_15.mdx | 6 ++-- .../2/installing/linux_ppc64le/index.mdx | 2 +- .../linux_x86_64/hadoop_centos_7.mdx | 4 +-- .../linux_x86_64/hadoop_debian_10.mdx | 2 +- .../linux_x86_64/hadoop_debian_11.mdx | 2 +- .../linux_x86_64/hadoop_other_linux_8.mdx | 6 ++-- .../linux_x86_64/hadoop_other_linux_9.mdx | 6 ++-- .../installing/linux_x86_64/hadoop_rhel_7.mdx | 6 ++-- .../installing/linux_x86_64/hadoop_rhel_8.mdx | 4 +-- .../installing/linux_x86_64/hadoop_rhel_9.mdx | 4 +-- .../linux_x86_64/hadoop_sles_12.mdx | 6 ++-- .../linux_x86_64/hadoop_sles_15.mdx | 6 ++-- .../linux_x86_64/hadoop_ubuntu_18.mdx | 2 +- .../linux_x86_64/hadoop_ubuntu_20.mdx | 2 +- .../linux_x86_64/hadoop_ubuntu_22.mdx | 2 +- .../2/installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_ppc64le/index.mdx | 2 +- .../installing/linux_ppc64le/jdbc_rhel_8.mdx | 6 ++-- .../installing/linux_ppc64le/jdbc_rhel_9.mdx | 6 ++-- .../installing/linux_ppc64le/jdbc_sles_12.mdx | 6 ++-- .../installing/linux_ppc64le/jdbc_sles_15.mdx | 6 ++-- .../installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_x86_64/jdbc_centos_7.mdx | 4 +-- .../linux_x86_64/jdbc_debian_10.mdx | 2 +- .../linux_x86_64/jdbc_debian_11.mdx | 2 +- .../linux_x86_64/jdbc_other_linux_8.mdx | 6 ++-- .../linux_x86_64/jdbc_other_linux_9.mdx | 6 ++-- .../installing/linux_x86_64/jdbc_rhel_7.mdx | 6 ++-- .../installing/linux_x86_64/jdbc_rhel_8.mdx | 4 +-- .../installing/linux_x86_64/jdbc_rhel_9.mdx | 4 +-- .../installing/linux_x86_64/jdbc_sles_12.mdx | 6 ++-- .../installing/linux_x86_64/jdbc_sles_15.mdx | 6 ++-- .../linux_x86_64/jdbc_ubuntu_18.mdx | 2 +- .../linux_x86_64/jdbc_ubuntu_20.mdx | 2 +- .../linux_x86_64/jdbc_ubuntu_22.mdx | 2 +- .../55/installing/linux_ppc64le/index.mdx | 2 +- .../installing/linux_ppc64le/mtk_rhel_8.mdx | 2 +- .../installing/linux_ppc64le/mtk_rhel_9.mdx | 2 +- .../installing/linux_ppc64le/mtk_sles_12.mdx | 6 ++-- .../installing/linux_ppc64le/mtk_sles_15.mdx | 6 ++-- .../55/installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_x86_64/mtk_centos_7.mdx | 4 +-- .../installing/linux_x86_64/mtk_debian_10.mdx | 2 +- .../installing/linux_x86_64/mtk_debian_11.mdx | 2 +- .../linux_x86_64/mtk_other_linux_8.mdx | 2 +- .../linux_x86_64/mtk_other_linux_9.mdx | 2 +- .../55/installing/linux_x86_64/mtk_rhel_7.mdx | 4 +-- .../55/installing/linux_x86_64/mtk_rhel_8.mdx | 2 +- .../55/installing/linux_x86_64/mtk_rhel_9.mdx | 2 +- .../installing/linux_x86_64/mtk_sles_12.mdx | 6 ++-- .../installing/linux_x86_64/mtk_sles_15.mdx | 6 ++-- .../installing/linux_x86_64/mtk_ubuntu_18.mdx | 2 +- .../installing/linux_x86_64/mtk_ubuntu_20.mdx | 2 +- .../installing/linux_x86_64/mtk_ubuntu_22.mdx | 2 +- .../5/installing/linux_ppc64le/index.mdx | 2 +- .../installing/linux_ppc64le/mongo_rhel_8.mdx | 6 ++-- .../installing/linux_ppc64le/mongo_rhel_9.mdx | 6 ++-- .../linux_ppc64le/mongo_sles_12.mdx | 6 ++-- .../linux_ppc64le/mongo_sles_15.mdx | 6 ++-- .../5/installing/linux_x86_64/index.mdx | 2 +- .../linux_x86_64/mongo_centos_7.mdx | 4 +-- .../linux_x86_64/mongo_debian_10.mdx | 2 +- .../linux_x86_64/mongo_debian_11.mdx | 2 +- .../linux_x86_64/mongo_other_linux_8.mdx | 6 ++-- .../linux_x86_64/mongo_other_linux_9.mdx | 6 ++-- .../installing/linux_x86_64/mongo_rhel_7.mdx | 6 ++-- .../installing/linux_x86_64/mongo_rhel_8.mdx | 4 +-- .../installing/linux_x86_64/mongo_rhel_9.mdx | 4 +-- .../installing/linux_x86_64/mongo_sles_12.mdx | 6 ++-- .../installing/linux_x86_64/mongo_sles_15.mdx | 6 ++-- .../linux_x86_64/mongo_ubuntu_18.mdx | 2 +- .../linux_x86_64/mongo_ubuntu_20.mdx | 2 +- .../linux_x86_64/mongo_ubuntu_22.mdx | 2 +- .../2/installing/linux_ppc64le/index.mdx | 2 +- .../installing/linux_ppc64le/mysql_rhel_8.mdx | 6 ++-- .../installing/linux_ppc64le/mysql_rhel_9.mdx | 6 ++-- .../linux_ppc64le/mysql_sles_12.mdx | 10 +++--- .../linux_ppc64le/mysql_sles_15.mdx | 10 +++--- .../2/installing/linux_x86_64/index.mdx | 2 +- .../linux_x86_64/mysql_centos_7.mdx | 8 ++--- .../linux_x86_64/mysql_debian_10.mdx | 6 ++-- .../linux_x86_64/mysql_debian_11.mdx | 4 +-- .../linux_x86_64/mysql_other_linux_8.mdx | 6 ++-- .../linux_x86_64/mysql_other_linux_9.mdx | 6 ++-- .../installing/linux_x86_64/mysql_rhel_7.mdx | 10 +++--- .../installing/linux_x86_64/mysql_rhel_8.mdx | 4 +-- .../installing/linux_x86_64/mysql_rhel_9.mdx | 4 +-- .../installing/linux_x86_64/mysql_sles_12.mdx | 10 +++--- .../installing/linux_x86_64/mysql_sles_15.mdx | 10 +++--- .../linux_x86_64/mysql_ubuntu_18.mdx | 4 +-- .../linux_x86_64/mysql_ubuntu_20.mdx | 2 +- .../linux_x86_64/mysql_ubuntu_22.mdx | 2 +- .../14/installing/linux_ppc64le/index.mdx | 2 +- .../installing/linux_ppc64le/ocl_rhel_8.mdx | 6 ++-- .../installing/linux_ppc64le/ocl_rhel_9.mdx | 6 ++-- .../installing/linux_ppc64le/ocl_sles_12.mdx | 6 ++-- .../installing/linux_ppc64le/ocl_sles_15.mdx | 6 ++-- .../14/installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_x86_64/ocl_centos_7.mdx | 4 +-- .../installing/linux_x86_64/ocl_debian_10.mdx | 2 +- .../installing/linux_x86_64/ocl_debian_11.mdx | 2 +- .../linux_x86_64/ocl_other_linux_8.mdx | 6 ++-- .../linux_x86_64/ocl_other_linux_9.mdx | 6 ++-- .../14/installing/linux_x86_64/ocl_rhel_7.mdx | 6 ++-- .../14/installing/linux_x86_64/ocl_rhel_8.mdx | 4 +-- .../14/installing/linux_x86_64/ocl_rhel_9.mdx | 4 +-- .../installing/linux_x86_64/ocl_sles_12.mdx | 6 ++-- .../installing/linux_x86_64/ocl_sles_15.mdx | 6 ++-- .../installing/linux_x86_64/ocl_ubuntu_18.mdx | 2 +- .../installing/linux_x86_64/ocl_ubuntu_20.mdx | 2 +- .../15/installing/linux_ppc64le/index.mdx | 2 +- .../installing/linux_ppc64le/ocl_rhel_8.mdx | 6 ++-- .../installing/linux_ppc64le/ocl_rhel_9.mdx | 6 ++-- .../installing/linux_ppc64le/ocl_sles_12.mdx | 6 ++-- .../installing/linux_ppc64le/ocl_sles_15.mdx | 6 ++-- .../15/installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_x86_64/ocl_centos_7.mdx | 4 +-- .../installing/linux_x86_64/ocl_debian_10.mdx | 2 +- .../installing/linux_x86_64/ocl_debian_11.mdx | 2 +- .../linux_x86_64/ocl_other_linux_8.mdx | 6 ++-- .../linux_x86_64/ocl_other_linux_9.mdx | 6 ++-- .../15/installing/linux_x86_64/ocl_rhel_7.mdx | 6 ++-- .../15/installing/linux_x86_64/ocl_rhel_8.mdx | 4 +-- .../15/installing/linux_x86_64/ocl_rhel_9.mdx | 4 +-- .../installing/linux_x86_64/ocl_sles_12.mdx | 6 ++-- .../installing/linux_x86_64/ocl_sles_15.mdx | 6 ++-- .../installing/linux_x86_64/ocl_ubuntu_18.mdx | 2 +- .../installing/linux_x86_64/ocl_ubuntu_20.mdx | 2 +- .../installing/linux_x86_64/ocl_ubuntu_22.mdx | 2 +- .../13/installing/linux_ppc64le/index.mdx | 2 +- .../installing/linux_ppc64le/odbc_rhel_8.mdx | 6 ++-- .../installing/linux_ppc64le/odbc_rhel_9.mdx | 6 ++-- .../installing/linux_ppc64le/odbc_sles_12.mdx | 6 ++-- .../installing/linux_ppc64le/odbc_sles_15.mdx | 6 ++-- .../13/installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_x86_64/odbc_centos_7.mdx | 4 +-- .../linux_x86_64/odbc_debian_10.mdx | 2 +- .../linux_x86_64/odbc_debian_11.mdx | 2 +- .../linux_x86_64/odbc_other_linux_8.mdx | 6 ++-- .../linux_x86_64/odbc_other_linux_9.mdx | 6 ++-- .../installing/linux_x86_64/odbc_rhel_7.mdx | 6 ++-- .../installing/linux_x86_64/odbc_rhel_8.mdx | 4 +-- .../installing/linux_x86_64/odbc_rhel_9.mdx | 4 +-- .../installing/linux_x86_64/odbc_sles_12.mdx | 6 ++-- .../installing/linux_x86_64/odbc_sles_15.mdx | 6 ++-- .../linux_x86_64/odbc_ubuntu_18.mdx | 2 +- .../linux_x86_64/odbc_ubuntu_20.mdx | 2 +- .../linux_x86_64/odbc_ubuntu_22.mdx | 2 +- .../pem/8/installing/linux_ppc64le/index.mdx | 2 +- .../8/installing/linux_ppc64le/pem_rhel_8.mdx | 2 +- .../8/installing/linux_ppc64le/pem_rhel_9.mdx | 2 +- .../installing/linux_ppc64le/pem_sles_12.mdx | 6 ++-- .../installing/linux_ppc64le/pem_sles_15.mdx | 6 ++-- .../pem/8/installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_x86_64/pem_centos_7.mdx | 2 +- .../installing/linux_x86_64/pem_debian_10.mdx | 2 +- .../installing/linux_x86_64/pem_debian_11.mdx | 2 +- .../linux_x86_64/pem_other_linux_8.mdx | 2 +- .../linux_x86_64/pem_other_linux_9.mdx | 2 +- .../8/installing/linux_x86_64/pem_rhel_7.mdx | 2 +- .../8/installing/linux_x86_64/pem_rhel_8.mdx | 2 +- .../8/installing/linux_x86_64/pem_rhel_9.mdx | 2 +- .../8/installing/linux_x86_64/pem_sles_12.mdx | 6 ++-- .../8/installing/linux_x86_64/pem_sles_15.mdx | 6 ++-- .../installing/linux_x86_64/pem_ubuntu_18.mdx | 2 +- .../installing/linux_x86_64/pem_ubuntu_20.mdx | 2 +- .../installing/linux_x86_64/pem_ubuntu_22.mdx | 2 +- .../linux_ppc64le/index.mdx | 2 +- .../linux_ppc64le/pem_agent_rhel_8.mdx | 2 +- .../linux_ppc64le/pem_agent_rhel_9.mdx | 2 +- .../linux_ppc64le/pem_agent_sles_12.mdx | 6 ++-- .../linux_ppc64le/pem_agent_sles_15.mdx | 6 ++-- .../linux_x86_64/index.mdx | 2 +- .../linux_x86_64/pem_agent_centos_7.mdx | 2 +- .../linux_x86_64/pem_agent_debian_10.mdx | 2 +- .../linux_x86_64/pem_agent_debian_11.mdx | 2 +- .../linux_x86_64/pem_agent_other_linux_8.mdx | 2 +- .../linux_x86_64/pem_agent_other_linux_9.mdx | 2 +- .../linux_x86_64/pem_agent_rhel_7.mdx | 2 +- .../linux_x86_64/pem_agent_rhel_8.mdx | 2 +- .../linux_x86_64/pem_agent_rhel_9.mdx | 2 +- .../linux_x86_64/pem_agent_sles_12.mdx | 6 ++-- .../linux_x86_64/pem_agent_sles_15.mdx | 6 ++-- .../linux_x86_64/pem_agent_ubuntu_18.mdx | 2 +- .../linux_x86_64/pem_agent_ubuntu_20.mdx | 2 +- .../linux_x86_64/pem_agent_ubuntu_22.mdx | 2 +- .../pem/9/installing/linux_ppc64le/index.mdx | 2 +- .../9/installing/linux_ppc64le/pem_rhel_8.mdx | 2 +- .../9/installing/linux_ppc64le/pem_rhel_9.mdx | 2 +- .../installing/linux_ppc64le/pem_sles_12.mdx | 6 ++-- .../installing/linux_ppc64le/pem_sles_15.mdx | 6 ++-- .../pem/9/installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_x86_64/pem_centos_7.mdx | 2 +- .../installing/linux_x86_64/pem_debian_10.mdx | 2 +- .../installing/linux_x86_64/pem_debian_11.mdx | 2 +- .../linux_x86_64/pem_other_linux_8.mdx | 2 +- .../linux_x86_64/pem_other_linux_9.mdx | 2 +- .../9/installing/linux_x86_64/pem_rhel_7.mdx | 2 +- .../9/installing/linux_x86_64/pem_rhel_8.mdx | 2 +- .../9/installing/linux_x86_64/pem_rhel_9.mdx | 2 +- .../9/installing/linux_x86_64/pem_sles_12.mdx | 6 ++-- .../9/installing/linux_x86_64/pem_sles_15.mdx | 6 ++-- .../installing/linux_x86_64/pem_ubuntu_18.mdx | 2 +- .../installing/linux_x86_64/pem_ubuntu_20.mdx | 2 +- .../installing/linux_x86_64/pem_ubuntu_22.mdx | 2 +- .../linux_ppc64le/index.mdx | 2 +- .../linux_ppc64le/pem_agent_rhel_8.mdx | 2 +- .../linux_ppc64le/pem_agent_rhel_9.mdx | 2 +- .../linux_ppc64le/pem_agent_sles_12.mdx | 6 ++-- .../linux_ppc64le/pem_agent_sles_15.mdx | 6 ++-- .../linux_x86_64/index.mdx | 2 +- .../linux_x86_64/pem_agent_centos_7.mdx | 2 +- .../linux_x86_64/pem_agent_debian_10.mdx | 2 +- .../linux_x86_64/pem_agent_debian_11.mdx | 2 +- .../linux_x86_64/pem_agent_other_linux_8.mdx | 2 +- .../linux_x86_64/pem_agent_other_linux_9.mdx | 2 +- .../linux_x86_64/pem_agent_rhel_7.mdx | 2 +- .../linux_x86_64/pem_agent_rhel_8.mdx | 2 +- .../linux_x86_64/pem_agent_rhel_9.mdx | 2 +- .../linux_x86_64/pem_agent_sles_12.mdx | 6 ++-- .../linux_x86_64/pem_agent_sles_15.mdx | 6 ++-- .../linux_x86_64/pem_agent_ubuntu_18.mdx | 2 +- .../linux_x86_64/pem_agent_ubuntu_20.mdx | 2 +- .../linux_x86_64/pem_agent_ubuntu_22.mdx | 2 +- .../1/installing/linux_ppc64le/index.mdx | 2 +- .../linux_ppc64le/pgbouncer_rhel_8.mdx | 6 ++-- .../linux_ppc64le/pgbouncer_rhel_9.mdx | 6 ++-- .../linux_ppc64le/pgbouncer_sles_12.mdx | 6 ++-- .../linux_ppc64le/pgbouncer_sles_15.mdx | 6 ++-- .../1/installing/linux_x86_64/index.mdx | 2 +- .../linux_x86_64/pgbouncer_centos_7.mdx | 4 +-- .../linux_x86_64/pgbouncer_debian_10.mdx | 2 +- .../linux_x86_64/pgbouncer_debian_11.mdx | 2 +- .../linux_x86_64/pgbouncer_other_linux_8.mdx | 6 ++-- .../linux_x86_64/pgbouncer_other_linux_9.mdx | 6 ++-- .../linux_x86_64/pgbouncer_rhel_7.mdx | 6 ++-- .../linux_x86_64/pgbouncer_rhel_8.mdx | 4 +-- .../linux_x86_64/pgbouncer_rhel_9.mdx | 4 +-- .../linux_x86_64/pgbouncer_sles_12.mdx | 6 ++-- .../linux_x86_64/pgbouncer_sles_15.mdx | 6 ++-- .../linux_x86_64/pgbouncer_ubuntu_18.mdx | 2 +- .../linux_x86_64/pgbouncer_ubuntu_20.mdx | 2 +- .../linux_x86_64/pgbouncer_ubuntu_22.mdx | 2 +- .../pge/15/installing/linux_x86_64/index.mdx | 2 +- .../installing/linux_x86_64/pge_centos_7.mdx | 4 +-- .../installing/linux_x86_64/pge_debian_10.mdx | 2 +- .../installing/linux_x86_64/pge_debian_11.mdx | 2 +- .../linux_x86_64/pge_other_linux_8.mdx | 6 ++-- .../linux_x86_64/pge_other_linux_9.mdx | 6 ++-- .../15/installing/linux_x86_64/pge_rhel_7.mdx | 6 ++-- .../15/installing/linux_x86_64/pge_rhel_8.mdx | 4 +-- .../15/installing/linux_x86_64/pge_rhel_9.mdx | 4 +-- .../installing/linux_x86_64/pge_ubuntu_18.mdx | 2 +- .../installing/linux_x86_64/pge_ubuntu_20.mdx | 2 +- .../installing/linux_x86_64/pge_ubuntu_22.mdx | 2 +- .../4/installing/linux_ppc64le/index.mdx | 2 +- .../linux_ppc64le/pgpool_rhel_8.mdx | 6 ++-- .../linux_ppc64le/pgpool_rhel_9.mdx | 6 ++-- .../linux_ppc64le/pgpool_sles_12.mdx | 6 ++-- .../linux_ppc64le/pgpool_sles_15.mdx | 6 ++-- .../4/installing/linux_x86_64/index.mdx | 2 +- .../linux_x86_64/pgpool_centos_7.mdx | 4 +-- .../linux_x86_64/pgpool_debian_10.mdx | 2 +- .../linux_x86_64/pgpool_debian_11.mdx | 2 +- .../linux_x86_64/pgpool_other_linux_8.mdx | 6 ++-- .../linux_x86_64/pgpool_other_linux_9.mdx | 6 ++-- .../installing/linux_x86_64/pgpool_rhel_7.mdx | 6 ++-- .../installing/linux_x86_64/pgpool_rhel_8.mdx | 4 +-- .../installing/linux_x86_64/pgpool_rhel_9.mdx | 4 +-- .../linux_x86_64/pgpool_sles_12.mdx | 6 ++-- .../linux_x86_64/pgpool_sles_15.mdx | 6 ++-- .../linux_x86_64/pgpool_ubuntu_18.mdx | 2 +- .../linux_x86_64/pgpool_ubuntu_20.mdx | 2 +- .../linux_x86_64/pgpool_ubuntu_22.mdx | 2 +- .../linux_ppc64le/index.mdx | 2 +- .../linux_ppc64le/pgpoolext_rhel_8.mdx | 6 ++-- .../linux_ppc64le/pgpoolext_rhel_9.mdx | 6 ++-- .../linux_ppc64le/pgpoolext_sles_12.mdx | 6 ++-- .../linux_ppc64le/pgpoolext_sles_15.mdx | 6 ++-- .../linux_x86_64/index.mdx | 2 +- .../linux_x86_64/pgpoolext_centos_7.mdx | 4 +-- .../linux_x86_64/pgpoolext_debian_10.mdx | 2 +- .../linux_x86_64/pgpoolext_debian_11.mdx | 2 +- .../linux_x86_64/pgpoolext_other_linux_8.mdx | 6 ++-- .../linux_x86_64/pgpoolext_other_linux_9.mdx | 6 ++-- .../linux_x86_64/pgpoolext_rhel_7.mdx | 6 ++-- .../linux_x86_64/pgpoolext_rhel_8.mdx | 4 +-- .../linux_x86_64/pgpoolext_rhel_9.mdx | 4 +-- .../linux_x86_64/pgpoolext_sles_12.mdx | 6 ++-- .../linux_x86_64/pgpoolext_sles_15.mdx | 6 ++-- .../linux_x86_64/pgpoolext_ubuntu_18.mdx | 2 +- .../linux_x86_64/pgpoolext_ubuntu_20.mdx | 2 +- .../linux_x86_64/pgpoolext_ubuntu_22.mdx | 2 +- .../3.2/installing/linux_ppc64le/index.mdx | 2 +- .../linux_ppc64le/postgis_rhel_8.mdx | 6 ++-- .../linux_ppc64le/postgis_rhel_9.mdx | 6 ++-- .../linux_ppc64le/postgis_sles_12.mdx | 6 ++-- .../linux_ppc64le/postgis_sles_15.mdx | 6 ++-- .../3.2/installing/linux_x86_64/index.mdx | 2 +- .../linux_x86_64/postgis_centos_7.mdx | 4 +-- .../linux_x86_64/postgis_debian_10.mdx | 2 +- .../linux_x86_64/postgis_debian_11.mdx | 2 +- .../linux_x86_64/postgis_other_linux_8.mdx | 6 ++-- .../linux_x86_64/postgis_other_linux_9.mdx | 6 ++-- .../linux_x86_64/postgis_rhel_7.mdx | 6 ++-- .../linux_x86_64/postgis_rhel_8.mdx | 4 +-- .../linux_x86_64/postgis_rhel_9.mdx | 4 +-- .../linux_x86_64/postgis_sles_12.mdx | 6 ++-- .../linux_x86_64/postgis_sles_15.mdx | 6 ++-- .../linux_x86_64/postgis_ubuntu_18.mdx | 2 +- .../linux_x86_64/postgis_ubuntu_20.mdx | 2 +- .../linux_x86_64/postgis_ubuntu_22.mdx | 2 +- 491 files changed, 1987 insertions(+), 1987 deletions(-) diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/index.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/index.mdx index 405a2b69ff5..a097b53ec1f 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/index.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/index.mdx @@ -10,7 +10,7 @@ navigation: - postgresql_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_8.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_8.mdx index fafea1fe49e..9b1cabf0563 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_8.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_8.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on RHEL 8 ppc64le Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). @@ -31,19 +31,19 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` -- Disable the built-in PostgreSQL module +- Disable the built-in PostgreSQL module: ```shell dnf -qy module disable postgresql ``` diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_9.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_9.mdx index 99b0f4470a5..57c6751499e 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_9.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_9.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on RHEL 9 ppc64le Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). @@ -31,19 +31,19 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` -- Disable the built-in PostgreSQL module +- Disable the built-in PostgreSQL module: ```shell dnf -qy module disable postgresql ``` diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_sles_12.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_sles_12.mdx index 7a5f9e698c4..cf44197df80 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_sles_12.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_sles_12.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on SLES 12 ppc64le Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). @@ -31,13 +31,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_sles_15.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_sles_15.mdx index f50f3ffb91b..c09677b6239 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_sles_15.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_sles_15.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on SLES 15 ppc64le Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). @@ -31,14 +31,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/index.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/index.mdx index b6b14fb3987..4e8227c12c2 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/index.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/index.mdx @@ -19,7 +19,7 @@ navigation: - postgresql_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_centos_7.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_centos_7.mdx index ca3f998f15a..1fb3e6d14ce 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_centos_7.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_centos_7.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on CentOS 7 x86_64 Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). @@ -31,7 +31,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_10.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_10.mdx index 2944bed8d26..e8024039709 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_10.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_10.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on Debian 10 x86_64 Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_11.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_11.mdx index c6259f15f71..62d817c16c8 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_11.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_11.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on Debian 11 x86_64 Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_8.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_8.mdx index 3453cf1818e..b43454a72e8 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_8.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_8.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on AlmaLinux 8 or Rocky Linux 8 x86_64 Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). @@ -31,23 +31,23 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell dnf config-manager --set-enabled powertools ``` -- Disable the built-in PostgreSQL module +- Disable the built-in PostgreSQL module: ```shell dnf -qy module disable postgresql ``` diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_9.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_9.mdx index c6990a216b4..9883b477c44 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_9.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_9.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on AlmaLinux 9 or Rocky Linux 9 x86_64 Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). @@ -31,23 +31,23 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell dnf config-manager --set-enabled powertools ``` -- Disable the built-in PostgreSQL module +- Disable the built-in PostgreSQL module: ```shell dnf -qy module disable postgresql ``` diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_7.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_7.mdx index 67b78e8dda2..82eab0899f2 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_7.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_7.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on RHEL 7 or OL 7 x86_64 Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). @@ -31,13 +31,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_8.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_8.mdx index 531c96d473d..f461b7dbf08 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_8.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_8.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on RHEL 8 or OL 8 x86_64 Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). @@ -31,17 +31,17 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` -- Disable the built-in PostgreSQL module +- Disable the built-in PostgreSQL module: ```shell dnf -qy module disable postgresql ``` diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_9.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_9.mdx index 7a9d41f6ab6..ea968986840 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_9.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_9.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on RHEL 9 or OL 9 x86_64 Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). @@ -31,17 +31,17 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" ``` -- Disable the built-in PostgreSQL module +- Disable the built-in PostgreSQL module: ```shell dnf -qy module disable postgresql ``` diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_sles_12.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_sles_12.mdx index cc7ee086ebe..496cd607ca6 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_sles_12.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_sles_12.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on SLES 12 x86_64 Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). @@ -31,13 +31,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_sles_15.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_sles_15.mdx index a0cc5180e16..3db686f432a 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_sles_15.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_sles_15.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on SLES 15 x86_64 Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). @@ -31,14 +31,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_18.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_18.mdx index d1f1a988bda..7c609647e78 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_18.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_18.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on Ubuntu 18.04 x86_64 Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_20.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_20.mdx index aed6d5a8439..52ca7708bd4 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_20.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_20.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on Ubuntu 20.04 x86_64 Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_22.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_22.mdx index 1474cc92dd7..46c51df78dd 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_22.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_22.mdx @@ -7,7 +7,7 @@ title: Installing PostgreSQL on Ubuntu 22.04 x86_64 Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. !!! Note Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). diff --git a/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_rhel_8.mdx b/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_rhel_8.mdx index 7e146ff360c..45bfac28119 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_rhel_8.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_rhel_8.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_rhel_9.mdx b/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_rhel_9.mdx index 6095701477c..4316f3e2a1a 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_rhel_9.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_rhel_9.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_sles_12.mdx b/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_sles_12.mdx index 741fc9afc3d..0bed756fad1 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_sles_12.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_sles_12.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,13 +33,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_sles_15.mdx b/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_sles_15.mdx index cd73e2b6bdc..a0a1f248390 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_sles_15.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_sles_15.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,14 +33,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/edb_plus/41/installing/linux_ppc64le/index.mdx b/product_docs/docs/edb_plus/41/installing/linux_ppc64le/index.mdx index b4915843470..ba38eb86c08 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_ppc64le/index.mdx @@ -16,7 +16,7 @@ navigation: - edbplus_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_centos_7.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_centos_7.mdx index 8470925b61c..2ba8f55332c 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_centos_7.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_centos_7.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,7 +33,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_debian_10.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_debian_10.mdx index 2c16d1133d7..2534a2aefb6 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_debian_10.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_debian_10.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_debian_11.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_debian_11.mdx index 95e488c9905..f1f782d7117 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_debian_11.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_debian_11.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_other_linux_8.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_other_linux_8.mdx index 87375b04a54..d5e6dabc419 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_other_linux_8.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_other_linux_8.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_other_linux_9.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_other_linux_9.mdx index a38a22a3ee9..4b82829f2fb 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_other_linux_9.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_other_linux_9.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_7.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_7.mdx index 19d9a0935ab..0a7af912aa4 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_7.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_7.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,13 +33,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_8.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_8.mdx index bc5bde9f2fb..7b9cac17632 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_8.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_8.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_9.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_9.mdx index f011a985423..da34085d24d 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_9.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_9.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_sles_12.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_sles_12.mdx index 9a960797269..2034fb44de5 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_sles_12.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_sles_12.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,13 +33,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_sles_15.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_sles_15.mdx index 372afcd2842..c05596e2c82 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_sles_15.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_sles_15.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,14 +33,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_ubuntu_18.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_ubuntu_18.mdx index 9127b34b748..2054d93401c 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_ubuntu_18.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_ubuntu_18.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_ubuntu_20.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_ubuntu_20.mdx index 08480372379..a0b0eee2b37 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_ubuntu_20.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_ubuntu_20.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_ubuntu_22.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_ubuntu_22.mdx index 1118e4c5ffc..bf7e7112e98 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_ubuntu_22.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_ubuntu_22.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/index.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/index.mdx index 6d16709d316..6fc857751b3 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/index.mdx @@ -25,7 +25,7 @@ navigation: - edbplus_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/efm/4/installing/linux_ppc64le/efm_rhel_8.mdx b/product_docs/docs/efm/4/installing/linux_ppc64le/efm_rhel_8.mdx index b2368b04fa5..cd5bb9276a5 100644 --- a/product_docs/docs/efm/4/installing/linux_ppc64le/efm_rhel_8.mdx +++ b/product_docs/docs/efm/4/installing/linux_ppc64le/efm_rhel_8.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/efm/4/installing/linux_ppc64le/efm_rhel_9.mdx b/product_docs/docs/efm/4/installing/linux_ppc64le/efm_rhel_9.mdx index 256ec94bf40..9f24c34c58d 100644 --- a/product_docs/docs/efm/4/installing/linux_ppc64le/efm_rhel_9.mdx +++ b/product_docs/docs/efm/4/installing/linux_ppc64le/efm_rhel_9.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/efm/4/installing/linux_ppc64le/efm_sles_12.mdx b/product_docs/docs/efm/4/installing/linux_ppc64le/efm_sles_12.mdx index e219ad2f1f7..a72db4dc70b 100644 --- a/product_docs/docs/efm/4/installing/linux_ppc64le/efm_sles_12.mdx +++ b/product_docs/docs/efm/4/installing/linux_ppc64le/efm_sles_12.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/efm/4/installing/linux_ppc64le/efm_sles_15.mdx b/product_docs/docs/efm/4/installing/linux_ppc64le/efm_sles_15.mdx index 621bb93c910..548ad0f3d5d 100644 --- a/product_docs/docs/efm/4/installing/linux_ppc64le/efm_sles_15.mdx +++ b/product_docs/docs/efm/4/installing/linux_ppc64le/efm_sles_15.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/efm/4/installing/linux_ppc64le/index.mdx b/product_docs/docs/efm/4/installing/linux_ppc64le/index.mdx index f556118eddd..1a3c7093259 100644 --- a/product_docs/docs/efm/4/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/efm/4/installing/linux_ppc64le/index.mdx @@ -17,7 +17,7 @@ navigation: - efm_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_centos_7.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_centos_7.mdx index 747939aea06..406f537e858 100644 --- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_centos_7.mdx +++ b/product_docs/docs/efm/4/installing/linux_x86_64/efm_centos_7.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_debian_10.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_debian_10.mdx index f669a42732f..b37428d5abb 100644 --- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_debian_10.mdx +++ b/product_docs/docs/efm/4/installing/linux_x86_64/efm_debian_10.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_debian_11.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_debian_11.mdx index 0fb96b53083..91945fd53a6 100644 --- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_debian_11.mdx +++ b/product_docs/docs/efm/4/installing/linux_x86_64/efm_debian_11.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_other_linux_8.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_other_linux_8.mdx index 48815da3ae6..a3aa26bd88c 100644 --- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_other_linux_8.mdx +++ b/product_docs/docs/efm/4/installing/linux_x86_64/efm_other_linux_8.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_other_linux_9.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_other_linux_9.mdx index 14a47807335..dc548b84296 100644 --- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_other_linux_9.mdx +++ b/product_docs/docs/efm/4/installing/linux_x86_64/efm_other_linux_9.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_7.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_7.mdx index 589f72e9270..f33e3ea5e8c 100644 --- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_7.mdx +++ b/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_7.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_8.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_8.mdx index ca424d4c98e..a4c7f824031 100644 --- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_8.mdx +++ b/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_8.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_9.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_9.mdx index c6cc53f6ca3..a4cca2907dc 100644 --- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_9.mdx +++ b/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_9.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_sles_12.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_sles_12.mdx index f19c8ca1dab..70d00690261 100644 --- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_sles_12.mdx +++ b/product_docs/docs/efm/4/installing/linux_x86_64/efm_sles_12.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_sles_15.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_sles_15.mdx index 9eb307813ac..c55f201fdd5 100644 --- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_sles_15.mdx +++ b/product_docs/docs/efm/4/installing/linux_x86_64/efm_sles_15.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_ubuntu_18.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_ubuntu_18.mdx index 15042c78f1a..d859af00fdb 100644 --- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_ubuntu_18.mdx +++ b/product_docs/docs/efm/4/installing/linux_x86_64/efm_ubuntu_18.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_ubuntu_20.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_ubuntu_20.mdx index c9fca0ef5cd..14f30ae98f1 100644 --- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_ubuntu_20.mdx +++ b/product_docs/docs/efm/4/installing/linux_x86_64/efm_ubuntu_20.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_ubuntu_22.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_ubuntu_22.mdx index af4849f945f..46b1218bbe3 100644 --- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_ubuntu_22.mdx +++ b/product_docs/docs/efm/4/installing/linux_x86_64/efm_ubuntu_22.mdx @@ -13,13 +13,13 @@ redirects: Before you begin the installation process: -- Install Postgres on the same host (not needed for witness nodes) +- Install Postgres on the same host (not needed for witness nodes). - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/index.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/index.mdx index d7320b0b34d..f6fd5164bbd 100644 --- a/product_docs/docs/efm/4/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/efm/4/installing/linux_x86_64/index.mdx @@ -26,7 +26,7 @@ navigation: - efm_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_7.mdx index 02e90eeb2f3..0f1650d3b84 100644 --- a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_7.mdx +++ b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,15 +34,15 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` @@ -53,7 +53,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as11`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as11`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb sudo systemctl start edb-as-11 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_8.mdx b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_8.mdx index ce830b92d04..d0c738954f8 100644 --- a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_8.mdx +++ b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,20 +34,20 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` -- If you are also installing PostGIS, enable additional repositories to resolve dependencies: +- If you're also installing PostGIS, enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` !!!note - If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-8-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + If you're using a public cloud RHEL image, `subscription manager` might not be enabled. Enabling it might incur unnecessary charges. Equivalent packages might be available under a different name, such as `codeready-builder-for-rhel-8-rhui-rpms`. To determine how to install `codeready-builder`, consult the documentation for the RHEL image you're using. ## Install the package @@ -55,7 +55,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`. To install an individual component: @@ -65,13 +65,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as11`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as11`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb @@ -79,7 +79,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb sudo systemctl start edb-as-11 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -89,7 +89,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -97,9 +97,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -108,7 +108,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -117,7 +117,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -127,7 +127,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -141,7 +141,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_9.mdx index 2738049f780..981eb3f1e3a 100644 --- a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,11 +34,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` @@ -55,7 +55,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`. To install an individual component: @@ -65,13 +65,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as11`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as11`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb @@ -79,7 +79,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb sudo systemctl start edb-as-11 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -89,7 +89,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -97,9 +97,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -108,7 +108,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -117,7 +117,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -127,7 +127,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -141,7 +141,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_12.mdx index d04c4966643..19f261fcbb0 100644 --- a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_12.mdx +++ b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_12.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -63,9 +63,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb @@ -73,7 +73,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb sudo systemctl start edb-as-11 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -83,7 +83,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -91,9 +91,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -102,7 +102,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -111,7 +111,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -121,7 +121,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -135,7 +135,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_15.mdx b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_15.mdx index adf3ceaf823..cb969d9023e 100644 --- a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_15.mdx +++ b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_15.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,14 +34,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -64,9 +64,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb @@ -74,7 +74,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb sudo systemctl start edb-as-11 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -84,7 +84,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -92,9 +92,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -103,7 +103,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -112,7 +112,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -122,7 +122,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -136,7 +136,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_ppc64le/index.mdx b/product_docs/docs/epas/11/installing/linux_ppc64le/index.mdx index 4057676a0b0..394693b4f37 100644 --- a/product_docs/docs/epas/11/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/epas/11/installing/linux_ppc64le/index.mdx @@ -18,7 +18,7 @@ navigation: - epas_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_centos_7.mdx index 07efd6cc517..6b24871c75d 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_centos_7.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_centos_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,7 +34,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` @@ -45,7 +45,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`. To install an individual component: @@ -55,13 +55,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as11`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as11`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb @@ -69,7 +69,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb sudo systemctl start edb-as-11 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -79,7 +79,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -87,9 +87,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -98,7 +98,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -107,7 +107,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -117,7 +117,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -131,7 +131,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_10.mdx index f5fcd29ceec..80d3286415c 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_10.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_10.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_11.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_11.mdx index 26452664caf..5397bd59bf2 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_11.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_11.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_8.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_8.mdx index 201df5f00f7..8c436b8a209 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_8.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as11`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as11`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb sudo systemctl start edb-as-11 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_9.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_9.mdx index 802704e904b..8c7ffe76417 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_9.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as11`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as11`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb sudo systemctl start edb-as-11 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_7.mdx index 7e4cc198fd5..6c8e4fe7880 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_7.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as11`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as11`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb sudo systemctl start edb-as-11 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_8.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_8.mdx index 2cdb5d3aec0..a6cc561cee4 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_8.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,18 +34,18 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- If you are also installing PostGIS, enable additional repositories to resolve dependencies: +- If you're also installing PostGIS, enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` !!!note - If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-8-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + If you're using a public cloud RHEL image, `subscription manager` might not be enabled. Enabling it might incur unnecessary charges. Equivalent packages might be available under a different name, such as `codeready-builder-for-rhel-8-rhui-rpms`. To determine how to install `codeready-builder`, consult the documentation for the RHEL image you're using. ## Install the package @@ -53,7 +53,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as11`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as11`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb sudo systemctl start edb-as-11 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_9.mdx index 38e806c5999..2495e08caaa 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,7 +34,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm @@ -53,7 +53,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as11`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as11`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb sudo systemctl start edb-as-11 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_12.mdx index 8539bc38ae2..3772f7bef44 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_12.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_12.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -63,9 +63,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb @@ -73,7 +73,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb sudo systemctl start edb-as-11 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -83,7 +83,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -91,9 +91,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -102,7 +102,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -111,7 +111,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -121,7 +121,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -135,7 +135,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_15.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_15.mdx index e2cac95fc36..a9415b05bfe 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_15.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_15.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,14 +34,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -64,9 +64,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb @@ -74,7 +74,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb sudo systemctl start edb-as-11 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -84,7 +84,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -92,9 +92,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -103,7 +103,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -112,7 +112,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -122,7 +122,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -136,7 +136,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_18.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_18.mdx index 0dc20b58447..b7c487927f9 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_18.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_18.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_20.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_20.mdx index f5bfff329c7..28c6b56ac1c 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_20.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_20.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_22.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_22.mdx index 41393f7f67b..5b44b3d75e4 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_22.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_22.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/index.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/index.mdx index 21aea65e285..e8137f1c3df 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/index.mdx @@ -27,7 +27,7 @@ navigation: - epas_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_7.mdx index b27e69cc1a2..e03579fe03d 100644 --- a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_7.mdx +++ b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,15 +34,15 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` @@ -53,7 +53,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as12`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as12`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb sudo systemctl start edb-as-12 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_8.mdx b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_8.mdx index 46de00c6177..3b8cac0238a 100644 --- a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_8.mdx +++ b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,20 +34,20 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` -- If you are also installing PostGIS, enable additional repositories to resolve dependencies: +- If you're also installing PostGIS, enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` !!!note - If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-8-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + If you're using a public cloud RHEL image, `subscription manager` might not be enabled. Enabling it might incur unnecessary charges. Equivalent packages might be available under a different name, such as `codeready-builder-for-rhel-8-rhui-rpms`. To determine how to install `codeready-builder`, consult the documentation for the RHEL image you're using. ## Install the package @@ -55,7 +55,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`. To install an individual component: @@ -65,13 +65,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as12`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as12`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb @@ -79,7 +79,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb sudo systemctl start edb-as-12 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -89,7 +89,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -97,9 +97,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -108,7 +108,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -117,7 +117,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -127,7 +127,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -141,7 +141,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_9.mdx index a49e7e5a27b..3e444c6600e 100644 --- a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,11 +34,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` @@ -55,7 +55,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`. To install an individual component: @@ -65,13 +65,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as12`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as12`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb @@ -79,7 +79,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb sudo systemctl start edb-as-12 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -89,7 +89,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -97,9 +97,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -108,7 +108,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -117,7 +117,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -127,7 +127,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -141,7 +141,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_12.mdx index 4b9152dd2dc..49bb168a9a7 100644 --- a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_12.mdx +++ b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_12.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -63,9 +63,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb @@ -73,7 +73,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb sudo systemctl start edb-as-12 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -83,7 +83,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -91,9 +91,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -102,7 +102,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -111,7 +111,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -121,7 +121,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -135,7 +135,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_15.mdx b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_15.mdx index e29010c529a..eed6caab5e2 100644 --- a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_15.mdx +++ b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_15.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,14 +34,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -64,9 +64,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb @@ -74,7 +74,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb sudo systemctl start edb-as-12 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -84,7 +84,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -92,9 +92,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -103,7 +103,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -112,7 +112,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -122,7 +122,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -136,7 +136,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_ppc64le/index.mdx b/product_docs/docs/epas/12/installing/linux_ppc64le/index.mdx index 653ec118812..cbd6f39813d 100644 --- a/product_docs/docs/epas/12/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/epas/12/installing/linux_ppc64le/index.mdx @@ -18,7 +18,7 @@ navigation: - epas_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_centos_7.mdx index c20d4cda14b..f966a66e147 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_centos_7.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_centos_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,7 +34,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` @@ -45,7 +45,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`. To install an individual component: @@ -55,13 +55,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as12`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as12`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb @@ -69,7 +69,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb sudo systemctl start edb-as-12 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -79,7 +79,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -87,9 +87,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -98,7 +98,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -107,7 +107,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -117,7 +117,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -131,7 +131,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_10.mdx index da8001119b4..1f3aa2525f7 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_10.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_10.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_11.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_11.mdx index f6fb10af3d3..c5d7441e94a 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_11.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_11.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_8.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_8.mdx index c4876480497..1ff3a9b112d 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_8.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as12`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as12`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb sudo systemctl start edb-as-12 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_9.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_9.mdx index fcc1e9a8947..96d22b8a253 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_9.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as12`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as12`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb sudo systemctl start edb-as-12 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_7.mdx index e4b9bc19843..e25bb6a8524 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_7.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as12`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as12`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb sudo systemctl start edb-as-12 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_8.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_8.mdx index ad0e6dc17a5..ba33cd2c9ff 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_8.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,18 +34,18 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- If you are also installing PostGIS, enable additional repositories to resolve dependencies: +- If you're also installing PostGIS, enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` !!!note - If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-8-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + If you're using a public cloud RHEL image, `subscription manager` might not be enabled. Enabling it might incur unnecessary charges. Equivalent packages might be available under a different name, such as `codeready-builder-for-rhel-8-rhui-rpms`. To determine how to install `codeready-builder`, consult the documentation for the RHEL image you're using. ## Install the package @@ -53,7 +53,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as12`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as12`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb sudo systemctl start edb-as-12 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_9.mdx index f81e07fa64b..aef7056768e 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,7 +34,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm @@ -53,7 +53,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as12`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as12`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb sudo systemctl start edb-as-12 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_12.mdx index f2e75d4d32f..077cb05acac 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_12.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_12.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -63,9 +63,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb @@ -73,7 +73,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb sudo systemctl start edb-as-12 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -83,7 +83,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -91,9 +91,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -102,7 +102,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -111,7 +111,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -121,7 +121,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -135,7 +135,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_15.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_15.mdx index 64b9bcbc9a5..280a85650f7 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_15.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_15.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,14 +34,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -64,9 +64,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb @@ -74,7 +74,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb sudo systemctl start edb-as-12 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -84,7 +84,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -92,9 +92,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -103,7 +103,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -112,7 +112,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -122,7 +122,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -136,7 +136,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_18.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_18.mdx index 222a2ae71a9..77881730bbc 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_18.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_18.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_20.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_20.mdx index fa3907f4b9a..0b27809f1fb 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_20.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_20.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_22.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_22.mdx index d94bf09b3d3..36d1122c85a 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_22.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_22.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/index.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/index.mdx index 99dd429a918..50c6f13a08a 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/index.mdx @@ -27,7 +27,7 @@ navigation: - epas_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_7.mdx index 236d086ecdb..64bdd9b77c1 100644 --- a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_7.mdx +++ b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,15 +34,15 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` @@ -53,7 +53,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as13`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as13`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb sudo systemctl start edb-as-13 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_8.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_8.mdx index 29cfffbda46..f25af0f0846 100644 --- a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_8.mdx +++ b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,20 +34,20 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` -- If you are also installing PostGIS, enable additional repositories to resolve dependencies: +- If you're also installing PostGIS, enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` !!!note - If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-8-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + If you're using a public cloud RHEL image, `subscription manager` might not be enabled. Enabling it might incur unnecessary charges. Equivalent packages might be available under a different name, such as `codeready-builder-for-rhel-8-rhui-rpms`. To determine how to install `codeready-builder`, consult the documentation for the RHEL image you're using. ## Install the package @@ -55,7 +55,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. To install an individual component: @@ -65,13 +65,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as13`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as13`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb @@ -79,7 +79,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb sudo systemctl start edb-as-13 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -89,7 +89,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -97,9 +97,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -108,7 +108,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -117,7 +117,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -127,7 +127,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -141,7 +141,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_9.mdx index e09657006f6..119b3d88ef0 100644 --- a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,11 +34,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` @@ -55,7 +55,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. To install an individual component: @@ -65,13 +65,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as13`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as13`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb @@ -79,7 +79,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb sudo systemctl start edb-as-13 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -89,7 +89,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -97,9 +97,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -108,7 +108,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -117,7 +117,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -127,7 +127,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -141,7 +141,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_12.mdx index 744d2f8d194..96ca0c457d7 100644 --- a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_12.mdx +++ b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_12.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -63,9 +63,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb @@ -73,7 +73,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb sudo systemctl start edb-as-13 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -83,7 +83,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -91,9 +91,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -102,7 +102,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -111,7 +111,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -121,7 +121,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -135,7 +135,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_15.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_15.mdx index 6762f3fcf11..e7acb2a4258 100644 --- a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_15.mdx +++ b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_15.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,14 +34,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -64,9 +64,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb @@ -74,7 +74,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb sudo systemctl start edb-as-13 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -84,7 +84,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -92,9 +92,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -103,7 +103,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -112,7 +112,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -122,7 +122,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -136,7 +136,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/index.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/index.mdx index a9917c63a79..ceba742881e 100644 --- a/product_docs/docs/epas/13/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/epas/13/installing/linux_ppc64le/index.mdx @@ -18,7 +18,7 @@ navigation: - epas_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_centos_7.mdx index db6d4eac24f..db6d66a71e5 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_centos_7.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_centos_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,7 +34,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` @@ -45,7 +45,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. To install an individual component: @@ -55,13 +55,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as13`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as13`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb @@ -69,7 +69,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb sudo systemctl start edb-as-13 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -79,7 +79,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -87,9 +87,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -98,7 +98,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -107,7 +107,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -117,7 +117,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -131,7 +131,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_10.mdx index 9f712b5e1c8..fa47bb6ff8f 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_10.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_10.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_11.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_11.mdx index 5a86a7ff287..e415c5f52b6 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_11.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_11.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_8.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_8.mdx index 6e15bcab71d..02794a41518 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_8.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as13`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as13`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb sudo systemctl start edb-as-13 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_9.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_9.mdx index e14dfcfc691..7108a5586f4 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_9.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as13`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as13`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb sudo systemctl start edb-as-13 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_7.mdx index 89761d28f3a..4ab029088f3 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_7.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as13`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as13`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb sudo systemctl start edb-as-13 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_8.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_8.mdx index d67963990d0..0189a243189 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_8.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,18 +34,18 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- If you are also installing PostGIS, enable additional repositories to resolve dependencies: +- If you're also installing PostGIS, enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` !!!note - If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-8-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + If you're using a public cloud RHEL image, `subscription manager` might not be enabled. Enabling it might incur unnecessary charges. Equivalent packages might be available under a different name, such as `codeready-builder-for-rhel-8-rhui-rpms`. To determine how to install `codeready-builder`, consult the documentation for the RHEL image you're using. ## Install the package @@ -53,7 +53,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as13`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as13`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb sudo systemctl start edb-as-13 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_9.mdx index e1689a0b1e3..59b97ab087b 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,7 +34,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm @@ -53,7 +53,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as13`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as13`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb sudo systemctl start edb-as-13 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_12.mdx index 62b905d73f0..74fcad35575 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_12.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_12.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -63,9 +63,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb @@ -73,7 +73,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb sudo systemctl start edb-as-13 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -83,7 +83,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -91,9 +91,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -102,7 +102,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -111,7 +111,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -121,7 +121,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -135,7 +135,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_15.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_15.mdx index 9936bfdebc2..a29eee83c7e 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_15.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_15.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,14 +34,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -64,9 +64,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb @@ -74,7 +74,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb sudo systemctl start edb-as-13 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -84,7 +84,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -92,9 +92,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -103,7 +103,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -112,7 +112,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -122,7 +122,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -136,7 +136,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_18.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_18.mdx index c134e425f05..6f9e612e9e6 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_18.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_18.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_20.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_20.mdx index 1b9652a775b..b0f4bfca8cb 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_20.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_20.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_22.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_22.mdx index 206e4e60a5f..968895d87ce 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_22.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_22.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/index.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/index.mdx index bc42b9b5bc1..81c31417e1a 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/index.mdx @@ -27,7 +27,7 @@ navigation: - epas_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_7.mdx index dc4f4593e8d..13d4ef480e4 100644 --- a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_7.mdx +++ b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,15 +34,15 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` @@ -53,7 +53,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as14`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as14`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb sudo systemctl start edb-as-14 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_8.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_8.mdx index e4d6a43bcfd..d025a5dab43 100644 --- a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_8.mdx +++ b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,20 +34,20 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` -- If you are also installing PostGIS, enable additional repositories to resolve dependencies: +- If you're also installing PostGIS, enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` !!!note - If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-8-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + If you're using a public cloud RHEL image, `subscription manager` might not be enabled. Enabling it might incur unnecessary charges. Equivalent packages might be available under a different name, such as `codeready-builder-for-rhel-8-rhui-rpms`. To determine how to install `codeready-builder`, consult the documentation for the RHEL image you're using. ## Install the package @@ -55,7 +55,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. To install an individual component: @@ -65,13 +65,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as14`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as14`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb @@ -79,7 +79,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb sudo systemctl start edb-as-14 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -89,7 +89,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -97,9 +97,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -108,7 +108,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -117,7 +117,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -127,7 +127,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -141,7 +141,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_9.mdx index 4bbe1293368..781bb2e4ae4 100644 --- a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,11 +34,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` @@ -55,7 +55,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. To install an individual component: @@ -65,13 +65,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as14`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as14`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb @@ -79,7 +79,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb sudo systemctl start edb-as-14 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -89,7 +89,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -97,9 +97,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -108,7 +108,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -117,7 +117,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -127,7 +127,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -141,7 +141,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_12.mdx index 196b81ef1b9..8daed5b3501 100644 --- a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_12.mdx +++ b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_12.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -63,9 +63,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb @@ -73,7 +73,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb sudo systemctl start edb-as-14 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -83,7 +83,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -91,9 +91,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -102,7 +102,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -111,7 +111,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -121,7 +121,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -135,7 +135,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_15.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_15.mdx index fd0d365694b..cd288bd90d6 100644 --- a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_15.mdx +++ b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_15.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,14 +34,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -64,9 +64,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb @@ -74,7 +74,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb sudo systemctl start edb-as-14 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -84,7 +84,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -92,9 +92,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -103,7 +103,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -112,7 +112,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -122,7 +122,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -136,7 +136,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/index.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/index.mdx index 5d63853dafd..f60a1c84f29 100644 --- a/product_docs/docs/epas/14/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/epas/14/installing/linux_ppc64le/index.mdx @@ -18,7 +18,7 @@ navigation: - epas_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_centos_7.mdx index 313ea779958..f33bb5f6b65 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_centos_7.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_centos_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,7 +34,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` @@ -45,7 +45,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. To install an individual component: @@ -55,13 +55,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as14`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as14`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb @@ -69,7 +69,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb sudo systemctl start edb-as-14 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -79,7 +79,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -87,9 +87,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -98,7 +98,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -107,7 +107,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -117,7 +117,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -131,7 +131,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_10.mdx index f22d6dae181..45b9850f7e9 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_10.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_10.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_11.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_11.mdx index 847dac6302e..eedcb491035 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_11.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_11.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_8.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_8.mdx index 2d22b064e7b..1f54101862b 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_8.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as14`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as14`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb sudo systemctl start edb-as-14 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_9.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_9.mdx index ce4aa5b5a4d..a3d044fc3f9 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_9.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as14`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as14`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb sudo systemctl start edb-as-14 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_7.mdx index 52b2170c865..2fce9ff259c 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_7.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as14`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as14`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb sudo systemctl start edb-as-14 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_8.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_8.mdx index 6c575e0c34c..34bcbbcd079 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_8.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,18 +34,18 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- If you are also installing PostGIS, enable additional repositories to resolve dependencies: +- If you're also installing PostGIS, enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` !!!note - If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-8-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + If you're using a public cloud RHEL image, `subscription manager` might not be enabled. Enabling it might incur unnecessary charges. Equivalent packages might be available under a different name, such as `codeready-builder-for-rhel-8-rhui-rpms`. To determine how to install `codeready-builder`, consult the documentation for the RHEL image you're using. ## Install the package @@ -53,7 +53,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as14`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as14`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb sudo systemctl start edb-as-14 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_9.mdx index 08ad2229787..7d649c63989 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,7 +34,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm @@ -53,7 +53,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as14`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as14`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb sudo systemctl start edb-as-14 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_12.mdx index ab3f8fca820..c26981bc742 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_12.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_12.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -63,9 +63,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb @@ -73,7 +73,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb sudo systemctl start edb-as-14 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -83,7 +83,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -91,9 +91,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -102,7 +102,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -111,7 +111,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -121,7 +121,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -135,7 +135,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_15.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_15.mdx index 650ca0d62db..fa8dcd09882 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_15.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_15.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,14 +34,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -64,9 +64,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb @@ -74,7 +74,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb sudo systemctl start edb-as-14 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -84,7 +84,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -92,9 +92,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -103,7 +103,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -112,7 +112,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -122,7 +122,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -136,7 +136,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_18.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_18.mdx index 5bebc2fced0..8cb23e779b5 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_18.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_18.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_20.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_20.mdx index 739a6101b79..c3b5610a881 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_20.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_20.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_22.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_22.mdx index e7adde7c80e..fc8a080eb83 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_22.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_22.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/index.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/index.mdx index c5bd2116dab..ecd62ff0040 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/index.mdx @@ -27,7 +27,7 @@ navigation: - epas_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx index fadb9f01f04..19194f58557 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,15 +34,15 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` @@ -53,7 +53,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as15`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as15`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb sudo systemctl start edb-as-15 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_8.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_8.mdx index b9d8718e83a..7f0cc553b0c 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_8.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,20 +34,20 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` -- If you are also installing PostGIS, enable additional repositories to resolve dependencies: +- If you're also installing PostGIS, enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` !!!note - If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-8-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + If you're using a public cloud RHEL image, `subscription manager` might not be enabled. Enabling it might incur unnecessary charges. Equivalent packages might be available under a different name, such as `codeready-builder-for-rhel-8-rhui-rpms`. To determine how to install `codeready-builder`, consult the documentation for the RHEL image you're using. ## Install the package @@ -55,7 +55,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. To install an individual component: @@ -65,13 +65,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as15`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as15`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb @@ -79,7 +79,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb sudo systemctl start edb-as-15 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -89,7 +89,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -97,9 +97,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -108,7 +108,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -117,7 +117,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -127,7 +127,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -141,7 +141,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx index 0be46476011..91ac028db29 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,11 +34,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` @@ -55,7 +55,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. To install an individual component: @@ -65,13 +65,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as15`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as15`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb @@ -79,7 +79,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb sudo systemctl start edb-as-15 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -89,7 +89,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -97,9 +97,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -108,7 +108,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -117,7 +117,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -127,7 +127,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -141,7 +141,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx index f497ac63eb0..570eb32a30d 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -63,9 +63,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb @@ -73,7 +73,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb sudo systemctl start edb-as-15 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -83,7 +83,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -91,9 +91,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -102,7 +102,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -111,7 +111,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -121,7 +121,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -135,7 +135,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_15.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_15.mdx index 9205ac4472c..6a3607220ea 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_15.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_15.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,14 +34,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -64,9 +64,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb @@ -74,7 +74,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb sudo systemctl start edb-as-15 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -84,7 +84,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -92,9 +92,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -103,7 +103,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -112,7 +112,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -122,7 +122,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -136,7 +136,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/index.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/index.mdx index df67059f9f4..78f4ddbe958 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/index.mdx @@ -18,7 +18,7 @@ navigation: - epas_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx index ab0da72c2da..210a69b0e92 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,7 +34,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` @@ -45,7 +45,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. To install an individual component: @@ -55,13 +55,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as15`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as15`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb @@ -69,7 +69,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb sudo systemctl start edb-as-15 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -79,7 +79,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -87,9 +87,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -98,7 +98,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -107,7 +107,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -117,7 +117,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -131,7 +131,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_10.mdx index bf11f953fe5..ee48367ff64 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_10.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_10.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_11.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_11.mdx index 430b8d0a97e..ccdf025428c 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_11.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_11.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_8.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_8.mdx index 9ffbe1028fd..40ec76dc564 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_8.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as15`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as15`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb sudo systemctl start edb-as-15 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_9.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_9.mdx index f8acd3ad53f..69d9c1914e0 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_9.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as15`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as15`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb sudo systemctl start edb-as-15 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx index b6effda2dcc..c50447914cb 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` @@ -51,7 +51,7 @@ Before you begin the installation process: sudo yum -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. To install an individual component: @@ -61,13 +61,13 @@ sudo yum -y install Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as15`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as15`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb @@ -75,7 +75,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb sudo systemctl start edb-as-15 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -85,7 +85,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -93,9 +93,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -104,7 +104,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -113,7 +113,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -123,7 +123,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -137,7 +137,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_8.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_8.mdx index 41177790cb4..333b703978b 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_8.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,18 +34,18 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- If you are also installing PostGIS, enable additional repositories to resolve dependencies: +- If you're also installing PostGIS, enable additional repositories to resolve dependencies: ```shell ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` !!!note - If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-8-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + If you're using a public cloud RHEL image, `subscription manager` might not be enabled. Enabling it might incur unnecessary charges. Equivalent packages might be available under a different name, such as `codeready-builder-for-rhel-8-rhui-rpms`. To determine how to install `codeready-builder`, consult the documentation for the RHEL image you're using. ## Install the package @@ -53,7 +53,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as15`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as15`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb sudo systemctl start edb-as-15 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx index 39e9d81371e..362a2a2e802 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,7 +34,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm @@ -53,7 +53,7 @@ Before you begin the installation process: sudo dnf -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. To install an individual component: @@ -63,13 +63,13 @@ sudo dnf -y install Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/). -Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as15`. +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as15`. ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb @@ -77,7 +77,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb sudo systemctl start edb-as-15 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -87,7 +87,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -95,9 +95,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -106,7 +106,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -115,7 +115,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -125,7 +125,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -139,7 +139,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx index e9b510cb09a..a39e1f8adbc 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,13 +34,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -63,9 +63,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb @@ -73,7 +73,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb sudo systemctl start edb-as-15 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -83,7 +83,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -91,9 +91,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -102,7 +102,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -111,7 +111,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -121,7 +121,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -135,7 +135,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_15.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_15.mdx index 6946d889b00..968fb55cc51 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_15.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_15.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -34,14 +34,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` @@ -64,9 +64,9 @@ Where `package_name` can be any of the available packages from the [available pa ## Initial configuration -This section steps you through getting started with your cluster including logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). +First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). ```shell sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb @@ -74,7 +74,7 @@ sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb sudo systemctl start edb-as-15 ``` -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -84,7 +84,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -92,9 +92,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -103,7 +103,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -112,7 +112,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -122,7 +122,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -136,7 +136,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_18.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_18.mdx index 15f815af87e..f5b90bb7a53 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_18.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_18.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_20.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_20.mdx index 29fd8ab36a4..aa941c6da61 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_20.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_20.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_22.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_22.mdx index c53c6a48134..fcb4ee9e023 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_22.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_22.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -40,7 +40,7 @@ Before you begin the installation process: sudo apt-get -y install edb-as-server ``` -Where `` is the version of the EDB Postgres Advanced Server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`. +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. To install an individual component: @@ -54,7 +54,7 @@ Where `package_name` can be any of the available packages from the [available pa This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -To work in your cluster, login as the enterprisedb user. Connect to the database server using the psql command line client (although you can use a client of your choice with the appropriate connection string). +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. ```shell sudo su - enterprisedb @@ -64,7 +64,7 @@ psql edb The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). ```sql ALTER ROLE enterprisedb IDENTIFIED BY password; @@ -72,9 +72,9 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; ## Experiment -Now you are ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First let's create a database to hold human resource information named `hr` using psql. +First, use psql create a database named `hr` to hold human resource information. ```sql # running in psql @@ -83,7 +83,7 @@ __OUTPUT__ CREATE DATABASE ``` -Connect to the `hr` database inside psql. +Connect to the `hr` database inside psql: ``` \c hr @@ -92,7 +92,7 @@ psql (15.2.0, server 15.2.0) You are now connected to database "hr" as user "enterprisedb". ``` -Create columns to hold department numbers, unique department names, and locations. +Create columns to hold department numbers, unique department names, and locations: ``` CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk @@ -102,7 +102,7 @@ __OUTPUT__ CREATE TABLE ``` -Insert values into the `dept` table. +Insert values into the `dept` table: ``` INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); @@ -116,7 +116,7 @@ __OUTPUT__ INSERT 0 1 ``` -View what is in the table by selecting the values from the table. +View the table data by selecting the values from the table: ``` SELECT * FROM dept; diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/index.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/index.mdx index 75acc83d834..e2ad57b7171 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/index.mdx @@ -27,7 +27,7 @@ navigation: - epas_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_rhel_8.mdx b/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_rhel_8.mdx index bd936ab5045..f5fd1a5859e 100644 --- a/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_rhel_8.mdx +++ b/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_rhel_8.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_rhel_9.mdx b/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_rhel_9.mdx index 5585c74cf39..963b708a11a 100644 --- a/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_rhel_9.mdx +++ b/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_rhel_9.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_sles_12.mdx b/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_sles_12.mdx index 9d28248d2c3..dfb892e452b 100644 --- a/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_sles_12.mdx +++ b/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_sles_12.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,13 +33,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_sles_15.mdx b/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_sles_15.mdx index 0ad85705dfc..25490b08645 100644 --- a/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_sles_15.mdx +++ b/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_sles_15.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,14 +33,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/eprs/7/installing/linux_ppc64le/index.mdx b/product_docs/docs/eprs/7/installing/linux_ppc64le/index.mdx index 5bac6af969a..db9f2bed46f 100644 --- a/product_docs/docs/eprs/7/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/eprs/7/installing/linux_ppc64le/index.mdx @@ -17,7 +17,7 @@ navigation: - eprs_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_centos_7.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_centos_7.mdx index ca35dda19d5..ce4b0248d9f 100644 --- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_centos_7.mdx +++ b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_centos_7.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,7 +33,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_debian_10.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_debian_10.mdx index 5226dca37f0..b7739f25dc3 100644 --- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_debian_10.mdx +++ b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_debian_10.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_debian_11.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_debian_11.mdx index 3f2d6e6b695..5adfb4bdc68 100644 --- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_debian_11.mdx +++ b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_debian_11.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_other_linux_8.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_other_linux_8.mdx index 9c48e6dedfc..16918c9009b 100644 --- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_other_linux_8.mdx +++ b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_other_linux_8.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_other_linux_9.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_other_linux_9.mdx index 5aca86f303e..6568172ede3 100644 --- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_other_linux_9.mdx +++ b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_other_linux_9.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_7.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_7.mdx index 9560ef3f5f7..f143be1bf6e 100644 --- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_7.mdx +++ b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_7.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,13 +33,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_8.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_8.mdx index cf81d5cae3b..cdd662adc83 100644 --- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_8.mdx +++ b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_8.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_9.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_9.mdx index 971baaf81e8..13a712afa08 100644 --- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_9.mdx +++ b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_9.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_sles_12.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_sles_12.mdx index 828e3219c83..4d21e1bfe78 100644 --- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_sles_12.mdx +++ b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_sles_12.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,13 +33,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_sles_15.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_sles_15.mdx index d24e7ad64f0..315715b914c 100644 --- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_sles_15.mdx +++ b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_sles_15.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,14 +33,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_ubuntu_18.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_ubuntu_18.mdx index eabb18276a2..cd0b7bd1d3a 100644 --- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_ubuntu_18.mdx +++ b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_ubuntu_18.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_ubuntu_20.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_ubuntu_20.mdx index 7c6fa36bac4..47d57c72828 100644 --- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_ubuntu_20.mdx +++ b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_ubuntu_20.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_ubuntu_22.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_ubuntu_22.mdx index fa37e6681d4..646efb170f6 100644 --- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_ubuntu_22.mdx +++ b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_ubuntu_22.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/index.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/index.mdx index 28a3f20ea38..1cca5b841ae 100644 --- a/product_docs/docs/eprs/7/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/eprs/7/installing/linux_x86_64/index.mdx @@ -26,7 +26,7 @@ navigation: - eprs_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_rhel_8.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_rhel_8.mdx index 5f7d5efe5bb..11754320209 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_rhel_8.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_rhel_9.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_rhel_9.mdx index c01cb61b075..c32383cee69 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_rhel_9.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_sles_12.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_sles_12.mdx index 19bfebd0272..9d52a6bf688 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_sles_12.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_sles_15.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_sles_15.mdx index ef9202c2f9a..8fc856b143a 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_sles_15.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/index.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/index.mdx index 8c0f1c10e53..7bd79cfb573 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/index.mdx @@ -16,7 +16,7 @@ navigation: - hadoop_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_centos_7.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_centos_7.mdx index e490aa62e15..ef0b35df80b 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_centos_7.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_centos_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_debian_10.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_debian_10.mdx index 0e2fb6831f4..e9996e094fe 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_debian_10.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_debian_10.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_debian_11.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_debian_11.mdx index ec8e1a25b19..ee33b813c44 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_debian_11.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_debian_11.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_other_linux_8.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_other_linux_8.mdx index e23cc785a2f..9b275453be5 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_other_linux_8.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_other_linux_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_other_linux_9.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_other_linux_9.mdx index 4fe7f994a67..6b86c88b7c9 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_other_linux_9.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_other_linux_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_7.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_7.mdx index c051f1de46f..1716fa23f44 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_7.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_8.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_8.mdx index dae941bd758..a5d17d908e4 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_8.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_9.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_9.mdx index d3c1c6d1902..473ed4a376c 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_9.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_sles_12.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_sles_12.mdx index cc76b1fd566..a35e11345b7 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_sles_12.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_sles_15.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_sles_15.mdx index 9da54741f71..e089e9a479e 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_sles_15.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_ubuntu_18.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_ubuntu_18.mdx index f7c5a03b40d..2a9be4081a2 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_ubuntu_18.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_ubuntu_18.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_ubuntu_20.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_ubuntu_20.mdx index 8ff21616e32..2ab9913348e 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_ubuntu_20.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_ubuntu_20.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_ubuntu_22.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_ubuntu_22.mdx index 6908ec8c453..3d23902b546 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_ubuntu_22.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_ubuntu_22.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/index.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/index.mdx index d6e166b5621..e2ff0edadd5 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/index.mdx @@ -25,7 +25,7 @@ navigation: - hadoop_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/index.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/index.mdx index 42d6fcf0a5b..f8f88dac9fe 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/index.mdx @@ -16,7 +16,7 @@ navigation: - jdbc_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_rhel_8.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_rhel_8.mdx index 0eea4619b6f..fee601d3ea0 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_rhel_8.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_rhel_8.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -43,11 +43,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_rhel_9.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_rhel_9.mdx index 715f6816201..dd72026bfbc 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_rhel_9.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_rhel_9.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -43,11 +43,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_sles_12.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_sles_12.mdx index be99c7e5151..2f7493eaa0c 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_sles_12.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_sles_12.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -43,13 +43,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_sles_15.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_sles_15.mdx index 90f37152251..2f2ca4284b4 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_sles_15.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_ppc64le/jdbc_sles_15.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -43,14 +43,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/index.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/index.mdx index ec33e1e7afd..e0f25e4c80a 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/index.mdx @@ -25,7 +25,7 @@ navigation: - jdbc_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_centos_7.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_centos_7.mdx index 5157f75a445..4e277aebb52 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_centos_7.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_centos_7.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -43,7 +43,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_debian_10.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_debian_10.mdx index 5bb279f4933..1f06aa38900 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_debian_10.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_debian_10.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_debian_11.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_debian_11.mdx index e6bc5787380..b9a269d9e58 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_debian_11.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_debian_11.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_other_linux_8.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_other_linux_8.mdx index 21c97d19796..27c115f652e 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_other_linux_8.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_other_linux_8.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -43,13 +43,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_other_linux_9.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_other_linux_9.mdx index b41ad72d0a9..e6201aa78c3 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_other_linux_9.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_other_linux_9.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -43,13 +43,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_rhel_7.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_rhel_7.mdx index 4beb75fd79c..568b8c3be9b 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_rhel_7.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_rhel_7.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -43,13 +43,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_rhel_8.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_rhel_8.mdx index 49c1c425a17..ad6d989ce40 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_rhel_8.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_rhel_8.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -43,7 +43,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_rhel_9.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_rhel_9.mdx index 88361ad96cc..70e4239a81f 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_rhel_9.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_rhel_9.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -43,7 +43,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_sles_12.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_sles_12.mdx index d6a933b8285..4ee5798b9c1 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_sles_12.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_sles_12.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -43,13 +43,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_sles_15.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_sles_15.mdx index c935bb7b2f4..6f242b75d9e 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_sles_15.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_sles_15.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -43,14 +43,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_ubuntu_18.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_ubuntu_18.mdx index ae5de0c19f8..4ddce819ee5 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_ubuntu_18.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_ubuntu_18.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx index 4ea3511f7b3..8fa7f773518 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_ubuntu_22.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_ubuntu_22.mdx index e9d0c8cb9dd..63203f3b3d5 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_ubuntu_22.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/linux_x86_64/jdbc_ubuntu_22.mdx @@ -23,7 +23,7 @@ Before you begin the installation process: - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/index.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/index.mdx index 17655316382..30eb9ec70de 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/index.mdx @@ -16,7 +16,7 @@ navigation: - mtk_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_rhel_8.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_rhel_8.mdx index 8ed2c8b1e8b..1b3b8989d03 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_rhel_8.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_rhel_8.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_rhel_9.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_rhel_9.mdx index bedf40ef31b..f40e62ca1c1 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_rhel_9.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_rhel_9.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_sles_12.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_sles_12.mdx index 32e4b01c525..9eb37639dff 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_sles_12.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_sles_12.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,13 +33,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_sles_15.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_sles_15.mdx index ddb5b338615..b672ca956bc 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_sles_15.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_sles_15.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,14 +33,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/index.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/index.mdx index 4a93c59e1ca..aac1edce262 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/index.mdx @@ -25,7 +25,7 @@ navigation: - mtk_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_centos_7.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_centos_7.mdx index 452eea283e0..e9cb193dc7d 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_centos_7.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_centos_7.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,7 +33,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_debian_10.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_debian_10.mdx index 5b9abcadc8f..ad9b1e5825c 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_debian_10.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_debian_10.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_debian_11.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_debian_11.mdx index f07feb70155..33da22f5a2f 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_debian_11.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_debian_11.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_other_linux_8.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_other_linux_8.mdx index 4755e69bf17..d4ecfd1f5a2 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_other_linux_8.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_other_linux_8.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_other_linux_9.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_other_linux_9.mdx index 6859788238d..e7049395736 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_other_linux_9.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_other_linux_9.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_7.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_7.mdx index 5e85c502d03..e59dc64df8e 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_7.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_7.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,7 +33,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Address other prerequisites +- Address other prerequisites: ```shell # Install the EPEL repository: sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_8.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_8.mdx index 5dd82715cb4..ddbd15a38f3 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_8.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_8.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_9.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_9.mdx index 7191a883e7d..a9d2068a5c1 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_9.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_9.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_sles_12.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_sles_12.mdx index d4782505260..8632a26c0c3 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_sles_12.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_sles_12.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,13 +33,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_sles_15.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_sles_15.mdx index 1350ee0177a..0a8bb067c91 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_sles_15.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_sles_15.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -33,14 +33,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_ubuntu_18.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_ubuntu_18.mdx index 4169fb19ddd..b01e93ccb98 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_ubuntu_18.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_ubuntu_18.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_ubuntu_20.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_ubuntu_20.mdx index bb33e859024..de0421c983f 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_ubuntu_20.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_ubuntu_20.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_ubuntu_22.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_ubuntu_22.mdx index 72d8e1ddb84..cb66e27282a 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_ubuntu_22.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_ubuntu_22.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/index.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/index.mdx index 6867fb53854..d2526dc4868 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/index.mdx @@ -16,7 +16,7 @@ navigation: - mongo_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_rhel_8.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_rhel_8.mdx index b9e0fdaa08a..8cfbc21dcff 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_rhel_8.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_rhel_9.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_rhel_9.mdx index e849255824a..4d757153289 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_rhel_9.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_sles_12.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_sles_12.mdx index f99c3f9afc4..eac45bd5069 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_sles_12.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_sles_15.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_sles_15.mdx index 6a55dc77e7c..157004ec7ef 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_sles_15.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/index.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/index.mdx index fd34d74d503..ef0dac228ec 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/index.mdx @@ -25,7 +25,7 @@ navigation: - mongo_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_centos_7.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_centos_7.mdx index e3bbf0a5b2b..ee94655c07b 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_centos_7.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_centos_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_debian_10.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_debian_10.mdx index f72e0b76043..1628ac365c1 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_debian_10.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_debian_10.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_debian_11.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_debian_11.mdx index 66a6ebc9ef2..94f61ecf75a 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_debian_11.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_debian_11.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_other_linux_8.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_other_linux_8.mdx index 482321f53c5..ddd99de21c9 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_other_linux_8.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_other_linux_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_other_linux_9.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_other_linux_9.mdx index 1eda6d5d827..a4facfe3b6c 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_other_linux_9.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_other_linux_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_7.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_7.mdx index 2d1b069d3ba..9ec672e9df3 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_7.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_8.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_8.mdx index fed3d55fa26..bfeeaf49ac6 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_8.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_9.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_9.mdx index 93f785f6526..a0d8801b8fe 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_9.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_sles_12.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_sles_12.mdx index cbd3491cfed..2e85c617b13 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_sles_12.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_sles_15.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_sles_15.mdx index 70b5c13188c..d40769da60d 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_sles_15.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_ubuntu_18.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_ubuntu_18.mdx index 0f4ffd7419f..3d26378928d 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_ubuntu_18.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_ubuntu_18.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_ubuntu_20.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_ubuntu_20.mdx index 9901fcc18cf..b983e0ba4ff 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_ubuntu_20.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_ubuntu_20.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_ubuntu_22.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_ubuntu_22.mdx index 518a986e7ec..0f6b3507534 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_ubuntu_22.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_ubuntu_22.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/index.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/index.mdx index 1fd4b278ea3..fa25126dd00 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/index.mdx @@ -16,7 +16,7 @@ navigation: - mysql_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_rhel_8.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_rhel_8.mdx index fbab053a443..18b831a2d7b 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_rhel_8.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_rhel_9.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_rhel_9.mdx index df28b7f95f3..910afbb36d2 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_rhel_9.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_sles_12.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_sles_12.mdx index 86fcd8287e2..0e333d089cf 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_sles_12.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,25 +39,25 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the MySQL community repository +- Install the MySQL community repository: ```shell sudo wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm rpm --import /etc/RPM-GPG-KEY-mysql-2022 ``` -- Enable the MySQL8 repository and disable the MySQL 5 repository +- Enable the MySQL8 repository and disable the MySQL 5 repository: ```shell sudo zypper modifyrepo -e mysql80-community sudo zypper modifyrepo -d mysql57-community ``` -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_sles_15.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_sles_15.mdx index 7405cb0dbba..9be36b6b434 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_sles_15.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,26 +39,26 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the MySQL community repository +- Install the MySQL community repository: ```shell sudo wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm rpm --import /etc/RPM-GPG-KEY-mysql-2022 ``` -- Enable the MySQL8 repository and disable the MySQL 5 repository +- Enable the MySQL8 repository and disable the MySQL 5 repository: ```shell sudo zypper modifyrepo -e mysql80-community sudo zypper modifyrepo -d mysql57-community ``` -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/index.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/index.mdx index 3907c52a3cc..d6e556f181e 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/index.mdx @@ -25,7 +25,7 @@ navigation: - mysql_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_centos_7.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_centos_7.mdx index e35b2ef32c0..83d0f78b10a 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_centos_7.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_centos_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,17 +39,17 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Download and install the MySQL repo +- Download and install the MySQL repo: ```shell sudo yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm ``` -- Enable the MySQL repo +- Enable the MySQL repo: ```shell # For MySQL 8: diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_10.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_10.mdx index 6c4980528fc..6b5231ae149 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_10.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_10.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Download the GPG key to your APT keyring directly using the apt-key utility +- Download the GPG key to your APT keyring directly using the apt-key utility: ```shell sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 3A79BD29 ``` -- Install and configure the MySQL repo +- Install and configure the MySQL repo: ```shell # For MySQL 8: diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_11.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_11.mdx index 9595367baf3..44ef11ece8d 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_11.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_11.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Address other prerequisites +- Address other prerequisites: ```shell # Download the GPG key to your APT keyring directly using the apt-key utility: diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_other_linux_8.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_other_linux_8.mdx index 6c6ec8d241b..e56fea3ce7b 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_other_linux_8.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_other_linux_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_other_linux_9.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_other_linux_9.mdx index 163368ca5b8..a5d0fe201f7 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_other_linux_9.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_other_linux_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_7.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_7.mdx index 6e7c7a54a35..9f9b2c34ab1 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_7.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,23 +39,23 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` -- Download and install the MYSQL repo +- Download and install the MYSQL repo: ```shell sudo yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm ``` -- Enable the MYSQL repo +- Enable the MYSQL repo: ```shell # For MySQL 8: diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_8.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_8.mdx index 61908cc2900..312d2805f9f 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_8.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_9.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_9.mdx index 5ecf21976ac..0ec44ff543b 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_9.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_sles_12.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_sles_12.mdx index ebb5f783447..88b12988b67 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_sles_12.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,25 +39,25 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the MySQL community repository +- Install the MySQL community repository: ```shell sudo wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm rpm --import /etc/RPM-GPG-KEY-mysql-2022 ``` -- Enable the MySQL8 repository and disable the MySQL 5 repository +- Enable the MySQL8 repository and disable the MySQL 5 repository: ```shell sudo zypper modifyrepo -e mysql80-community sudo zypper modifyrepo -d mysql57-community ``` -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_sles_15.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_sles_15.mdx index 0a2d5d6771a..50f049b4de7 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_sles_15.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,26 +39,26 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the MySQL community repository +- Install the MySQL community repository: ```shell sudo wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm rpm --import /etc/RPM-GPG-KEY-mysql-2022 ``` -- Enable the MySQL8 repository and disable the MySQL 5 repository +- Enable the MySQL8 repository and disable the MySQL 5 repository: ```shell sudo zypper modifyrepo -e mysql80-community sudo zypper modifyrepo -d mysql57-community ``` -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_ubuntu_18.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_ubuntu_18.mdx index 8d6a3451629..a68421e0fa7 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_ubuntu_18.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_ubuntu_18.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Address other prerequisites +- Address other prerequisites: ```shell # Download the GPG key to your APT keyring directly using the apt-key utility: diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_ubuntu_20.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_ubuntu_20.mdx index cea0bf26fa9..d1cf4276103 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_ubuntu_20.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_ubuntu_20.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_ubuntu_22.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_ubuntu_22.mdx index 2f3cefd8bfe..ad3ad0725ec 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_ubuntu_22.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_ubuntu_22.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/index.mdx b/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/index.mdx index e2bbd20aebb..225be426ffb 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/index.mdx @@ -16,7 +16,7 @@ navigation: - ocl_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_rhel_8.mdx index 407a18e40f1..644e90c31bf 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_rhel_8.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_rhel_9.mdx index e41b1ec13f0..9decf1cec76 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_rhel_9.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_sles_12.mdx index 6aa814f8430..5fe93acde6f 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_sles_12.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_sles_15.mdx index 0a8aa7aeca9..a1a18975d88 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_sles_15.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/index.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/index.mdx index 79825e363df..ccdde6b0a74 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/index.mdx @@ -25,7 +25,7 @@ navigation: - ocl_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_centos_7.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_centos_7.mdx index 417a2f4acb3..32bfdf98c07 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_centos_7.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_centos_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_debian_10.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_debian_10.mdx index 1cac9322ae2..60ef298a9d9 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_debian_10.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_debian_10.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_debian_11.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_debian_11.mdx index 8dc90ce54f6..cf16ad93370 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_debian_11.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_debian_11.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_other_linux_8.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_other_linux_8.mdx index c1700215935..d3121909bd1 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_other_linux_8.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_other_linux_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_other_linux_9.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_other_linux_9.mdx index 744efce99ca..4f3d9a98536 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_other_linux_9.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_other_linux_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_7.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_7.mdx index 30ef24cc1d4..eaffe882b4a 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_7.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_8.mdx index 9436df469fc..37433595a0e 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_8.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_9.mdx index 0a9ef598341..4a6de89f2d5 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_9.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_sles_12.mdx index 4e958947ee7..4db2c7c0b6f 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_sles_12.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_sles_15.mdx index 1371e2ddf4f..b1e9b35f2dc 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_sles_15.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_ubuntu_18.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_ubuntu_18.mdx index 3f94a00d9f5..9651d44a898 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_ubuntu_18.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_ubuntu_18.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_ubuntu_20.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_ubuntu_20.mdx index 9c76c3b0b7b..bb89532199f 100644 --- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_ubuntu_20.mdx +++ b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_ubuntu_20.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/index.mdx b/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/index.mdx index e2bbd20aebb..225be426ffb 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/index.mdx @@ -16,7 +16,7 @@ navigation: - ocl_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_rhel_8.mdx index 47a4b1a65a4..e807b9a1b2a 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_rhel_8.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_rhel_9.mdx index 5ed2ea34859..f062e997850 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_rhel_9.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_sles_12.mdx index c94b0b0ab72..41e5c0199d8 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_sles_12.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_sles_15.mdx index f19d5d61583..922ba0b2c23 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_sles_15.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/index.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/index.mdx index 1df66e21511..7f0847898a3 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/index.mdx @@ -25,7 +25,7 @@ navigation: - ocl_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_centos_7.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_centos_7.mdx index fc83c755048..f79c6dbaa82 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_centos_7.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_centos_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_debian_10.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_debian_10.mdx index a7607d619fe..d19a2b41a28 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_debian_10.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_debian_10.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_debian_11.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_debian_11.mdx index a76bfb3cb21..ae3cb3405ac 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_debian_11.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_debian_11.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_other_linux_8.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_other_linux_8.mdx index 2969811a6b8..7e4f344c2cb 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_other_linux_8.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_other_linux_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_other_linux_9.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_other_linux_9.mdx index 357d8a8f72d..1df2cd2c0fd 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_other_linux_9.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_other_linux_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_7.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_7.mdx index 9d21451ba0b..19070b5ce72 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_7.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_8.mdx index ee0ccf118c7..37b76de73f3 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_8.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_9.mdx index bc86669f3d5..cc84cedea39 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_9.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_sles_12.mdx index 9303841f8fb..863f6bdb4cb 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_sles_12.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_sles_15.mdx index f808e39de3f..54f2f854c18 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_sles_15.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_ubuntu_18.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_ubuntu_18.mdx index 717d694f49e..f791fc3f257 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_ubuntu_18.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_ubuntu_18.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_ubuntu_20.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_ubuntu_20.mdx index 4de09b2438f..e4c9c508378 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_ubuntu_20.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_ubuntu_20.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_ubuntu_22.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_ubuntu_22.mdx index 96d81a5f3a0..2cf14134c10 100644 --- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_ubuntu_22.mdx +++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_ubuntu_22.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/index.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/index.mdx index 24c35c42528..2051bc77f7d 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/index.mdx @@ -16,7 +16,7 @@ navigation: - odbc_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx index 394a6a48aaf..43763848216 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_9.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_9.mdx index 1af5834c9c1..0bb9aab169a 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_9.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx index 76d2eab1d0f..eadd467df54 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_15.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_15.mdx index 66227e5f15f..ac20d9f0696 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_15.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/index.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/index.mdx index 77b357ec0d2..f8815ac6a4c 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/index.mdx @@ -25,7 +25,7 @@ navigation: - odbc_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx index c80582d18ce..b6d97d5a3a4 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx index 09463aa8551..c4a97d2488a 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_11.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_11.mdx index e3e94f62bff..97225a3a6ca 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_11.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_11.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_8.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_8.mdx index 94dae773be9..918cf6ef710 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_8.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_9.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_9.mdx index b94d2a6318d..77d9049ea8c 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_9.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx index 7afaf627827..7f559cef450 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx index 64cfb422b31..2d99bb0458a 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_9.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_9.mdx index 0515e3c9425..b2a9237eaed 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_9.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx index d2b39f1a1b2..036e4128907 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx index dc48cac2a23..cca6bf4b2ff 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx index 577f75646a8..f1a0276bace 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_20.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_20.mdx index e5eed5ecb79..74196019ffd 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_20.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_20.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_22.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_22.mdx index 60cc33e902f..b780e704aac 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_22.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_22.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/index.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/index.mdx index cf46ef4b31d..bd416f10392 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/index.mdx @@ -17,7 +17,7 @@ navigation: - pem_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx index b3f840ce754..baf63d9ce0f 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_8.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx index 559b1533294..9ff8005f7e0 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_rhel_9.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx index b6dfb9a2131..d7c0f2a107a 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_12.mdx @@ -21,7 +21,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: @@ -46,13 +46,13 @@ Before you begin the installation process: - Review [configuration and authentication requirements](../prerequisites/) for PEM. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx index ebfa6a0afe6..ff9f9c51e17 100644 --- a/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx +++ b/product_docs/docs/pem/8/installing/linux_ppc64le/pem_sles_15.mdx @@ -21,7 +21,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: @@ -46,7 +46,7 @@ Before you begin the installation process: - Review [configuration and authentication requirements](../prerequisites/) for PEM. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell # You can use SLES 15 SP3 for PEM 8.3 and later: @@ -57,7 +57,7 @@ Before you begin the installation process: ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/index.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/index.mdx index 113089919b8..449a28e3cfc 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/index.mdx @@ -26,7 +26,7 @@ navigation: - pem_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx index e8d93c7f10a..05ef5b0a7ff 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_centos_7.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx index a0154d4672c..79ba1612af3 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_10.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx index 376d1ed8678..4f2577265b7 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_debian_11.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx index 43009817530..ab35eaf12a9 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_8.mdx @@ -18,7 +18,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx index 5415e049ae6..0168048ba24 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_other_linux_9.mdx @@ -18,7 +18,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx index a3376575db7..2c553141972 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_7.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx index 4933c0eb673..6a97d006fdf 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_8.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx index bc70cc9d94d..166a865dea5 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_rhel_9.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx index 6b81f0c92fb..dc0730e8ca7 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_12.mdx @@ -21,7 +21,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: @@ -46,13 +46,13 @@ Before you begin the installation process: - Review [configuration and authentication requirements](../prerequisites/) for PEM. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx index a1a8e5d47c4..84b683ec804 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_sles_15.mdx @@ -21,7 +21,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: @@ -46,7 +46,7 @@ Before you begin the installation process: - Review [configuration and authentication requirements](../prerequisites/) for PEM. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell # You can use SLES 15 SP3 for PEM 8.3 and later: @@ -57,7 +57,7 @@ Before you begin the installation process: ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_18.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_18.mdx index 23f710a0f30..b54bcaba898 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_18.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_18.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx index c483d47fc3a..8a8bdb2bd65 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_20.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx index ae21bff5cb5..78b6c571be3 100644 --- a/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx +++ b/product_docs/docs/pem/8/installing/linux_x86_64/pem_ubuntu_22.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/index.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/index.mdx index 0a6f75b809f..2313da49884 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/index.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/index.mdx @@ -16,7 +16,7 @@ navigation: - pem_agent_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_rhel_8.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_rhel_8.mdx index a742fbf9db1..e475f2f47d6 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_rhel_8.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_rhel_8.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_rhel_9.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_rhel_9.mdx index e8d435dd9db..5a988064b97 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_rhel_9.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_rhel_9.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_sles_12.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_sles_12.mdx index 189cef564c6..632c67284f2 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_sles_12.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_sles_12.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -37,13 +37,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_sles_15.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_sles_15.mdx index dbba9633dc1..9e8fece35f6 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_sles_15.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_sles_15.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -37,7 +37,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell # You can use SLES 15 SP3 for PEM 8.3 and later: @@ -48,7 +48,7 @@ Before you begin the installation process: ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/index.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/index.mdx index 1822e0392f5..18497e53840 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/index.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/index.mdx @@ -25,7 +25,7 @@ navigation: - pem_agent_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_centos_7.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_centos_7.mdx index 90b8bec3364..ec3c8491a03 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_centos_7.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_centos_7.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_debian_10.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_debian_10.mdx index a7b6557a898..15902e44c80 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_debian_10.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_debian_10.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_debian_11.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_debian_11.mdx index 13270e3f015..c33c4cdf04d 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_debian_11.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_debian_11.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_other_linux_8.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_other_linux_8.mdx index 36b04e32199..2df888213d2 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_other_linux_8.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_other_linux_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_other_linux_9.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_other_linux_9.mdx index 84e26fabf1d..48bd22ae79b 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_other_linux_9.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_other_linux_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_7.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_7.mdx index 04e7e6336e7..c99732ff0af 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_7.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_7.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_8.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_8.mdx index 4ef3e776bfa..6bb46f3d22b 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_8.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_8.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_9.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_9.mdx index 0f25c0f42c4..130352e8caa 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_9.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_9.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_sles_12.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_sles_12.mdx index abd9add71fa..62683383dcc 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_sles_12.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_sles_12.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -37,13 +37,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_sles_15.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_sles_15.mdx index 8f333e4d07b..bf90992be44 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_sles_15.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_sles_15.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -37,7 +37,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell # You can use SLES 15 SP3 for PEM 8.3 and later: @@ -48,7 +48,7 @@ Before you begin the installation process: ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_18.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_18.mdx index 5addcd7ce8d..3396cd17a52 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_18.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_18.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_20.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_20.mdx index 8c6893192ae..d84a434fab3 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_20.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_20.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_22.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_22.mdx index 9dea90e3501..7333eabca30 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_22.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_22.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/index.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/index.mdx index f3c72b4de3d..9f844d72be3 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/index.mdx @@ -17,7 +17,7 @@ navigation: - pem_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx index 5bb7291718e..b4085dddb46 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_8.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx index b703600ed07..9f804f241f1 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_rhel_9.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx index be0456cfbdb..a3c750413d7 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx @@ -21,7 +21,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: @@ -46,13 +46,13 @@ Before you begin the installation process: - Review [configuration and authentication requirements](../prerequisites/) for PEM. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx index 42298c5aa22..bdc2ae521ed 100644 --- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx +++ b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_15.mdx @@ -21,7 +21,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: @@ -46,7 +46,7 @@ Before you begin the installation process: - Review [configuration and authentication requirements](../prerequisites/) for PEM. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell # You can use SLES 15 SP3 for PEM 8.3 and later: @@ -57,7 +57,7 @@ Before you begin the installation process: ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/index.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/index.mdx index b775a7a673b..484c53b6497 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/index.mdx @@ -26,7 +26,7 @@ navigation: - pem_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx index 7a9dbc8084a..e5adf907b55 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx index 6d503840d49..d9fb512340c 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx index cd181e97167..cb8034c98d4 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_11.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx index 0f858ebf69a..d0d1d27da0f 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_8.mdx @@ -18,7 +18,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx index 0c84be7ed56..7bf9b704295 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_other_linux_9.mdx @@ -18,7 +18,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx index ce5050e7473..d667314d9ff 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx index c17e2a189dd..9bc79f25be6 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_8.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx index 0c48e0fe3ad..34c4442af4c 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_9.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx index bfeb88058ac..fd002ff92f5 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx @@ -21,7 +21,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: @@ -46,13 +46,13 @@ Before you begin the installation process: - Review [configuration and authentication requirements](../prerequisites/) for PEM. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx index dd7a7a09612..0d19fd43e3a 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_15.mdx @@ -21,7 +21,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: @@ -46,7 +46,7 @@ Before you begin the installation process: - Review [configuration and authentication requirements](../prerequisites/) for PEM. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell # You can use SLES 15 SP3 for PEM 8.3 and later: @@ -57,7 +57,7 @@ Before you begin the installation process: ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_18.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_18.mdx index 50b2cca834b..d22bcc5136c 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_18.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_18.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx index 94f4d591b49..89a6e7c6c69 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_20.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx index 58f86de0312..46ae2a6a3e8 100644 --- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx +++ b/product_docs/docs/pem/9/installing/linux_x86_64/pem_ubuntu_22.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the repository +- Set up the repository. Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. To determine if your repository exists, enter this command: diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/index.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/index.mdx index c23d57bd3f2..31974f8eb70 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/index.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/index.mdx @@ -16,7 +16,7 @@ navigation: - pem_agent_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_rhel_8.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_rhel_8.mdx index 34e8c6a3bc6..a58c945b1a3 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_rhel_8.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_rhel_8.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_rhel_9.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_rhel_9.mdx index d3220a4ae01..a51f4a317ba 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_rhel_9.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_rhel_9.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_sles_12.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_sles_12.mdx index 5b6cfa71cd8..7f14539c8cb 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_sles_12.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_sles_12.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -37,13 +37,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_sles_15.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_sles_15.mdx index fca9b9b1bed..fc83c706c70 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_sles_15.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_sles_15.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -37,7 +37,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell # You can use SLES 15 SP3 for PEM 8.3 and later: @@ -48,7 +48,7 @@ Before you begin the installation process: ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/index.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/index.mdx index 6794e8fe5e8..261be996af1 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/index.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/index.mdx @@ -25,7 +25,7 @@ navigation: - pem_agent_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_centos_7.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_centos_7.mdx index 3d2f047b728..5baa5a066e4 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_centos_7.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_centos_7.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_debian_10.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_debian_10.mdx index 88ea9cc132c..36576d76200 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_debian_10.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_debian_10.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_debian_11.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_debian_11.mdx index a5fe53bf126..0b25f6f3f5a 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_debian_11.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_debian_11.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_other_linux_8.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_other_linux_8.mdx index 221493418d5..38d5ef4018b 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_other_linux_8.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_other_linux_8.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_other_linux_9.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_other_linux_9.mdx index 40fce90e6a2..0635f114f55 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_other_linux_9.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_other_linux_9.mdx @@ -14,7 +14,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_7.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_7.mdx index 346e52d1809..d0eb676f56b 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_7.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_7.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_8.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_8.mdx index b576d1c6593..dd16f9219b7 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_8.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_8.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_9.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_9.mdx index 9669e36a686..be6882b65e8 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_9.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_9.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_sles_12.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_sles_12.mdx index 4bae14d9b30..6d3e2a11934 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_sles_12.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_sles_12.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -37,13 +37,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_sles_15.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_sles_15.mdx index 39dc81df22d..83dc1326122 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_sles_15.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_sles_15.mdx @@ -17,7 +17,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -37,7 +37,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell # You can use SLES 15 SP3 for PEM 8.3 and later: @@ -48,7 +48,7 @@ Before you begin the installation process: ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_18.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_18.mdx index 4905c1add73..85f8ee81632 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_18.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_18.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_20.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_20.mdx index f9b4d196b42..f247f8221a3 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_20.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_20.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_22.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_22.mdx index 45164d7c91b..1960134d0cf 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_22.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_ubuntu_22.mdx @@ -13,7 +13,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/index.mdx b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/index.mdx index b373a0885ee..db8e2247429 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/index.mdx @@ -18,7 +18,7 @@ navigation: - pgbouncer_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_8.mdx b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_8.mdx index f5a9b3381b5..ef19ee0a010 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_8.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_9.mdx b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_9.mdx index 2cc997e8224..a039730cecf 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_9.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_12.mdx b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_12.mdx index 3dd802684ac..1871947ca24 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_12.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_15.mdx b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_15.mdx index 413a5d3e0b2..9fba63a1e5c 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_15.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/index.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/index.mdx index 8e7f7cbd9f6..29b04c8946f 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/index.mdx @@ -27,7 +27,7 @@ navigation: - pgbouncer_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_centos_7.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_centos_7.mdx index e0f96e36003..fb2d3426827 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_centos_7.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_centos_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_10.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_10.mdx index a47083850e4..3eb41a9e452 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_10.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_10.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_11.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_11.mdx index 772872c195d..563f72bfcd2 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_11.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_11.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_8.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_8.mdx index ab517586f63..a9be3d6389b 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_8.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_9.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_9.mdx index 394ce1b8825..d8ffe024929 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_9.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_other_linux_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_7.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_7.mdx index 849a32c9176..837d43942d4 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_7.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_8.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_8.mdx index 5b0672115df..440014b30ec 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_8.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_9.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_9.mdx index dd9da039b93..73ef555be4b 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_9.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_12.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_12.mdx index 1a391ebfcda..9c47eebf24d 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_12.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_15.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_15.mdx index 21bd3c97d2b..10e732d00d4 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_15.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_18.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_18.mdx index 7b5c43a712a..ce2eba28cb6 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_18.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_18.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_20.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_20.mdx index d9be77de9e5..a1a688dd59f 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_20.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_20.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_22.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_22.mdx index c080c34c4ec..7d880f99801 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_22.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_ubuntu_22.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/index.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/index.mdx index 85916f6a91b..ca192acc278 100644 --- a/product_docs/docs/pge/15/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/pge/15/installing/linux_x86_64/index.mdx @@ -18,7 +18,7 @@ navigation: - pge_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/pge_centos_7.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/pge_centos_7.mdx index ac2c270bb0b..3c46ca81aae 100644 --- a/product_docs/docs/pge/15/installing/linux_x86_64/pge_centos_7.mdx +++ b/product_docs/docs/pge/15/installing/linux_x86_64/pge_centos_7.mdx @@ -12,7 +12,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -32,7 +32,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/pge_debian_10.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/pge_debian_10.mdx index 20efb57d10e..33db78f6702 100644 --- a/product_docs/docs/pge/15/installing/linux_x86_64/pge_debian_10.mdx +++ b/product_docs/docs/pge/15/installing/linux_x86_64/pge_debian_10.mdx @@ -12,7 +12,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/pge_debian_11.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/pge_debian_11.mdx index 25c34925642..c557e2d2b02 100644 --- a/product_docs/docs/pge/15/installing/linux_x86_64/pge_debian_11.mdx +++ b/product_docs/docs/pge/15/installing/linux_x86_64/pge_debian_11.mdx @@ -12,7 +12,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/pge_other_linux_8.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/pge_other_linux_8.mdx index 73403cc3df0..ccd0fc2dd4d 100644 --- a/product_docs/docs/pge/15/installing/linux_x86_64/pge_other_linux_8.mdx +++ b/product_docs/docs/pge/15/installing/linux_x86_64/pge_other_linux_8.mdx @@ -12,7 +12,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -32,13 +32,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/pge_other_linux_9.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/pge_other_linux_9.mdx index 117317d66f7..9dde370c886 100644 --- a/product_docs/docs/pge/15/installing/linux_x86_64/pge_other_linux_9.mdx +++ b/product_docs/docs/pge/15/installing/linux_x86_64/pge_other_linux_9.mdx @@ -12,7 +12,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -32,13 +32,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_7.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_7.mdx index 1f2176f55c4..72b8a36b467 100644 --- a/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_7.mdx +++ b/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_7.mdx @@ -12,7 +12,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -32,13 +32,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_8.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_8.mdx index 6b38cd32477..04a9ee7570e 100644 --- a/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_8.mdx +++ b/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_8.mdx @@ -12,7 +12,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -32,7 +32,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_9.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_9.mdx index 3049a7ff9ce..ab4f396ec87 100644 --- a/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_9.mdx +++ b/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_9.mdx @@ -12,7 +12,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -32,7 +32,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/pge_ubuntu_18.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/pge_ubuntu_18.mdx index c416d16ea20..d82b4dc55bc 100644 --- a/product_docs/docs/pge/15/installing/linux_x86_64/pge_ubuntu_18.mdx +++ b/product_docs/docs/pge/15/installing/linux_x86_64/pge_ubuntu_18.mdx @@ -12,7 +12,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/pge_ubuntu_20.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/pge_ubuntu_20.mdx index 40c7ae7e57b..1de88ccf30a 100644 --- a/product_docs/docs/pge/15/installing/linux_x86_64/pge_ubuntu_20.mdx +++ b/product_docs/docs/pge/15/installing/linux_x86_64/pge_ubuntu_20.mdx @@ -12,7 +12,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/pge_ubuntu_22.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/pge_ubuntu_22.mdx index 6e6f87afcdc..b09984f5fee 100644 --- a/product_docs/docs/pge/15/installing/linux_x86_64/pge_ubuntu_22.mdx +++ b/product_docs/docs/pge/15/installing/linux_x86_64/pge_ubuntu_22.mdx @@ -12,7 +12,7 @@ redirects: Before you begin the installation process: -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgpool/4/installing/linux_ppc64le/index.mdx b/product_docs/docs/pgpool/4/installing/linux_ppc64le/index.mdx index 4ec4e24895d..864faa4347b 100644 --- a/product_docs/docs/pgpool/4/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_ppc64le/index.mdx @@ -17,7 +17,7 @@ navigation: - pgpool_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_rhel_8.mdx b/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_rhel_8.mdx index 5bb6d6e4ad5..699b85b7368 100644 --- a/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_rhel_8.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_rhel_9.mdx b/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_rhel_9.mdx index 9690e60fdfe..bcf128882b1 100644 --- a/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_rhel_9.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_sles_12.mdx b/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_sles_12.mdx index 6eba1e057dc..63774023c1d 100644 --- a/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_sles_12.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_sles_15.mdx b/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_sles_15.mdx index 73a027047db..143a26998e7 100644 --- a/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_sles_15.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/index.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/index.mdx index bf1bab46121..d37a8c41caa 100644 --- a/product_docs/docs/pgpool/4/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/index.mdx @@ -30,7 +30,7 @@ navigation: - pgpool_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_centos_7.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_centos_7.mdx index ec8638c6960..1c2d61281d7 100644 --- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_centos_7.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_centos_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_debian_10.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_debian_10.mdx index 1f96a3f68e0..48819468e31 100644 --- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_debian_10.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_debian_10.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_debian_11.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_debian_11.mdx index 3c8acf3a2ea..f0659dbedb0 100644 --- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_debian_11.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_debian_11.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_other_linux_8.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_other_linux_8.mdx index ebeb788de27..5c3a849f5e6 100644 --- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_other_linux_8.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_other_linux_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_other_linux_9.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_other_linux_9.mdx index 9accfdf0fb3..6668acf83a0 100644 --- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_other_linux_9.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_other_linux_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_7.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_7.mdx index b5dea08ff21..dc6e3a147c4 100644 --- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_7.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_8.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_8.mdx index f9ff9cfe157..c50633ff389 100644 --- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_8.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_9.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_9.mdx index 9578431eb5b..ad13c4c899b 100644 --- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_9.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_sles_12.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_sles_12.mdx index 059e7d106cb..286316adc94 100644 --- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_sles_12.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_sles_15.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_sles_15.mdx index 1762d657ff3..25b41fac7d2 100644 --- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_sles_15.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_ubuntu_18.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_ubuntu_18.mdx index ee825dd2409..1a84baf94f7 100644 --- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_ubuntu_18.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_ubuntu_18.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_ubuntu_20.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_ubuntu_20.mdx index 2181efa846f..89260672d49 100644 --- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_ubuntu_20.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_ubuntu_20.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_ubuntu_22.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_ubuntu_22.mdx index 2cd84d90a24..e999ccefa92 100644 --- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_ubuntu_22.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_ubuntu_22.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/index.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/index.mdx index b3748796de1..b4083bf8847 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/index.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/index.mdx @@ -16,7 +16,7 @@ navigation: - pgpoolext_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_rhel_8.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_rhel_8.mdx index 9916629e278..2d81be62d67 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_rhel_8.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_rhel_9.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_rhel_9.mdx index e4c56fc3e64..febf2a25044 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_rhel_9.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_sles_12.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_sles_12.mdx index f98386ffb24..00254563c07 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_sles_12.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_sles_15.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_sles_15.mdx index 3de0ae0b2a2..fbfbf525e55 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_sles_15.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/index.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/index.mdx index 0f33b10307f..87e76234a57 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/index.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/index.mdx @@ -29,7 +29,7 @@ navigation: - pgpoolext_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_centos_7.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_centos_7.mdx index 73baa442b6c..0e081fff04c 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_centos_7.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_centos_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_debian_10.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_debian_10.mdx index c81bef23bbc..c4b670dc412 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_debian_10.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_debian_10.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_debian_11.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_debian_11.mdx index 8d3beae7b24..1c4268ac7c6 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_debian_11.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_debian_11.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_other_linux_8.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_other_linux_8.mdx index 694ea0a18fa..e08162ccc53 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_other_linux_8.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_other_linux_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_other_linux_9.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_other_linux_9.mdx index c1ea6dd143d..5910325590a 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_other_linux_9.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_other_linux_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_7.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_7.mdx index e659ce2c756..3ae0c8fe86a 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_7.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_8.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_8.mdx index 8fd799b61de..57d253f3bd4 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_8.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_9.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_9.mdx index 92308768c4e..655e89597dc 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_9.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_sles_12.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_sles_12.mdx index b14d9b73b81..a22d9b0b1dd 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_sles_12.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_sles_15.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_sles_15.mdx index 617c723e75f..77cc5cd0032 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_sles_15.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_ubuntu_18.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_ubuntu_18.mdx index 3363ecee3ff..a612243e8d9 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_ubuntu_18.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_ubuntu_18.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_ubuntu_20.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_ubuntu_20.mdx index 25574e1f5f8..3eabd4854b3 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_ubuntu_20.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_ubuntu_20.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_ubuntu_22.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_ubuntu_22.mdx index 93cc534a0d5..39e7b071009 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_ubuntu_22.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_ubuntu_22.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/postgis/3.2/installing/linux_ppc64le/index.mdx b/product_docs/docs/postgis/3.2/installing/linux_ppc64le/index.mdx index 8a34d49dafe..516fff796f0 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_ppc64le/index.mdx @@ -17,7 +17,7 @@ navigation: - postgis_sles_12 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) diff --git a/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_rhel_8.mdx b/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_rhel_8.mdx index f64c56cddf1..ad1ea0c0ab1 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_rhel_8.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_rhel_9.mdx b/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_rhel_9.mdx index 5ed3ec74e3a..f238b987e4d 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_rhel_9.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,11 +39,11 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -- Refresh the cache +- Refresh the cache: ```shell sudo dnf makecache ``` diff --git a/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_sles_12.mdx b/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_sles_12.mdx index 8c535401266..6578b84112d 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_sles_12.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/ppc64le sudo SUSEConnect -p sle-sdk/12.5/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_sles_15.mdx b/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_sles_15.mdx index b03a8b9edd1..13187523eed 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_sles_15.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_ppc64le/postgis_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/ppc64le ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/postgis/3.2/installing/linux_x86_64/index.mdx b/product_docs/docs/postgis/3.2/installing/linux_x86_64/index.mdx index 926e41545e7..4c9479ce89a 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_x86_64/index.mdx @@ -26,7 +26,7 @@ navigation: - postgis_debian_10 --- -For operating system-specific install instructions, including accessing the repo, see: +Operating system-specific install instructions are described in the corresponding documentation: ### Red Hat Enterprise Linux (RHEL) and derivatives diff --git a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_centos_7.mdx b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_centos_7.mdx index d086bb910a3..91a3637feca 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_centos_7.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_centos_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` diff --git a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_debian_10.mdx b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_debian_10.mdx index 1a1d70f84bc..935a5bfb84a 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_debian_10.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_debian_10.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_debian_11.mdx b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_debian_11.mdx index 4852af27de8..6fbf8c353df 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_debian_11.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_debian_11.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_other_linux_8.mdx b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_other_linux_8.mdx index fca371fdc86..041a7ba6256 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_other_linux_8.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_other_linux_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_other_linux_9.mdx b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_other_linux_9.mdx index bdf91acc6ff..cc6b075a45b 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_other_linux_9.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_other_linux_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install epel-release ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell sudo dnf config-manager --set-enabled powertools ``` diff --git a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_rhel_7.mdx b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_rhel_7.mdx index 4de11e745e7..79ea1c8355a 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_rhel_7.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_rhel_7.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- Enable additional repositories to resolve dependencies +- Enable additional repositories to resolve dependencies: ```shell subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` diff --git a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_rhel_8.mdx b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_rhel_8.mdx index 38a9d4c5166..093705cdb54 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_rhel_8.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_rhel_8.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm diff --git a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_rhel_9.mdx b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_rhel_9.mdx index 2eece456b32..35ab9925953 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_rhel_9.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_rhel_9.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Install the EPEL repository +- Install the EPEL repository: ```shell sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm diff --git a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_sles_12.mdx b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_sles_12.mdx index 7d40d420062..6ec0ba7af04 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_sles_12.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_sles_12.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,13 +39,13 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/12.5/x86_64 sudo SUSEConnect -p sle-sdk/12.5/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_sles_15.mdx b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_sles_15.mdx index 24809549f78..426c305bbe3 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_sles_15.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_sles_15.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. @@ -39,14 +39,14 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Activate the required SUSE module +- Activate the required SUSE module: ```shell sudo SUSEConnect -p PackageHub/15.4/x86_64 ``` -- Refresh the metadata +- Refresh the metadata: ```shell sudo zypper refresh ``` diff --git a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_ubuntu_18.mdx b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_ubuntu_18.mdx index 3ea639c62dd..fdc933d7ec7 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_ubuntu_18.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_ubuntu_18.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_ubuntu_20.mdx b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_ubuntu_20.mdx index 3187c39b2f7..50cb99d141d 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_ubuntu_20.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_ubuntu_20.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. diff --git a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_ubuntu_22.mdx b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_ubuntu_22.mdx index ec10c354c0f..563b2d648f9 100644 --- a/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_ubuntu_22.mdx +++ b/product_docs/docs/postgis/3.2/installing/linux_x86_64/postgis_ubuntu_22.mdx @@ -19,7 +19,7 @@ Before you begin the installation process: - [Installing PostgreSQL](https://www.postgresql.org/download/) -- Set up the EDB repository +- Set up the EDB repository. Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. From 9895f882310075d53b2e2aab7943101815ab177c Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 12 Sep 2023 08:04:04 -0400 Subject: [PATCH 123/255] Agreements: screenshot policy --- docs/agreements/screenshot_policy.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 docs/agreements/screenshot_policy.md diff --git a/docs/agreements/screenshot_policy.md b/docs/agreements/screenshot_policy.md new file mode 100644 index 00000000000..8aee44c0907 --- /dev/null +++ b/docs/agreements/screenshot_policy.md @@ -0,0 +1,25 @@ +# Screenshot policy + +Industry best practices for screenshots have evolved over time. When user manuals were written to reflect both mainframe and, later, distributed systems products, users were primarily new to computers and needed step-by-step screenshots to use a product. As the collective knowledge of computers has grown and as users have become more sophisticated and knowledgeable about the applications they use, documentation no longer needs to provide users with a shot of every screen or dialog box. As our users have become more sophisticated, so have our user interfaces, such that information previously gleaned from screenshots are now intuited from the user interface itself. + +Screenshots also come with a cost that needs to be weighed against the value: + +- Environments need to be available and configured with the appropriate data. The type of data QA needs to test and what documentation needs for screenshots (sanitized, no proprietary information, and so on) are not the same. Maintaining usable data for the screenshots is an effort requiring resources outside of the documentation team. + +- Release-specific screenshots are a significant maintenance burden that doesn't scale. + +- If our documentation is translated, we need to contain the costs of translating and updating graphics by including only critical screenshots. + +## Screenshot guidelines + +The documentation team promotes the intentional use of screenshots based on customer needs. We include only screenshots that add value. The documentation team uses the following specific criteria to determine where a screenshot adds value: + +- We provide screenshots for complex dialog boxes; in some cases, we also provide callout text that is then explained in detail in accompanying procedures. Examples include dialog boxes that contain multiple subsets of information, with freeform text fields and many options available for selection. + +- We provide screenshots that help to orient users in a complicated procedure or to validate that what they see on the screen is correct. Screenshots are helpful when text alone cannot adequately or economically orient the users. + +- We might also provide screenshots to illustrate new features or concepts. This approach is helpful for users who are reading the documentation but not currently accessing the product. However, it is still important to choose screenshots carefully based on the needs of a moderately experienced user. We include screenshots only for features or concepts that are unique to our products, and not for familiar features or concepts that users might experience in other products or technologies (showing drop-down lists, file pickers, and so on). + +- We will accommodate internal and external customer requests for screenshots that improve the understanding of a procedure. + +- We do not provide screenshots for welcome, progress bar, print, confirmation (such as “Are you sure you want to delete this policy?”), message, and about screens. The information conveyed by such screens can be easily communicated in text. We do not provide screenshots for simple dialog box representations. Examples include dialog boxes and wizard pages that feature drop-down lists and option buttons with few or no freeform text fields. These intuitive, simple dialog boxes are easy to explain in text, and screenshots do not add context or value for the customer. \ No newline at end of file From 3e240e0f93073f57f0482561e7c9800fb66be253 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 12 Sep 2023 08:47:00 -0400 Subject: [PATCH 124/255] small grammatical fix suggested by Dee Dee --- .../templates/products/edb-postgres-advanced-server/base.njk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/install_template/templates/products/edb-postgres-advanced-server/base.njk b/install_template/templates/products/edb-postgres-advanced-server/base.njk index 8ad6b911bc4..0fac8cc0f49 100644 --- a/install_template/templates/products/edb-postgres-advanced-server/base.njk +++ b/install_template/templates/products/edb-postgres-advanced-server/base.njk @@ -63,7 +63,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql From 92ca575aafef066ca4d09388eeb8f1b43fb8da52 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 12 Sep 2023 10:15:52 -0400 Subject: [PATCH 125/255] BigAnimal: fixing PEM remote monitoring link --- .../release/using_cluster/05_monitoring_and_logging/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/index.mdx b/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/index.mdx index c63b8cc356f..c9b40ce04cc 100644 --- a/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/index.mdx @@ -20,7 +20,7 @@ With BigAnimal, you have a few options for monitoring and logging solutions: - BigAnimal provides a Prometheus-compatible endpoint you can use to connect to your own metrics infrastructure, such as your AWS Managed Grafana. It also provides the option to view logs from your cloud provider's blob storage solution. For more information, see [Other monitoring and logging solutions](other_monitoring). This ability is an optional solution when you're using your own cloud account but is the only option when using BigAnimal's cloud account. -- Existing Postgres Enterprise Manager (PEM) users who want to monitor BigAnimal clusters alongside self-managed Postgres clusters can use the remote monitoring capability of PEM. See [Remote monitoring](/pem/latest/pem_admin/02a_pem_remote_monitoring). +- Existing Postgres Enterprise Manager (PEM) users who want to monitor BigAnimal clusters alongside self-managed Postgres clusters can use the remote monitoring capability of PEM. See [Remote monitoring](/pem/latest/monitoring_performance/pem_remote_monitoring/). With remote monitoring, you have access to many PEM features, including the ability to profile the workloads on your BigAnimal clusters. See [Profiling workloads](/pem/latest/profiling_workloads) for more information. From a69f12f56947f846747a70b84bc396a9140266dd Mon Sep 17 00:00:00 2001 From: Florin Irion Date: Tue, 12 Sep 2023 17:13:13 +0200 Subject: [PATCH 126/255] Update upgrade_paths Set the range of accepted upgrade paths for BDR4 --- .../docs/pgd/4/upgrades/upgrade_paths.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/product_docs/docs/pgd/4/upgrades/upgrade_paths.mdx b/product_docs/docs/pgd/4/upgrades/upgrade_paths.mdx index 5d682abe58e..229b2cfc97a 100644 --- a/product_docs/docs/pgd/4/upgrades/upgrade_paths.mdx +++ b/product_docs/docs/pgd/4/upgrades/upgrade_paths.mdx @@ -15,17 +15,17 @@ before upgrading to 4. See [Upgrading within from 3.7](/pgd/3.7/bdr/upgrades/sup 3.7 documentation for more information. After upgrading to 3.7.15 or later, the following upgrade paths are possible. -| From version | To version | +| From version | To versions (range) | | ---- | -- | -| 3.7.15 | 4.0.2 or later | -| 3.7.16 | 4.1.0 or later | -| 3.7.17 | Must be upgraded to a later 3.7.x version before upgrading | -| 3.7.18 | 4.2.1 or later | -| 3.7.19 | 4.2.2 or later | -| 3.7.20 | 4.3.0 or later | -| 3.7.21 | 4.3.1 or later | -| 3.7.22 | 4.3.2 or later | +| 3.7.15 | 4.0.2 to 4.2.1 | +| 3.7.16 | 4.0.2 to 4.2.1 | +| 3.7.17 | 4.2.0 to 4.2.1 | +| 3.7.18 | 4.2.1 only | +| 3.7.19 | 4.2.2 only | +| 3.7.20 | 4.3.0 to 4.3.2 | +| 3.7.21 | 4.3.1 to 4.3.2 | +| 3.7.22 | 4.3.2 only | ## Upgrading from version 3.6 to version 4 -Currently there are no direct upgrade paths from 3.6 to 4. You must first upgrade your cluster to 3.7 before upgrading to 4. See [Upgrading from 3.6](/pgd/3.7/bdr/upgrades/supported_paths/#upgrading-from-version-36) in the 3.7 documentation for more information. \ No newline at end of file +Currently there are no direct upgrade paths from 3.6 to 4. You must first upgrade your cluster to 3.7 before upgrading to 4. See [Upgrading from 3.6](/pgd/3.7/bdr/upgrades/supported_paths/#upgrading-from-version-36) in the 3.7 documentation for more information. From f617f93d9531c24b60af81ffa2fc607ff5d8122d Mon Sep 17 00:00:00 2001 From: Florin Irion Date: Tue, 12 Sep 2023 17:40:42 +0200 Subject: [PATCH 127/255] Update upgrade_paths (#4822) * Update upgrade_paths Set the range of accepted upgrade paths for BDR5 Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com --- product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx b/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx index d911ba899e3..cc20091a7a8 100644 --- a/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx +++ b/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx @@ -19,7 +19,8 @@ release, before upgrading to the latest version 5 release. After upgrading to | ---- | -- | | 4.3.0 | 5.0.0 or later | | 4.3.1 | 5.1.0 or later | -| 4.3.2 | 5.2.0 or later | +| 4.3.2 | Upgrade to 5.3 (once it is released) | + ## Upgrading from version 3.7 to version 5 @@ -37,4 +38,4 @@ major version was supported by both PGD versions. Development is currently ongoing to provide a direct upgrade path from 3.7 to 5 using TPA by Q4. In the interim, customers may reach out to EDB Professional -Services or Support for assistance and guidance. \ No newline at end of file +Services or Support for assistance and guidance. From 39fe9fdc32ccfcf15f51a40c2a89111353bd3669 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 12 Sep 2023 13:40:29 -0400 Subject: [PATCH 128/255] minor copy edits --- advocacy_docs/migrating/oracle/factors_to_consider.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/migrating/oracle/factors_to_consider.mdx b/advocacy_docs/migrating/oracle/factors_to_consider.mdx index 68bf5e9d171..885351cf852 100644 --- a/advocacy_docs/migrating/oracle/factors_to_consider.mdx +++ b/advocacy_docs/migrating/oracle/factors_to_consider.mdx @@ -79,7 +79,7 @@ Why is that? Postgres and Oracle are very different under the hood, with different SQL planning and different storage and access patterns. Even the version control and transaction isolation are implemented in a different way. That makes it difficult to set up a simple formula that covers all possible permutations of Oracle configurations and architectures. All databases respond differently to the workload being run. -Customers of EDB who have migrated to EPAS have found performance on par with Oracle when using similar hardware. In some instances, depending on their workload, they even outperform Oracle. All our customers who migrated aimed to at least match Oracle's performance and, if feasible, to exceed it either on comparable hardware or by adding resources as needed. We (EDB) also suggest conducting a benchmark using your specific workload to ensure the system meets performance expectations and to plan production accordingly. +Customers of EDB who have migrated to EDB Postgres Advanced Server have found performance on par with Oracle when using similar hardware. In some instances, depending on their workload, they even outperform Oracle. All our customers who migrated aimed to at least match Oracle's performance and, if feasible, to exceed it either on comparable hardware or by adding resources as needed. We also suggest conducting a benchmark using your specific workload to ensure the system meets performance expectations and to plan production accordingly. ## Some best practice considerations From 1c81efcd627002a9e171565511dd62bb4394b22f Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 13 Sep 2023 11:07:27 +0100 Subject: [PATCH 129/255] Fixed link (was incorrectly going up tree) Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/limitations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/limitations.mdx b/product_docs/docs/pgd/5/limitations.mdx index 4e9690d6c4b..866f3c6f1f7 100644 --- a/product_docs/docs/pgd/5/limitations.mdx +++ b/product_docs/docs/pgd/5/limitations.mdx @@ -21,7 +21,7 @@ into account when planning your deployment. fail if one of the nodes were unresponsive. Consensus is required for some PGD operations, such as distributed sequence generation. For more information about the consensus mechanism used by EDB Postgres Distributed, see [Architectural - details](../architectures/#architecture-details). + details](architectures/#architecture-details). ## Multiple databases on single instances From 419cb4c6a6305bae40c9f184be8cc0fd9694ca75 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 13 Sep 2023 08:05:13 -0400 Subject: [PATCH 130/255] Generated topics to reflect previous small fix --- .../docs/epas/11/installing/linux_ppc64le/epas_rhel_7.mdx | 2 +- .../docs/epas/11/installing/linux_ppc64le/epas_rhel_8.mdx | 2 +- .../docs/epas/11/installing/linux_ppc64le/epas_rhel_9.mdx | 2 +- .../docs/epas/11/installing/linux_ppc64le/epas_sles_12.mdx | 2 +- .../docs/epas/11/installing/linux_ppc64le/epas_sles_15.mdx | 2 +- .../docs/epas/11/installing/linux_x86_64/epas_centos_7.mdx | 2 +- .../docs/epas/11/installing/linux_x86_64/epas_debian_10.mdx | 2 +- .../docs/epas/11/installing/linux_x86_64/epas_debian_11.mdx | 2 +- .../docs/epas/11/installing/linux_x86_64/epas_other_linux_8.mdx | 2 +- .../docs/epas/11/installing/linux_x86_64/epas_other_linux_9.mdx | 2 +- .../docs/epas/11/installing/linux_x86_64/epas_rhel_7.mdx | 2 +- .../docs/epas/11/installing/linux_x86_64/epas_rhel_8.mdx | 2 +- .../docs/epas/11/installing/linux_x86_64/epas_rhel_9.mdx | 2 +- .../docs/epas/11/installing/linux_x86_64/epas_sles_12.mdx | 2 +- .../docs/epas/11/installing/linux_x86_64/epas_sles_15.mdx | 2 +- .../docs/epas/11/installing/linux_x86_64/epas_ubuntu_18.mdx | 2 +- .../docs/epas/11/installing/linux_x86_64/epas_ubuntu_20.mdx | 2 +- .../docs/epas/11/installing/linux_x86_64/epas_ubuntu_22.mdx | 2 +- .../docs/epas/12/installing/linux_ppc64le/epas_rhel_7.mdx | 2 +- .../docs/epas/12/installing/linux_ppc64le/epas_rhel_8.mdx | 2 +- .../docs/epas/12/installing/linux_ppc64le/epas_rhel_9.mdx | 2 +- .../docs/epas/12/installing/linux_ppc64le/epas_sles_12.mdx | 2 +- .../docs/epas/12/installing/linux_ppc64le/epas_sles_15.mdx | 2 +- .../docs/epas/12/installing/linux_x86_64/epas_centos_7.mdx | 2 +- .../docs/epas/12/installing/linux_x86_64/epas_debian_10.mdx | 2 +- .../docs/epas/12/installing/linux_x86_64/epas_debian_11.mdx | 2 +- .../docs/epas/12/installing/linux_x86_64/epas_other_linux_8.mdx | 2 +- .../docs/epas/12/installing/linux_x86_64/epas_other_linux_9.mdx | 2 +- .../docs/epas/12/installing/linux_x86_64/epas_rhel_7.mdx | 2 +- .../docs/epas/12/installing/linux_x86_64/epas_rhel_8.mdx | 2 +- .../docs/epas/12/installing/linux_x86_64/epas_rhel_9.mdx | 2 +- .../docs/epas/12/installing/linux_x86_64/epas_sles_12.mdx | 2 +- .../docs/epas/12/installing/linux_x86_64/epas_sles_15.mdx | 2 +- .../docs/epas/12/installing/linux_x86_64/epas_ubuntu_18.mdx | 2 +- .../docs/epas/12/installing/linux_x86_64/epas_ubuntu_20.mdx | 2 +- .../docs/epas/12/installing/linux_x86_64/epas_ubuntu_22.mdx | 2 +- .../docs/epas/13/installing/linux_ppc64le/epas_rhel_7.mdx | 2 +- .../docs/epas/13/installing/linux_ppc64le/epas_rhel_8.mdx | 2 +- .../docs/epas/13/installing/linux_ppc64le/epas_rhel_9.mdx | 2 +- .../docs/epas/13/installing/linux_ppc64le/epas_sles_12.mdx | 2 +- .../docs/epas/13/installing/linux_ppc64le/epas_sles_15.mdx | 2 +- .../docs/epas/13/installing/linux_x86_64/epas_centos_7.mdx | 2 +- .../docs/epas/13/installing/linux_x86_64/epas_debian_10.mdx | 2 +- .../docs/epas/13/installing/linux_x86_64/epas_debian_11.mdx | 2 +- .../docs/epas/13/installing/linux_x86_64/epas_other_linux_8.mdx | 2 +- .../docs/epas/13/installing/linux_x86_64/epas_other_linux_9.mdx | 2 +- .../docs/epas/13/installing/linux_x86_64/epas_rhel_7.mdx | 2 +- .../docs/epas/13/installing/linux_x86_64/epas_rhel_8.mdx | 2 +- .../docs/epas/13/installing/linux_x86_64/epas_rhel_9.mdx | 2 +- .../docs/epas/13/installing/linux_x86_64/epas_sles_12.mdx | 2 +- .../docs/epas/13/installing/linux_x86_64/epas_sles_15.mdx | 2 +- .../docs/epas/13/installing/linux_x86_64/epas_ubuntu_18.mdx | 2 +- .../docs/epas/13/installing/linux_x86_64/epas_ubuntu_20.mdx | 2 +- .../docs/epas/13/installing/linux_x86_64/epas_ubuntu_22.mdx | 2 +- .../docs/epas/14/installing/linux_ppc64le/epas_rhel_7.mdx | 2 +- .../docs/epas/14/installing/linux_ppc64le/epas_rhel_8.mdx | 2 +- .../docs/epas/14/installing/linux_ppc64le/epas_rhel_9.mdx | 2 +- .../docs/epas/14/installing/linux_ppc64le/epas_sles_12.mdx | 2 +- .../docs/epas/14/installing/linux_ppc64le/epas_sles_15.mdx | 2 +- .../docs/epas/14/installing/linux_x86_64/epas_centos_7.mdx | 2 +- .../docs/epas/14/installing/linux_x86_64/epas_debian_10.mdx | 2 +- .../docs/epas/14/installing/linux_x86_64/epas_debian_11.mdx | 2 +- .../docs/epas/14/installing/linux_x86_64/epas_other_linux_8.mdx | 2 +- .../docs/epas/14/installing/linux_x86_64/epas_other_linux_9.mdx | 2 +- .../docs/epas/14/installing/linux_x86_64/epas_rhel_7.mdx | 2 +- .../docs/epas/14/installing/linux_x86_64/epas_rhel_8.mdx | 2 +- .../docs/epas/14/installing/linux_x86_64/epas_rhel_9.mdx | 2 +- .../docs/epas/14/installing/linux_x86_64/epas_sles_12.mdx | 2 +- .../docs/epas/14/installing/linux_x86_64/epas_sles_15.mdx | 2 +- .../docs/epas/14/installing/linux_x86_64/epas_ubuntu_18.mdx | 2 +- .../docs/epas/14/installing/linux_x86_64/epas_ubuntu_20.mdx | 2 +- .../docs/epas/14/installing/linux_x86_64/epas_ubuntu_22.mdx | 2 +- .../docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx | 2 +- .../docs/epas/15/installing/linux_ppc64le/epas_rhel_8.mdx | 2 +- .../docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx | 2 +- .../docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx | 2 +- .../docs/epas/15/installing/linux_ppc64le/epas_sles_15.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_debian_10.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_debian_11.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_other_linux_8.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_other_linux_9.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_rhel_8.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_sles_15.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_ubuntu_18.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_ubuntu_20.mdx | 2 +- .../docs/epas/15/installing/linux_x86_64/epas_ubuntu_22.mdx | 2 +- 90 files changed, 90 insertions(+), 90 deletions(-) diff --git a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_7.mdx index 0f1650d3b84..f3c81e67da6 100644 --- a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_7.mdx +++ b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_7.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_8.mdx b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_8.mdx index d0c738954f8..320f66e6edb 100644 --- a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_8.mdx +++ b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_8.mdx @@ -99,7 +99,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_9.mdx index 981eb3f1e3a..68c95e1937c 100644 --- a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_9.mdx @@ -99,7 +99,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_12.mdx index 19f261fcbb0..d4d7c74948b 100644 --- a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_12.mdx +++ b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_12.mdx @@ -93,7 +93,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_15.mdx b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_15.mdx index cb969d9023e..c59e67c4ef5 100644 --- a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_15.mdx +++ b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_15.mdx @@ -94,7 +94,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_centos_7.mdx index 6b24871c75d..43cbf0c8840 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_centos_7.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_centos_7.mdx @@ -89,7 +89,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_10.mdx index 80d3286415c..f9bd9499c45 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_10.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_10.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_11.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_11.mdx index 5397bd59bf2..3efe80cf1a1 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_11.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_11.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_8.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_8.mdx index 8c436b8a209..cfdadc746b7 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_8.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_8.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_9.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_9.mdx index 8c7ffe76417..3d422acdf4c 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_9.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_other_linux_9.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_7.mdx index 6c8e4fe7880..2199a0f64c4 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_7.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_7.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_8.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_8.mdx index a6cc561cee4..bd31438b9cd 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_8.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_8.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_9.mdx index 2495e08caaa..bdd51e49520 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_9.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_12.mdx index 3772f7bef44..0dbde6d4d08 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_12.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_12.mdx @@ -93,7 +93,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_15.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_15.mdx index a9415b05bfe..128f3523f54 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_15.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_15.mdx @@ -94,7 +94,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_18.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_18.mdx index b7c487927f9..b6e0baa55ed 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_18.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_18.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_20.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_20.mdx index 28c6b56ac1c..0cabc6bc7e1 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_20.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_20.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_22.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_22.mdx index 5b44b3d75e4..421064a54ac 100644 --- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_22.mdx +++ b/product_docs/docs/epas/11/installing/linux_x86_64/epas_ubuntu_22.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_7.mdx index e03579fe03d..98861c13f90 100644 --- a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_7.mdx +++ b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_7.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_8.mdx b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_8.mdx index 3b8cac0238a..11acd2c4d6a 100644 --- a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_8.mdx +++ b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_8.mdx @@ -99,7 +99,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_9.mdx index 3e444c6600e..4f4af735e23 100644 --- a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_9.mdx @@ -99,7 +99,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_12.mdx index 49bb168a9a7..a9341e767c0 100644 --- a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_12.mdx +++ b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_12.mdx @@ -93,7 +93,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_15.mdx b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_15.mdx index eed6caab5e2..f6ceff1c8cd 100644 --- a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_15.mdx +++ b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_15.mdx @@ -94,7 +94,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_centos_7.mdx index f966a66e147..4300e3286a6 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_centos_7.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_centos_7.mdx @@ -89,7 +89,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_10.mdx index 1f3aa2525f7..5b046520179 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_10.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_10.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_11.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_11.mdx index c5d7441e94a..a096df277f4 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_11.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_11.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_8.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_8.mdx index 1ff3a9b112d..53e898b5da0 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_8.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_8.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_9.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_9.mdx index 96d22b8a253..33324e71dc9 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_9.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_other_linux_9.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_7.mdx index e25bb6a8524..57d3a8e03dc 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_7.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_7.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_8.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_8.mdx index ba33cd2c9ff..c30de6b9678 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_8.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_8.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_9.mdx index aef7056768e..4a84ae0f3ad 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_9.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_12.mdx index 077cb05acac..b11ea74e6ae 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_12.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_12.mdx @@ -93,7 +93,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_15.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_15.mdx index 280a85650f7..ed9b5124827 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_15.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_15.mdx @@ -94,7 +94,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_18.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_18.mdx index 77881730bbc..0193b0325cc 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_18.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_18.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_20.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_20.mdx index 0b27809f1fb..19495c144be 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_20.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_20.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_22.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_22.mdx index 36d1122c85a..da3bd5aead2 100644 --- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_22.mdx +++ b/product_docs/docs/epas/12/installing/linux_x86_64/epas_ubuntu_22.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_7.mdx index 64bdd9b77c1..e8fb1e11703 100644 --- a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_7.mdx +++ b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_7.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_8.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_8.mdx index f25af0f0846..37d633baf35 100644 --- a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_8.mdx +++ b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_8.mdx @@ -99,7 +99,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_9.mdx index 119b3d88ef0..9ed058b9979 100644 --- a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_9.mdx @@ -99,7 +99,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_12.mdx index 96ca0c457d7..b6c6321ffa7 100644 --- a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_12.mdx +++ b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_12.mdx @@ -93,7 +93,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_15.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_15.mdx index e7acb2a4258..a8fac4a76b1 100644 --- a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_15.mdx +++ b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_15.mdx @@ -94,7 +94,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_centos_7.mdx index db6d66a71e5..b4e35210a92 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_centos_7.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_centos_7.mdx @@ -89,7 +89,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_10.mdx index fa47bb6ff8f..1e51f600936 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_10.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_10.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_11.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_11.mdx index e415c5f52b6..c42ed5d99f0 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_11.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_11.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_8.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_8.mdx index 02794a41518..e5fc70a5cf1 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_8.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_8.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_9.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_9.mdx index 7108a5586f4..d81cfdab1a4 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_9.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_other_linux_9.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_7.mdx index 4ab029088f3..926daee985b 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_7.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_7.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_8.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_8.mdx index 0189a243189..d2941c93f24 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_8.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_8.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_9.mdx index 59b97ab087b..493009b5d9b 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_9.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_12.mdx index 74fcad35575..f1f12dabccb 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_12.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_12.mdx @@ -93,7 +93,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_15.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_15.mdx index a29eee83c7e..0efb306011c 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_15.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_15.mdx @@ -94,7 +94,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_18.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_18.mdx index 6f9e612e9e6..e807b553b1a 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_18.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_18.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_20.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_20.mdx index b0f4bfca8cb..1531420a07e 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_20.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_20.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_22.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_22.mdx index 968895d87ce..2ff62b84b1f 100644 --- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_22.mdx +++ b/product_docs/docs/epas/13/installing/linux_x86_64/epas_ubuntu_22.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_7.mdx index 13d4ef480e4..81aa547de5f 100644 --- a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_7.mdx +++ b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_7.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_8.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_8.mdx index d025a5dab43..0a51e198781 100644 --- a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_8.mdx +++ b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_8.mdx @@ -99,7 +99,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_9.mdx index 781bb2e4ae4..9a5cdb485fe 100644 --- a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_9.mdx @@ -99,7 +99,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_12.mdx index 8daed5b3501..578ab5b7013 100644 --- a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_12.mdx +++ b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_12.mdx @@ -93,7 +93,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_15.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_15.mdx index cd288bd90d6..12792bf0b96 100644 --- a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_15.mdx +++ b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_15.mdx @@ -94,7 +94,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_centos_7.mdx index f33bb5f6b65..49104e367f6 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_centos_7.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_centos_7.mdx @@ -89,7 +89,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_10.mdx index 45b9850f7e9..0b4fb2b1905 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_10.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_10.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_11.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_11.mdx index eedcb491035..9b53aca0e81 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_11.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_11.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_8.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_8.mdx index 1f54101862b..d4e98a355c1 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_8.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_8.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_9.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_9.mdx index a3d044fc3f9..899cdf9bb40 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_9.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_other_linux_9.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_7.mdx index 2fce9ff259c..f5bb61703ba 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_7.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_7.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_8.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_8.mdx index 34bcbbcd079..eb30af9dc9e 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_8.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_8.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_9.mdx index 7d649c63989..f13b24ca42c 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_9.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_12.mdx index c26981bc742..f4791a102d5 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_12.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_12.mdx @@ -93,7 +93,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_15.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_15.mdx index fa8dcd09882..d546c497946 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_15.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_15.mdx @@ -94,7 +94,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_18.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_18.mdx index 8cb23e779b5..e6febda0c0e 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_18.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_18.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_20.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_20.mdx index c3b5610a881..8c389eadfde 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_20.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_20.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_22.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_22.mdx index fc8a080eb83..e35fb895771 100644 --- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_22.mdx +++ b/product_docs/docs/epas/14/installing/linux_x86_64/epas_ubuntu_22.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx index 19194f58557..469cbcc1fa3 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_8.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_8.mdx index 7f0cc553b0c..651693bfe04 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_8.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_8.mdx @@ -99,7 +99,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx index 91ac028db29..9ef92e3577b 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_9.mdx @@ -99,7 +99,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx index 570eb32a30d..5b90f2c6645 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx @@ -93,7 +93,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_15.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_15.mdx index 6a3607220ea..50d5ac741b3 100644 --- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_15.mdx +++ b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_15.mdx @@ -94,7 +94,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx index 210a69b0e92..835c8177c10 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx @@ -89,7 +89,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_10.mdx index ee48367ff64..5d106336f76 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_10.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_10.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_11.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_11.mdx index ccdf025428c..c949411deee 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_11.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_11.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_8.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_8.mdx index 40ec76dc564..428445be69b 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_8.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_8.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_9.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_9.mdx index 69d9c1914e0..3a780aa726c 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_9.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_other_linux_9.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx index c50447914cb..c79d91cde15 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx @@ -95,7 +95,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_8.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_8.mdx index 333b703978b..eb612d7c1e9 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_8.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_8.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx index 362a2a2e802..39685242f11 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_9.mdx @@ -97,7 +97,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx index a39e1f8adbc..aa8e0f452cf 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx @@ -93,7 +93,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_15.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_15.mdx index 968fb55cc51..744ea5bac3f 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_15.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_15.mdx @@ -94,7 +94,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_18.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_18.mdx index f5b90bb7a53..bfc54931ef6 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_18.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_18.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_20.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_20.mdx index aa941c6da61..69e824824b8 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_20.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_20.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_22.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_22.mdx index fcb4ee9e023..10d25a61090 100644 --- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_22.mdx +++ b/product_docs/docs/epas/15/installing/linux_x86_64/epas_ubuntu_22.mdx @@ -74,7 +74,7 @@ ALTER ROLE enterprisedb IDENTIFIED BY password; Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. -First, use psql create a database named `hr` to hold human resource information. +First, use psql to create a database named `hr` to hold human resource information. ```sql # running in psql From 59c27efe2c1238f75f9110bc093d2d7ce4209ce9 Mon Sep 17 00:00:00 2001 From: Vishal Sawale Date: Thu, 14 Sep 2023 17:37:20 +0530 Subject: [PATCH 131/255] docs: Update superset doc for user privileges --- .../release/using_cluster/06_analyze_with_superset.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/biganimal/release/using_cluster/06_analyze_with_superset.mdx b/product_docs/docs/biganimal/release/using_cluster/06_analyze_with_superset.mdx index 9867bd36ca1..a1d6a40403f 100644 --- a/product_docs/docs/biganimal/release/using_cluster/06_analyze_with_superset.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/06_analyze_with_superset.mdx @@ -30,11 +30,11 @@ To connect to a BigAnimal cluster: 2. Select **Analyze > Connections**. 3. Select **+ Database**. 4. In the Add Database dialog box, enter a value for **Database Name**. -5. Enter the connection string for your cluster in the **SQLALCHEMY URI** field, using the following format: +5. To connect to the database, you need database user with a password.Enter the connection string for your cluster in the **SQLALCHEMY URI** field, using the following format: `postgresql://{}:{}@{}:{}/{}?sslmode=verify-full` !!!note - Your password is always encrypted before storage and never leaves your cloud environment. It's used only by the Superset software running in your BigAnimal infrastructure. As a defense-in-depth mechanism, we recommend using a Postgres user dedicated to Superset with a minimal set of privileges to just the database you're connecting. Never use your edb_admin user with Superset. + Your password is always encrypted before storage and never leaves your cloud environment. It's used only by the Superset software running in your BigAnimal infrastructure. As a defense-in-depth mechanism, we recommend using a Postgres user dedicated to Superset with a minimal set of privileges to just the database you're connecting. Never use your edb_admin, superuser or equivalent user with Superset. !!! 6. Check the connection by selecting **Test Connection**. Select **Add** if the connection was successful. From d9516273818ee5ada22d4c07cc900b5a0d20570d Mon Sep 17 00:00:00 2001 From: Bobby Bissett <70302203+EFM-Bobby@users.noreply.github.com> Date: Thu, 14 Sep 2023 10:11:16 -0400 Subject: [PATCH 132/255] removed text that was not needed The db.bin property is just one of many needed properties, so calling it out here in a note doesn't make sense. My guess is that we added that property some time back and an upgrade required setting it, but by now any installation that a user is upgrading from will already have it set. The unit file comment I removed doesn't make sense here, and I don't know where it might have come from. When upgrading, the service name doesn't change, and there would be a new unit file anyway. This might be related to the multiple efm agents on a single node section, but doesn't make sense here that I can see. --- product_docs/docs/efm/4/upgrading.mdx | 6 ------ 1 file changed, 6 deletions(-) diff --git a/product_docs/docs/efm/4/upgrading.mdx b/product_docs/docs/efm/4/upgrading.mdx index d8064ddd1db..939d8175781 100644 --- a/product_docs/docs/efm/4/upgrading.mdx +++ b/product_docs/docs/efm/4/upgrading.mdx @@ -26,9 +26,6 @@ Failover Manager provides a utility to assist you when upgrading a cluster manag 3. Modify the `.properties` and `.nodes` files for Failover Manager 4.7, specifying any new preferences. Use your choice of editor to modify any additional properties in the properties file (located in the `/etc/edb/efm-4.7` directory) before starting the service for that node. For detailed information about property settings, see [The cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties). -!!! Note - `db.bin` is a required property. When modifying the properties file, ensure that the `db.bin` property specifies the location of the Postgres `bin` directory. - 4. If you're using Eager Failover, you must disable it before stopping the Failover Manager cluster. For more information, see [Disabling Eager Failover](04_configuring_efm/06_configuring_for_eager_failover/#disabling-eager-failover). 5. Use a version-specific command to stop the old Failover Manager cluster. For example, you can use the following command to stop a version 4.4 cluster: @@ -54,9 +51,6 @@ Upgrade of files is finished. The owner and group for properties and nodes files If you're [using a Failover Manager configuration without sudo](04_configuring_efm/04_extending_efm_permissions/#running_efm_without_sudo), include the `-source` flag and specify the name of the directory in which the configuration files reside when invoking `upgrade-conf`. If the directory isn't the configuration default directory, the upgraded files are created in the directory from which the `upgrade-conf` command was invoked. -!!! Note - If you're using a unit file, manually update the file to reflect the new Failover Manager service name when you perform an upgrade. - ## Uninstalling Failover Manager !!! Note From 0fb8d58b097d03382c1ea8cdf59a1dd2861db8d4 Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Wed, 23 Aug 2023 04:08:43 +0000 Subject: [PATCH 133/255] Rewrite references to internal repo for P4K to public docs --- .../processors/cnp/replace-github-urls.mjs | 22 +++++++++++++++++++ scripts/source/process-cnp-docs.sh | 4 ++++ scripts/source/process-pgd4k-docs.sh | 1 + 3 files changed, 27 insertions(+) create mode 100644 scripts/fileProcessor/processors/cnp/replace-github-urls.mjs diff --git a/scripts/fileProcessor/processors/cnp/replace-github-urls.mjs b/scripts/fileProcessor/processors/cnp/replace-github-urls.mjs new file mode 100644 index 00000000000..a3d366ae5fc --- /dev/null +++ b/scripts/fileProcessor/processors/cnp/replace-github-urls.mjs @@ -0,0 +1,22 @@ +// Replace URLs beginning with the following patterns... +// - https://raw.githubusercontent.com/EnterpriseDB/cloud-native-postgres/main/config/manager/default-monitoring.yaml +// - https://github.com/EnterpriseDB/cloud-native-postgres/tree/main/docs/ +// - https://raw.githubusercontent.com/EnterpriseDB/cloud-native-postgres/main/docs/src/ +// ...with equivalent URLs referencing postgres for kubernetes in the public EDB Docs repo + +const replacements = [ + {pattern: /https:\/\/raw\.githubusercontent\.com\/EnterpriseDB\/cloud-native-postgres\/main\/config\/manager\/default-monitoring\.yaml/g, replacement: "default-monitoring.yaml"}, + {pattern: /https:\/\/github\.com\/EnterpriseDB\/cloud-native-postgres\/tree\/main\/docs\/src\//g, replacement: "https://github.com/EnterpriseDB/docs/tree/main/product_docs/docs/postgres_for_kubernetes/1/"}, + {pattern: /https:\/\/github\.com\/EnterpriseDB\/cloud-native-postgres\/blob\/main\/docs\/src\//g, replacement: "https://github.com/EnterpriseDB/docs/blob/main/product_docs/docs/postgres_for_kubernetes/1/"}, + {pattern: /https:\/\/raw\.githubusercontent\.com\/EnterpriseDB\/cloud-native-postgres\/main\/docs\/src\//g, replacement: "https://raw.githubusercontent.com/EnterpriseDB/docs/main/product_docs/docs/postgres_for_kubernetes/1/"}, +]; + +export const process = (filename, content) => { + for (const r of replacements) + content = content.replace(r.pattern, r.replacement); + + return { + newFilename: filename, + newContent: content, + }; +}; diff --git a/scripts/source/process-cnp-docs.sh b/scripts/source/process-cnp-docs.sh index d70a4abeee1..b5df0948b2e 100755 --- a/scripts/source/process-cnp-docs.sh +++ b/scripts/source/process-cnp-docs.sh @@ -20,12 +20,16 @@ node $DESTINATION_CHECKOUT/scripts/source/files-to-ignore.mjs \ cd $SOURCE_CHECKOUT/docs +# grab key bit of source for use in docs +cp $SOURCE_CHECKOUT/config/manager/default-monitoring.yaml $SOURCE_CHECKOUT/docs/src/ + node $DESTINATION_CHECKOUT/scripts/fileProcessor/main.mjs \ -f "src/**/quickstart.md" \ -p cnp/add-quickstart-content node $DESTINATION_CHECKOUT/scripts/fileProcessor/main.mjs \ -f "src/**/*.md" \ + -p "cnp/replace-github-urls" \ -p "cnp/update-yaml-links" \ -p "cnp/add-frontmatters" \ -p "cnp/rename-to-mdx" diff --git a/scripts/source/process-pgd4k-docs.sh b/scripts/source/process-pgd4k-docs.sh index 11ad5d9aa28..052c5db1d1a 100755 --- a/scripts/source/process-pgd4k-docs.sh +++ b/scripts/source/process-pgd4k-docs.sh @@ -22,6 +22,7 @@ cd $SOURCE_CHECKOUT/docs node $DESTINATION_CHECKOUT/scripts/fileProcessor/main.mjs \ -f "src/**/*.md" \ + -p "cnp/replace-github-urls" \ -p "cnp/update-yaml-links" \ -p "cnp/add-frontmatters" \ -p "cnp/rename-to-mdx" From 6460d6647604ca238d26c13d9302bd215f8f1b54 Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Thu, 14 Sep 2023 20:03:03 +0000 Subject: [PATCH 134/255] Import corrections --- .../1/benchmarking.mdx | 2 +- .../postgres_for_kubernetes/1/bootstrap.mdx | 2 +- .../1/default-monitoring.yaml | 383 ++++++++++++++++++ .../1/installation_upgrade.mdx | 2 +- .../1/kubectl-plugin.mdx | 2 +- .../postgres_for_kubernetes/1/monitoring.mdx | 15 +- .../postgres_for_kubernetes/1/openshift.mdx | 2 +- .../1/operator_conf.mdx | 22 +- .../postgres_for_kubernetes/1/quickstart.mdx | 6 +- ...erator-podmonitor.yaml => podmonitor.yaml} | 0 ...rometheusrule.yaml => prometheusrule.yaml} | 0 .../postgres_for_kubernetes/1/security.mdx | 2 +- 12 files changed, 410 insertions(+), 28 deletions(-) create mode 100644 product_docs/docs/postgres_for_kubernetes/1/default-monitoring.yaml rename product_docs/docs/postgres_for_kubernetes/1/samples/monitoring/{cnp-operator-podmonitor.yaml => podmonitor.yaml} (100%) rename product_docs/docs/postgres_for_kubernetes/1/samples/monitoring/{cnp-prometheusrule.yaml => prometheusrule.yaml} (100%) diff --git a/product_docs/docs/postgres_for_kubernetes/1/benchmarking.mdx b/product_docs/docs/postgres_for_kubernetes/1/benchmarking.mdx index cb90ac72b44..0884e13a29e 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/benchmarking.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/benchmarking.mdx @@ -55,7 +55,7 @@ kubectl cnp pgbench \ You can see the progress of the job with: -```shell  +```shell kubectl logs jobs/pgbench-run ``` diff --git a/product_docs/docs/postgres_for_kubernetes/1/bootstrap.mdx b/product_docs/docs/postgres_for_kubernetes/1/bootstrap.mdx index 427408ac4fa..62e64f500ae 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/bootstrap.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/bootstrap.mdx @@ -97,7 +97,7 @@ When only the streaming connection is defined, the source can be used for the source can be used for the `recovery` method. When both are defined, any of the two bootstrap methods can be chosen. -Furthermore, in case of `pg_basebackup` or full `recovery`point in time), the +Furthermore, in case of `pg_basebackup` or full `recovery` point in time, the cluster is eligible for replica cluster mode. This means that the cluster is continuously fed from the source, either via streaming, via WAL shipping through the PostgreSQL's `restore_command`, or any of the two. diff --git a/product_docs/docs/postgres_for_kubernetes/1/default-monitoring.yaml b/product_docs/docs/postgres_for_kubernetes/1/default-monitoring.yaml new file mode 100644 index 00000000000..08dd66346a8 --- /dev/null +++ b/product_docs/docs/postgres_for_kubernetes/1/default-monitoring.yaml @@ -0,0 +1,383 @@ +--- +apiVersion: v1 +kind: ConfigMap +metadata: + name: default-monitoring + labels: + k8s.enterprisedb.io/reload: "" +data: + queries: | + backends: + query: | + SELECT sa.datname + , sa.usename + , sa.application_name + , states.state + , COALESCE(sa.count, 0) AS total + , COALESCE(sa.max_tx_secs, 0) AS max_tx_duration_seconds + FROM ( VALUES ('active') + , ('idle') + , ('idle in transaction') + , ('idle in transaction (aborted)') + , ('fastpath function call') + , ('disabled') + ) AS states(state) + LEFT JOIN ( + SELECT datname + , state + , usename + , COALESCE(application_name, '') AS application_name + , COUNT(*) + , COALESCE(EXTRACT (EPOCH FROM (max(now() - xact_start))), 0) AS max_tx_secs + FROM pg_catalog.pg_stat_activity + GROUP BY datname, state, usename, application_name + ) sa ON states.state = sa.state + WHERE sa.usename IS NOT NULL + metrics: + - datname: + usage: "LABEL" + description: "Name of the database" + - usename: + usage: "LABEL" + description: "Name of the user" + - application_name: + usage: "LABEL" + description: "Name of the application" + - state: + usage: "LABEL" + description: "State of the backend" + - total: + usage: "GAUGE" + description: "Number of backends" + - max_tx_duration_seconds: + usage: "GAUGE" + description: "Maximum duration of a transaction in seconds" + + backends_waiting: + query: | + SELECT count(*) AS total + FROM pg_catalog.pg_locks blocked_locks + JOIN pg_catalog.pg_locks blocking_locks + ON blocking_locks.locktype = blocked_locks.locktype + AND blocking_locks.database IS NOT DISTINCT FROM blocked_locks.database + AND blocking_locks.relation IS NOT DISTINCT FROM blocked_locks.relation + AND blocking_locks.page IS NOT DISTINCT FROM blocked_locks.page + AND blocking_locks.tuple IS NOT DISTINCT FROM blocked_locks.tuple + AND blocking_locks.virtualxid IS NOT DISTINCT FROM blocked_locks.virtualxid + AND blocking_locks.transactionid IS NOT DISTINCT FROM blocked_locks.transactionid + AND blocking_locks.classid IS NOT DISTINCT FROM blocked_locks.classid + AND blocking_locks.objid IS NOT DISTINCT FROM blocked_locks.objid + AND blocking_locks.objsubid IS NOT DISTINCT FROM blocked_locks.objsubid + AND blocking_locks.pid != blocked_locks.pid + JOIN pg_catalog.pg_stat_activity blocking_activity ON blocking_activity.pid = blocking_locks.pid + WHERE NOT blocked_locks.granted + metrics: + - total: + usage: "GAUGE" + description: "Total number of backends that are currently waiting on other queries" + + pg_database: + query: | + SELECT datname + , pg_catalog.pg_database_size(datname) AS size_bytes + , pg_catalog.age(datfrozenxid) AS xid_age + , pg_catalog.mxid_age(datminmxid) AS mxid_age + FROM pg_catalog.pg_database + metrics: + - datname: + usage: "LABEL" + description: "Name of the database" + - size_bytes: + usage: "GAUGE" + description: "Disk space used by the database" + - xid_age: + usage: "GAUGE" + description: "Number of transactions from the frozen XID to the current one" + - mxid_age: + usage: "GAUGE" + description: "Number of multiple transactions (Multixact) from the frozen XID to the current one" + + pg_postmaster: + query: | + SELECT EXTRACT(EPOCH FROM pg_postmaster_start_time) AS start_time + FROM pg_catalog.pg_postmaster_start_time() + metrics: + - start_time: + usage: "GAUGE" + description: "Time at which postgres started (based on epoch)" + + pg_replication: + query: "SELECT CASE WHEN ( + NOT pg_catalog.pg_is_in_recovery() + OR pg_catalog.pg_last_wal_receive_lsn() = pg_catalog.pg_last_wal_replay_lsn()) + THEN 0 + ELSE GREATEST (0, + EXTRACT(EPOCH FROM (now() - pg_catalog.pg_last_xact_replay_timestamp()))) + END AS lag, + pg_catalog.pg_is_in_recovery() AS in_recovery, + EXISTS (TABLE pg_stat_wal_receiver) AS is_wal_receiver_up, + (SELECT count(*) FROM pg_catalog.pg_stat_replication) AS streaming_replicas" + metrics: + - lag: + usage: "GAUGE" + description: "Replication lag behind primary in seconds" + - in_recovery: + usage: "GAUGE" + description: "Whether the instance is in recovery" + - is_wal_receiver_up: + usage: "GAUGE" + description: "Whether the instance wal_receiver is up" + - streaming_replicas: + usage: "GAUGE" + description: "Number of streaming replicas connected to the instance" + + pg_replication_slots: + primary: true + query: | + SELECT slot_name, + slot_type, + database, + active, + pg_catalog.pg_wal_lsn_diff(pg_catalog.pg_current_wal_lsn(), restart_lsn) + FROM pg_catalog.pg_replication_slots + WHERE NOT temporary + metrics: + - slot_name: + usage: "LABEL" + description: "Name of the replication slot" + - slot_type: + usage: "LABEL" + description: "Type of the replication slot" + - database: + usage: "LABEL" + description: "Name of the database" + - active: + usage: "GAUGE" + description: "Flag indicating whether the slot is active" + - pg_wal_lsn_diff: + usage: "GAUGE" + description: "Replication lag in bytes" + + pg_stat_archiver: + query: | + SELECT archived_count + , failed_count + , COALESCE(EXTRACT(EPOCH FROM (now() - last_archived_time)), -1) AS seconds_since_last_archival + , COALESCE(EXTRACT(EPOCH FROM (now() - last_failed_time)), -1) AS seconds_since_last_failure + , COALESCE(EXTRACT(EPOCH FROM last_archived_time), -1) AS last_archived_time + , COALESCE(EXTRACT(EPOCH FROM last_failed_time), -1) AS last_failed_time + , COALESCE(CAST(CAST('x'||pg_catalog.right(pg_catalog.split_part(last_archived_wal, '.', 1), 16) AS pg_catalog.bit(64)) AS pg_catalog.int8), -1) AS last_archived_wal_start_lsn + , COALESCE(CAST(CAST('x'||pg_catalog.right(pg_catalog.split_part(last_failed_wal, '.', 1), 16) AS pg_catalog.bit(64)) AS pg_catalog.int8), -1) AS last_failed_wal_start_lsn + , EXTRACT(EPOCH FROM stats_reset) AS stats_reset_time + FROM pg_catalog.pg_stat_archiver + metrics: + - archived_count: + usage: "COUNTER" + description: "Number of WAL files that have been successfully archived" + - failed_count: + usage: "COUNTER" + description: "Number of failed attempts for archiving WAL files" + - seconds_since_last_archival: + usage: "GAUGE" + description: "Seconds since the last successful archival operation" + - seconds_since_last_failure: + usage: "GAUGE" + description: "Seconds since the last failed archival operation" + - last_archived_time: + usage: "GAUGE" + description: "Epoch of the last time WAL archiving succeeded" + - last_failed_time: + usage: "GAUGE" + description: "Epoch of the last time WAL archiving failed" + - last_archived_wal_start_lsn: + usage: "GAUGE" + description: "Archived WAL start LSN" + - last_failed_wal_start_lsn: + usage: "GAUGE" + description: "Last failed WAL LSN" + - stats_reset_time: + usage: "GAUGE" + description: "Time at which these statistics were last reset" + + pg_stat_bgwriter: + query: | + SELECT checkpoints_timed + , checkpoints_req + , checkpoint_write_time + , checkpoint_sync_time + , buffers_checkpoint + , buffers_clean + , maxwritten_clean + , buffers_backend + , buffers_backend_fsync + , buffers_alloc + FROM pg_catalog.pg_stat_bgwriter + metrics: + - checkpoints_timed: + usage: "COUNTER" + description: "Number of scheduled checkpoints that have been performed" + - checkpoints_req: + usage: "COUNTER" + description: "Number of requested checkpoints that have been performed" + - checkpoint_write_time: + usage: "COUNTER" + description: "Total amount of time that has been spent in the portion of checkpoint processing where files are written to disk, in milliseconds" + - checkpoint_sync_time: + usage: "COUNTER" + description: "Total amount of time that has been spent in the portion of checkpoint processing where files are synchronized to disk, in milliseconds" + - buffers_checkpoint: + usage: "COUNTER" + description: "Number of buffers written during checkpoints" + - buffers_clean: + usage: "COUNTER" + description: "Number of buffers written by the background writer" + - maxwritten_clean: + usage: "COUNTER" + description: "Number of times the background writer stopped a cleaning scan because it had written too many buffers" + - buffers_backend: + usage: "COUNTER" + description: "Number of buffers written directly by a backend" + - buffers_backend_fsync: + usage: "COUNTER" + description: "Number of times a backend had to execute its own fsync call (normally the background writer handles those even when the backend does its own write)" + - buffers_alloc: + usage: "COUNTER" + description: "Number of buffers allocated" + + pg_stat_database: + query: | + SELECT datname + , xact_commit + , xact_rollback + , blks_read + , blks_hit + , tup_returned + , tup_fetched + , tup_inserted + , tup_updated + , tup_deleted + , conflicts + , temp_files + , temp_bytes + , deadlocks + , blk_read_time + , blk_write_time + FROM pg_catalog.pg_stat_database + metrics: + - datname: + usage: "LABEL" + description: "Name of this database" + - xact_commit: + usage: "COUNTER" + description: "Number of transactions in this database that have been committed" + - xact_rollback: + usage: "COUNTER" + description: "Number of transactions in this database that have been rolled back" + - blks_read: + usage: "COUNTER" + description: "Number of disk blocks read in this database" + - blks_hit: + usage: "COUNTER" + description: "Number of times disk blocks were found already in the buffer cache, so that a read was not necessary (this only includes hits in the PostgreSQL buffer cache, not the operating system's file system cache)" + - tup_returned: + usage: "COUNTER" + description: "Number of rows returned by queries in this database" + - tup_fetched: + usage: "COUNTER" + description: "Number of rows fetched by queries in this database" + - tup_inserted: + usage: "COUNTER" + description: "Number of rows inserted by queries in this database" + - tup_updated: + usage: "COUNTER" + description: "Number of rows updated by queries in this database" + - tup_deleted: + usage: "COUNTER" + description: "Number of rows deleted by queries in this database" + - conflicts: + usage: "COUNTER" + description: "Number of queries canceled due to conflicts with recovery in this database" + - temp_files: + usage: "COUNTER" + description: "Number of temporary files created by queries in this database" + - temp_bytes: + usage: "COUNTER" + description: "Total amount of data written to temporary files by queries in this database" + - deadlocks: + usage: "COUNTER" + description: "Number of deadlocks detected in this database" + - blk_read_time: + usage: "COUNTER" + description: "Time spent reading data file blocks by backends in this database, in milliseconds" + - blk_write_time: + usage: "COUNTER" + description: "Time spent writing data file blocks by backends in this database, in milliseconds" + + pg_stat_replication: + primary: true + query: | + SELECT usename + , COALESCE(application_name, '') AS application_name + , COALESCE(client_addr::text, '') AS client_addr + , EXTRACT(EPOCH FROM backend_start) AS backend_start + , COALESCE(pg_catalog.age(backend_xmin), 0) AS backend_xmin_age + , pg_catalog.pg_wal_lsn_diff(pg_catalog.pg_current_wal_lsn(), sent_lsn) AS sent_diff_bytes + , pg_catalog.pg_wal_lsn_diff(pg_catalog.pg_current_wal_lsn(), write_lsn) AS write_diff_bytes + , pg_catalog.pg_wal_lsn_diff(pg_catalog.pg_current_wal_lsn(), flush_lsn) AS flush_diff_bytes + , COALESCE(pg_catalog.pg_wal_lsn_diff(pg_catalog.pg_current_wal_lsn(), replay_lsn),0) AS replay_diff_bytes + , COALESCE((EXTRACT(EPOCH FROM write_lag)),0)::float AS write_lag_seconds + , COALESCE((EXTRACT(EPOCH FROM flush_lag)),0)::float AS flush_lag_seconds + , COALESCE((EXTRACT(EPOCH FROM replay_lag)),0)::float AS replay_lag_seconds + FROM pg_catalog.pg_stat_replication + metrics: + - usename: + usage: "LABEL" + description: "Name of the replication user" + - application_name: + usage: "LABEL" + description: "Name of the application" + - client_addr: + usage: "LABEL" + description: "Client IP address" + - backend_start: + usage: "COUNTER" + description: "Time when this process was started" + - backend_xmin_age: + usage: "COUNTER" + description: "The age of this standby's xmin horizon" + - sent_diff_bytes: + usage: "GAUGE" + description: "Difference in bytes from the last write-ahead log location sent on this connection" + - write_diff_bytes: + usage: "GAUGE" + description: "Difference in bytes from the last write-ahead log location written to disk by this standby server" + - flush_diff_bytes: + usage: "GAUGE" + description: "Difference in bytes from the last write-ahead log location flushed to disk by this standby server" + - replay_diff_bytes: + usage: "GAUGE" + description: "Difference in bytes from the last write-ahead log location replayed into the database on this standby server" + - write_lag_seconds: + usage: "GAUGE" + description: "Time elapsed between flushing recent WAL locally and receiving notification that this standby server has written it" + - flush_lag_seconds: + usage: "GAUGE" + description: "Time elapsed between flushing recent WAL locally and receiving notification that this standby server has written and flushed it" + - replay_lag_seconds: + usage: "GAUGE" + description: "Time elapsed between flushing recent WAL locally and receiving notification that this standby server has written, flushed and applied it" + + pg_settings: + query: | + SELECT name, + CASE setting WHEN 'on' THEN '1' WHEN 'off' THEN '0' ELSE setting END AS setting + FROM pg_catalog.pg_settings + WHERE vartype IN ('integer', 'real', 'bool') + ORDER BY 1 + metrics: + - name: + usage: "LABEL" + description: "Name of the setting" + - setting: + usage: "GAUGE" + description: "Setting value" diff --git a/product_docs/docs/postgres_for_kubernetes/1/installation_upgrade.mdx b/product_docs/docs/postgres_for_kubernetes/1/installation_upgrade.mdx index 421ac797426..0cfb10c663b 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/installation_upgrade.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/installation_upgrade.mdx @@ -57,7 +57,7 @@ for a more comprehensive example. ports, as explained in the official [docs](https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters#add_firewall_rules) and by this - [issue](https://github.com/EnterpriseDB/cloud-native-postgres/issues/1360). + [issue](https://github.com/cloudnative-pg/cloudnative-pg/issues/1360). You'll need to either change the `targetPort` in the webhook service, to be one of the allowed ones, or open the webhooks' port (`9443`) on the firewall. diff --git a/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx b/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx index db070492918..84a5744a4e3 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx @@ -941,4 +941,4 @@ A specific `VolumeSnapshotClass` can be requested via the `-c` option: ```shell kubectl cnp snapshot cluster-example -c longhorn -``` +``` \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/1/monitoring.mdx b/product_docs/docs/postgres_for_kubernetes/1/monitoring.mdx index fb3688fb605..2221bd3cb0d 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/monitoring.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/monitoring.mdx @@ -35,8 +35,8 @@ All monitoring queries that are performed on PostgreSQL are: - executed with `application_name` set to `cnp_metrics_exporter` - executed as user `postgres` -Please refer to the "Default roles" section in PostgreSQL -[documentation](https://www.postgresql.org/docs/current/default-roles.html) +Please refer to the "Predefined Roles" section in PostgreSQL +[documentation](https://www.postgresql.org/docs/current/predefined-roles.html) for details on the `pg_monitor` role. Queries, by default, are run against the *main database*, as defined by @@ -363,7 +363,7 @@ go_threads 18 ### User defined metrics This feature is currently in *beta* state and the format is inspired by the -[queries.yaml file](https://github.com/prometheus-community/postgres_exporter/blob/master/queries.yaml) +[queries.yaml file (release 0.12)](https://github.com/prometheus-community/postgres_exporter/blob/v0.12.1/queries.yaml) of the PostgreSQL Prometheus Exporter. Custom metrics can be defined by users by referring to the created `Configmap`/`Secret` in a `Cluster` definition @@ -442,7 +442,7 @@ data: ``` A list of basic monitoring queries can be found in the -[`default-monitoring.yaml` file](https://github.com/EnterpriseDB/cloud-native-postgres/blob/main/config/manager/default-monitoring.yaml) +[`default-monitoring.yaml` file](default-monitoring.yaml) that is already installed in your EDB Postgres for Kubernetes deployment (see ["Default set of metrics"](#default-set-of-metrics)). #### Example of a user defined metric running on multiple databases @@ -543,7 +543,7 @@ Here is a short description of all the available fields: - ``: the name of the Prometheus metric - `query`: the SQL query to run on the target database to generate the metrics - - `primary`: whether to run the query only on the primary instance + - `primary`: whether to run the query only on the primary instance - `master`: same as `primary` (for compatibility with the Prometheus PostgreSQL exporter's syntax - deprecated) - `runonserver`: a semantic version range to limit the versions of PostgreSQL the query should run on (e.g. `">=11.0.0"` or `">=12.0.0 <=15.0.0"`) @@ -737,16 +737,17 @@ kubectl delete -f curl.yaml These resources are provided for illustration and experimentation, and do not represent any kind of recommendation for your production system -In the [`doc/src/samples/monitoring/`](https://github.com/EnterpriseDB/cloud-native-postgres/tree/main/docs/src/samples/monitoring) +In the [`doc/src/samples/monitoring/`](https://github.com/EnterpriseDB/docs/tree/main/product_docs/docs/postgres_for_kubernetes/1/samples/monitoring) directory you will find a series of sample files for observability. Please refer to [Part 4 of the quickstart](quickstart.md#part-4-monitor-clusters-with-prometheus-and-grafana) section for context: - `kube-stack-config.yaml`: a configuration file for the kube-stack helm chart installation. It ensures that Prometheus listens for all PodMonitor resources. -- `postgresql-operator-prometheusrule.yaml`: a `PrometheusRule` with alerts for EDB Postgres for Kubernetes. +- `prometheusrule.yaml`: a `PrometheusRule` with alerts for EDB Postgres for Kubernetes. NOTE: this does not include inter-operation with notification services. Please refer to the [Prometheus documentation](https://prometheus.io/docs/alerting/latest/alertmanager/). +- `podmonitor.yaml`: a `PodMonitor` for the EDB Postgres for Kubernetes Operator deployment. - `grafana-configmap.yaml`: a ConfigMap containing the definition of the sample EDB Postgres for Kubernetes Dashboard. Note the labels in the definition, which ensure that the Grafana deployment will find the ConfigMap. diff --git a/product_docs/docs/postgres_for_kubernetes/1/openshift.mdx b/product_docs/docs/postgres_for_kubernetes/1/openshift.mdx index 4dec98b6713..cb417fda042 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/openshift.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/openshift.mdx @@ -984,7 +984,7 @@ enabled, so you can peek the `cnp_` prefix: ![Prometheus queries](./images/openshift/prometheus-queries.png) It is easy to define Alerts based on the default metrics as `PrometheusRules`. -You can find some examples of rules in the [cnp-prometheusrule.yaml](../samples/monitoring/cnp-prometheusrule.yaml) +You can find some examples of rules in the [prometheusrule.yaml](../samples/monitoring/prometheusrule.yaml) file, which you can download. Before applying the rules, again, some OpenShift setup may be necessary. diff --git a/product_docs/docs/postgres_for_kubernetes/1/operator_conf.mdx b/product_docs/docs/postgres_for_kubernetes/1/operator_conf.mdx index 6e71212990d..8097d31b22b 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/operator_conf.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/operator_conf.mdx @@ -134,23 +134,21 @@ Following the above example, if the `Cluster` definition contains a `categories` annotation and any of the `environment`, `workload`, or `app` labels, these will be inherited by all the resources generated by the deployment. -## PPROF HTTP SERVER +## pprof HTTP Server -The operator can expose a PPROF HTTP server with the following endpoints on localhost:6060: +The operator can expose a PPROF HTTP server with the following endpoints on `localhost:6060`: -``` -- `/debug/pprof/`. Responds to a request for "/debug/pprof/" with an HTML page listing the available profiles -- `/debug/pprof/cmdline`. Responds with the running program's command line, with arguments separated by NUL bytes. -- `/debug/pprof/profile`. Responds with the pprof-formatted cpu profile. Profiling lasts for duration specified in seconds GET parameter, or for 30 seconds if not specified. -- `/debug/pprof/symbol`. Looks up the program counters listed in the request, responding with a table mapping program counters to function names. -- `/debug/pprof/trace`. Responds with the execution trace in binary form. Tracing lasts for duration specified in seconds GET parameter, or for 1 second if not specified. -``` +- `/debug/pprof/`. Responds to a request for "/debug/pprof/" with an HTML page listing the available profiles +- `/debug/pprof/cmdline`. Responds with the running program's command line, with arguments separated by NULL bytes. +- `/debug/pprof/profile`. Responds with the pprof-formatted cpu profile. Profiling lasts for duration specified in seconds GET parameter, or for 30 seconds if not specified. +- `/debug/pprof/symbol`. Looks up the program counters listed in the request, responding with a table mapping program counters to function names. +- `/debug/pprof/trace`. Responds with the execution trace in binary form. Tracing lasts for duration specified in seconds GET parameter, or for 1 second if not specified. To enable the operator you need to edit the operator deployment add the flag `--pprof-server=true`. You can do this by executing these commands: -``` +```shell kubectl edit deployment -n postgresql-operator-system postgresql-operator-controller-manager ``` @@ -173,12 +171,12 @@ Save the changes, the deployment now will execute a rollout and the new pod will Once the pod is running you can exec inside the container by doing: -``` +```shell kubectl exec -ti -n postgresql-operator-system -- bash ``` Once inside execute: -``` +```shell curl localhost:6060/debug/pprof/ ``` \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/1/quickstart.mdx b/product_docs/docs/postgres_for_kubernetes/1/quickstart.mdx index 35647edd10c..881fb86b8fa 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/quickstart.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/quickstart.mdx @@ -246,7 +246,7 @@ helm repo add prometheus-community \ https://prometheus-community.github.io/helm-charts helm upgrade --install \ - -f https://raw.githubusercontent.com/EnterpriseDB/cloud-native-postgres/main/docs/src/samples/monitoring/kube-stack-config.yaml \ + -f https://raw.githubusercontent.com/EnterpriseDB/docs/main/product_docs/docs/postgres_for_kubernetes/1/samples/monitoring/kube-stack-config.yaml \ prometheus-community \ prometheus-community/kube-prometheus-stack ``` @@ -330,7 +330,7 @@ You can now define some alerts by creating a `prometheusRule`: ```sh kubectl apply -f \ - https://raw.githubusercontent.com/EnterpriseDB/cloud-native-postgres/main/docs/src/samples/monitoring/postgresql-operator-prometheusrule.yaml + https://raw.githubusercontent.com/EnterpriseDB/docs/main/product_docs/docs/postgres_for_kubernetes/1/samples/monitoring/prometheusrule.yaml ``` You should see the default alerts now: @@ -361,7 +361,7 @@ We can now install our sample Grafana dashboard: ```sh kubectl apply -f \ - https://raw.githubusercontent.com/EnterpriseDB/cloud-native-postgres/main/docs/src/samples/monitoring/grafana-configmap.yaml + https://raw.githubusercontent.com/EnterpriseDB/docs/main/product_docs/docs/postgres_for_kubernetes/1/samples/monitoring/grafana-configmap.yaml ``` Which will be picked up by the Grafana page in a few seconds. You should now diff --git a/product_docs/docs/postgres_for_kubernetes/1/samples/monitoring/cnp-operator-podmonitor.yaml b/product_docs/docs/postgres_for_kubernetes/1/samples/monitoring/podmonitor.yaml similarity index 100% rename from product_docs/docs/postgres_for_kubernetes/1/samples/monitoring/cnp-operator-podmonitor.yaml rename to product_docs/docs/postgres_for_kubernetes/1/samples/monitoring/podmonitor.yaml diff --git a/product_docs/docs/postgres_for_kubernetes/1/samples/monitoring/cnp-prometheusrule.yaml b/product_docs/docs/postgres_for_kubernetes/1/samples/monitoring/prometheusrule.yaml similarity index 100% rename from product_docs/docs/postgres_for_kubernetes/1/samples/monitoring/cnp-prometheusrule.yaml rename to product_docs/docs/postgres_for_kubernetes/1/samples/monitoring/prometheusrule.yaml diff --git a/product_docs/docs/postgres_for_kubernetes/1/security.mdx b/product_docs/docs/postgres_for_kubernetes/1/security.mdx index 642e4740e29..dad9841372d 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/security.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/security.mdx @@ -159,7 +159,7 @@ PostgreSQL `Cluster` resource name. [recommended way to access the API server from within a Pod](https://kubernetes.io/docs/tasks/run-application/access-api-from-pod/). For transparency, the permissions associated with the service account are defined in the -[roles.go](https://github.com/EnterpriseDB/cloud-native-postgres/blob/main/pkg/specs/roles.go) +[roles.go](https://github.com/cloudnative-pg/cloudnative-pg/blob/main/pkg/specs/roles.go) file. For example, to retrieve the permissions of a generic `mypg` cluster in the `myns` namespace, you can type the following command: From 0ec91b1c2819f63e7562e7639f1ba0ea51770a3b Mon Sep 17 00:00:00 2001 From: Josh Heyer <63653723+josh-heyer@users.noreply.github.com> Date: Thu, 14 Sep 2023 16:48:20 -0700 Subject: [PATCH 135/255] :(( --- CODEOWNERS | 1 - 1 file changed, 1 deletion(-) diff --git a/CODEOWNERS b/CODEOWNERS index 907737c5090..53d4ea4fb93 100644 --- a/CODEOWNERS +++ b/CODEOWNERS @@ -2,4 +2,3 @@ product_docs/docs/pgd/ @djw-m product_docs/docs/epas/ @nidhibhammar -product_docs/docs/biganimal/ @drothery-edb From 997fd1a5f25fb70051cbf8583df80cc3ab991ec9 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 18 Sep 2023 13:44:58 +0530 Subject: [PATCH 136/255] EPAS 15 - Profile parameter update as per DF-356 --- .../epas_compat_sql/29_create_profile.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/29_create_profile.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/29_create_profile.mdx index e2ee13b00c4..3bc12041923 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/29_create_profile.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/29_create_profile.mdx @@ -59,7 +59,7 @@ EDB Postgres Advanced Server supports these values for each parameter: - `DEFAULT` — The value of `PASSWORD_LOCK_TIME` specified in the `DEFAULT` profile. - `UNLIMITED` — The account is locked until manually unlocked by a database superuser. -`PASSWORD_LIFE_TIME` specifies the number of days that the current password can be used before the user is prompted to provide a new password. Include the `PASSWORD_GRACE_TIME` clause when using the `PASSWORD_LIFE_TIME` clause to specify the number of days to pass after the password expires before connections by the role are rejected. If you don't specify `PASSWORD_GRACE_TIME`, the password expires on the day specified by the default value of `PASSWORD_GRACE_TIME`, and the user isn't allowed to execute any command until a new password is provided. Supported values are: +`PASSWORD_LIFE_TIME` specifies the number of days that the current password can be used before the user is prompted to provide a new password. Include the `PASSWORD_GRACE_TIME` clause when using the `PASSWORD_LIFE_TIME` clause to specify the number of days to pass after the password expires before the user is forced to change their password. If you don't specify `PASSWORD_GRACE_TIME`, the password expires on the day specified by the default value of `PASSWORD_GRACE_TIME`, and the user isn't allowed to execute any command until a new password is provided. Supported values are: - A `NUMERIC` value greater of `0` or greater. To specify a fractional portion of a day, specify a decimal value. For example, use the value `4.5` to specify 4 days, 12 hours. - `DEFAULT` — The value of `PASSWORD_LIFE_TIME` specified in the `DEFAULT` profile. From faf7ff296dbef6d0eae774572950ff56c87e97e7 Mon Sep 17 00:00:00 2001 From: Vishal Sawale Date: Mon, 18 Sep 2023 14:57:44 +0530 Subject: [PATCH 137/255] fix(UPM-24162): Fix typo, space --- .../release/using_cluster/06_analyze_with_superset.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/using_cluster/06_analyze_with_superset.mdx b/product_docs/docs/biganimal/release/using_cluster/06_analyze_with_superset.mdx index a1d6a40403f..cecf5a2d7c9 100644 --- a/product_docs/docs/biganimal/release/using_cluster/06_analyze_with_superset.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/06_analyze_with_superset.mdx @@ -30,7 +30,7 @@ To connect to a BigAnimal cluster: 2. Select **Analyze > Connections**. 3. Select **+ Database**. 4. In the Add Database dialog box, enter a value for **Database Name**. -5. To connect to the database, you need database user with a password.Enter the connection string for your cluster in the **SQLALCHEMY URI** field, using the following format: +5. To connect to the database, you need database user with a password. Enter the connection string for your cluster in the **SQLALCHEMY URI** field, using the following format: `postgresql://{}:{}@{}:{}/{}?sslmode=verify-full` !!!note From 259582e56599a0b0ca4f93753b771b77d4a6023f Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Mon, 11 Sep 2023 12:38:55 +0100 Subject: [PATCH 138/255] Now with fully automatic index page generation Signed-off-by: Dj Walker-Morgan --- .../security/advisories/cve.mdx.template | 1 + .../security/advisories/cve20074639.mdx | 1 + .../security/advisories/cve201910128.mdx | 1 + .../security/advisories/cve202331043.mdx | 1 + .../security/advisories/cve202341113.mdx | 1 + .../security/advisories/cve202341114.mdx | 1 + .../security/advisories/cve202341115.mdx | 1 + .../security/advisories/cve202341116.mdx | 6 +- .../security/advisories/cve202341117.mdx | 1 + .../security/advisories/cve202341118.mdx | 1 + .../security/advisories/cve202341119.mdx | 1 + .../security/advisories/cve202341120.mdx | 1 + advocacy_docs/security/advisories/index.mdx | 181 +++++++++------ advocacy_docs/security/index.mdx | 106 ++++----- .../security/templates/advisoriesindex.njs | 39 ++++ .../security/templates/securityindex.njs | 45 ++++ .../generators/advisoryindex/advisoryindex.js | 173 ++++++++++++++ .../advisoryindex/package-lock.json | 216 ++++++++++++++++++ .../generators/advisoryindex/package.json | 17 ++ 19 files changed, 662 insertions(+), 132 deletions(-) create mode 100755 advocacy_docs/security/templates/advisoriesindex.njs create mode 100755 advocacy_docs/security/templates/securityindex.njs create mode 100755 tools/automation/generators/advisoryindex/advisoryindex.js create mode 100644 tools/automation/generators/advisoryindex/package-lock.json create mode 100755 tools/automation/generators/advisoryindex/package.json diff --git a/advocacy_docs/security/advisories/cve.mdx.template b/advocacy_docs/security/advisories/cve.mdx.template index bea078ec99c..737e13f1c70 100644 --- a/advocacy_docs/security/advisories/cve.mdx.template +++ b/advocacy_docs/security/advisories/cve.mdx.template @@ -1,6 +1,7 @@ --- title: CVE Title navTitle: CVE ID as CVE-Year-Number +affectedProducts: one liner covering which products affected --- First Published: YYYY/MM/DD (ISO8601) diff --git a/advocacy_docs/security/advisories/cve20074639.mdx b/advocacy_docs/security/advisories/cve20074639.mdx index 87c6c3bb631..591e5d8dc02 100644 --- a/advocacy_docs/security/advisories/cve20074639.mdx +++ b/advocacy_docs/security/advisories/cve20074639.mdx @@ -1,6 +1,7 @@ --- title: CVE-2007-4639 - EDB Advanced Server 8.2 improperly handles debugging function calls navTitle: CVE-2007-4639 +affectedProducts: EDB Advanced Server 8.2 --- First Published: 2007/08/31 diff --git a/advocacy_docs/security/advisories/cve201910128.mdx b/advocacy_docs/security/advisories/cve201910128.mdx index 1625190c580..ac0edcd989b 100644 --- a/advocacy_docs/security/advisories/cve201910128.mdx +++ b/advocacy_docs/security/advisories/cve201910128.mdx @@ -1,6 +1,7 @@ --- title: CVE-2019-10128 - EDB supplied PostgreSQL inherits ACL for installation directory navTitle: CVE-2019-10128 +affectedProducts: PostgreSQL --- First Published: 2021/03/19 diff --git a/advocacy_docs/security/advisories/cve202331043.mdx b/advocacy_docs/security/advisories/cve202331043.mdx index bbdace27441..bf46090ac4b 100644 --- a/advocacy_docs/security/advisories/cve202331043.mdx +++ b/advocacy_docs/security/advisories/cve202331043.mdx @@ -1,6 +1,7 @@ --- title: CVE-2023-31043 - EDB Postgres Advanced Server (EPAS) logs unredacted passwords prior to 14.6.0 navTitle: CVE-2023-31043 +affectedProducts: EDB Postgres Advanced Server 10.23.32 to 14.5.0 --- First Published: 2023/04/23 diff --git a/advocacy_docs/security/advisories/cve202341113.mdx b/advocacy_docs/security/advisories/cve202341113.mdx index b81a774e300..085470c016b 100644 --- a/advocacy_docs/security/advisories/cve202341113.mdx +++ b/advocacy_docs/security/advisories/cve202341113.mdx @@ -1,6 +1,7 @@ --- title: CVE-2023-41113 - EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory() navTitle: CVE-2023-41113 +affectedProducts: All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0 --- First Published: 2023/08/21 diff --git a/advocacy_docs/security/advisories/cve202341114.mdx b/advocacy_docs/security/advisories/cve202341114.mdx index c4dcb6de550..b4203893917 100644 --- a/advocacy_docs/security/advisories/cve202341114.mdx +++ b/advocacy_docs/security/advisories/cve202341114.mdx @@ -1,6 +1,7 @@ --- title: CVE-2023-41114 - EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL navTitle: CVE-2023-41114 +affectedProducts: All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0 --- First Published: 2023/08/21 diff --git a/advocacy_docs/security/advisories/cve202341115.mdx b/advocacy_docs/security/advisories/cve202341115.mdx index 83c847237dd..e49f4cc7a0d 100644 --- a/advocacy_docs/security/advisories/cve202341115.mdx +++ b/advocacy_docs/security/advisories/cve202341115.mdx @@ -1,6 +1,7 @@ --- title: CVE-2023-41115 - EDB Postgres Advanced Server (EPAS) permission bypass for large objects navTitle: CVE-2023-41115 +affectedProducts: All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0 --- First Published: 2023/08/21 diff --git a/advocacy_docs/security/advisories/cve202341116.mdx b/advocacy_docs/security/advisories/cve202341116.mdx index 13a342a4114..db07c04c79d 100644 --- a/advocacy_docs/security/advisories/cve202341116.mdx +++ b/advocacy_docs/security/advisories/cve202341116.mdx @@ -1,6 +1,7 @@ --- title: CVE-2023-41116 - EDB Postgres Advanced Server (EPAS) permission bypass for materialized views navTitle: CVE-2023-41116 +affectedProducts: All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0 --- First Published: 2023/08/21 @@ -9,10 +10,7 @@ Last Updated: 2023/08/30 ## Summary -An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before -11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and -15.x before 15.4.0. It allows an authenticated user to refresh any materialized -view, regardless of that user's permissions. +An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It allows an authenticated user to refresh any materialized view, regardless of that user's permissions. ## Vulnerability details diff --git a/advocacy_docs/security/advisories/cve202341117.mdx b/advocacy_docs/security/advisories/cve202341117.mdx index 8fcbaacd774..288d7d8ca66 100644 --- a/advocacy_docs/security/advisories/cve202341117.mdx +++ b/advocacy_docs/security/advisories/cve202341117.mdx @@ -1,6 +1,7 @@ --- title: CVE-2023-41117 - EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path navTitle: CVE-2023-41117 +affectedProducts: All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0 --- First Published: 2023/08/21 diff --git a/advocacy_docs/security/advisories/cve202341118.mdx b/advocacy_docs/security/advisories/cve202341118.mdx index 5953cc41dde..b9ce6888252 100644 --- a/advocacy_docs/security/advisories/cve202341118.mdx +++ b/advocacy_docs/security/advisories/cve202341118.mdx @@ -1,6 +1,7 @@ --- title: CVE-2023-41118 - EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass navTitle: CVE-2023-41118 +affectedProducts: All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0 --- First Published: 2023/08/21 diff --git a/advocacy_docs/security/advisories/cve202341119.mdx b/advocacy_docs/security/advisories/cve202341119.mdx index ca40495a3ec..6c1052adba8 100644 --- a/advocacy_docs/security/advisories/cve202341119.mdx +++ b/advocacy_docs/security/advisories/cve202341119.mdx @@ -1,6 +1,7 @@ --- title: CVE-2023-41119 - EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser navTitle: CVE-2023-41119 +affectedProducts: All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0 --- First Published: 2023/08/21 diff --git a/advocacy_docs/security/advisories/cve202341120.mdx b/advocacy_docs/security/advisories/cve202341120.mdx index fb9c0411444..a1f82346248 100644 --- a/advocacy_docs/security/advisories/cve202341120.mdx +++ b/advocacy_docs/security/advisories/cve202341120.mdx @@ -1,6 +1,7 @@ --- title: CVE-2023-41120 - EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission navTitle: CVE-2023-41120 +affectedProducts: All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0 --- First Published: 2023/08/21 diff --git a/advocacy_docs/security/advisories/index.mdx b/advocacy_docs/security/advisories/index.mdx index 9501d20e4ff..02ac823fd9e 100644 --- a/advocacy_docs/security/advisories/index.mdx +++ b/advocacy_docs/security/advisories/index.mdx @@ -18,18 +18,25 @@ navigation: - cve20074639 --- -## Updated 2023 + + + + + + + +

Updated 2023

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + -
-

CVE-2023-41120

+

CVE-2023-41120

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission -

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+  Updated: 2023/08/30 +

CVE-2023-41120 - EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  @@ -38,31 +45,37 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1 Read More...
-

CVE-2023-41119

+

CVE-2023-41119

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser -

-
All EnterpriseDB Postgres Advanced Server (EPAS) versions prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+  Updated: 2023/08/30 +

CVE-2023-41119 - EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It contains the function _dbms_aq_move_to_exception_queue that may be used to elevate a user's privileges to superuser. This function accepts the OID of a table, and then accesses that table as the superuser by using SELECT and DML commands.
Read More... -
-
-

CVE-2023-41118

+

CVE-2023-41118

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass -

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 +  Updated: 2023/08/30 +

CVE-2023-41118 - EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+
Summary:  An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It may allow an authenticated user to bypass authorization requirements and access underlying implementation functions. When a superuser has configured file locations using CREATE DIRECTORY, these functions allow users to take a wide range of actions, including read, write, copy, rename, and delete. @@ -70,30 +83,36 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1 Read More...
-

CVE-2023-41117

+

CVE-2023-41117

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+  Updated: 2023/08/30 +

CVE-2023-41117 - EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It contain packages, standalone packages, and functions that run SECURITY DEFINER but are inadequately secured against search_path attacks.
Read More... -
-
-

CVE-2023-41116

+

CVE-2023-41116

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) permission bypass for materialized views -

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+  Updated: 2023/08/30 +

CVE-2023-41116 - EDB Postgres Advanced Server (EPAS) permission bypass for materialized views

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  @@ -102,14 +121,17 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1 Read More...
-

CVE-2023-41115

+

CVE-2023-41115

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) permission bypass for large objects -

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+  Updated: 2023/08/30 +

CVE-2023-41115 - EDB Postgres Advanced Server (EPAS) permission bypass for large objects

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  @@ -119,14 +141,16 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1
-

CVE-2023-41114

+

CVE-2023-41114

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL -

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+  Updated: 2023/08/30 +

CVE-2023-41114 - EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  @@ -135,32 +159,36 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1 Read More...
-

CVE-2023-41113

+

CVE-2023-41113

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory() -

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+  Updated: 2023/08/30 +

CVE-2023-41113 - EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory()

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It allows an authenticated user to to obtain information about whether certain files exist on disk, what errors if any occur when attempting to read them, and some limited information about their contents (regardless of permissions). This can occur when a superuser has configured one or more directories for filesystem access via CREATE DIRECTORY and adopted certain non-default settings for log_line_prefix and log_connections. -
+
Read More... -
-
-

CVE-2023-31043

+

CVE-2023-31043

  Read Advisory -  Updated: 2023/05/02 -

EDB Postgres Advanced Server (EPAS) logs unredacted passwords prior to 14.6.0 -

-
EDB Postgres Advanced Server 10.23.32 to 14.5.0
+  Updated: 2023/05/02 +

CVE-2023-31043 - EDB Postgres Advanced Server (EPAS) logs unredacted passwords prior to 14.6.0

+
EDB Postgres Advanced Server 10.23.32 to 14.5.0
Summary:  @@ -168,43 +196,54 @@ EDB Postgres Advanced Server (EPAS) versions before 14.6.0 log unredacted passwo
Read More...
-## Updated 2022 - + + +
+

Updated 2022

+ + + + -
-

CVE-2019-10128

+

CVE-2019-10128

  Read Advisory -  Updated: 2022/01/01 -

EDB supplied PostgreSQL inherits ACL for installation directory -

-
PostgreSQL
+  Updated: 2022/01/01 +

CVE-2019-10128 - EDB supplied PostgreSQL inherits ACL for installation directory

+
PostgreSQL
Summary:  -A vulnerability was found in PostgreSQL versions 11.x prior to 11.3. The Windows installer for EDB-supplied PostgreSQL does not lock down the ACL of the binary installation directory or the ACL of the data directory; it keeps the inherited ACL. In the default configuration, this allows a local attacker to read arbitrary data directory files, essentially bypassing database-imposed read access limitations. In plausible non-default configurations, an attacker having both an unprivileged Windows account and an unprivileged PostgreSQL account can cause the PostgreSQL service account to execute arbitrary code. +A vulnerability was found in PostgreSQL versions 11.x prior to 11.3. The Windows installer for EnterpriseDB-supplied PostgreSQL does not lock down the ACL of the binary installation directory or the ACL of the data directory; it keeps the inherited ACL. In the default configuration, this allows a local attacker to read arbitrary data directory files, essentially bypassing database-imposed read access limitations. In plausible non-default configurations, an attacker having both an unprivileged Windows account and an unprivileged PostgreSQL account can cause the PostgreSQL service account to execute arbitrary code.
Read More...
-## Updated 2018 - + + +
+

Updated 2018

+ + + +
-

CVE-2007-4639

+

CVE-2007-4639

  Read Advisory -  Updated: 2018/10/15 -

EDB Advanced Server 8.2 improperly handles debugging function calls -

-
EDB Postgres Advanced Server version 8.2
+  Updated: 2018/10/15 +

CVE-2007-4639 - EDB Advanced Server 8.2 improperly handles debugging function calls

+
EDB Advanced Server 8.2
Summary:  -EDB Postgres Advanced Server 8.2 does not properly handle certain debugging function calls that occur before a call to pldbg_create_listener, which allows remote authenticated users to cause a denial of service (daemon crash) and possibly execute arbitrary code via a SELECT statement that invokes a pldbg_ function, as demonstrated by (1) pldbg_get_stack and (2) pldbg_abort_target, which triggers use of an uninitialized pointer.
+EDB Postgres Advanced Server 8.2 (EPAS) does not properly handle certain debugging function calls that occur before a call to `pldbg_create_listener`, which allows remote authenticated users to cause a denial of service (daemon crash) and possibly execute arbitrary code via a SELECT statement that invokes a `pldbg_` function, as demonstrated by (1) `pldbg_get_stack` and (2) `pldbg_abort_target`, which triggers use of an uninitialized pointer. +
Read More... -
+ + + diff --git a/advocacy_docs/security/index.mdx b/advocacy_docs/security/index.mdx index 4dccdc88fbc..00537b22c9c 100644 --- a/advocacy_docs/security/index.mdx +++ b/advocacy_docs/security/index.mdx @@ -24,14 +24,15 @@ This policy outlines how EnterpriseDB handles disclosures related to suspected v ## Most Recent Advisories + + + + + + + + - - - - - - - + + +
-

CVE-2023-41120

+

CVE-2023-41120

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission -

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+  Updated: 2023/08/30 +

CVE-2023-41120 - EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  @@ -40,31 +41,31 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1 Read More...
-

CVE-2023-41119

+

CVE-2023-41119

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser -

-
All EnterpriseDB Postgres Advanced Server (EPAS) versions prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+  Updated: 2023/08/30 +

CVE-2023-41119 - EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It contains the function _dbms_aq_move_to_exception_queue that may be used to elevate a user's privileges to superuser. This function accepts the OID of a table, and then accesses that table as the superuser by using SELECT and DML commands.
Read More... -
-
-

CVE-2023-41118

+

CVE-2023-41118

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass -

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 +  Updated: 2023/08/30 +

CVE-2023-41118 - EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+
Summary:  An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It may allow an authenticated user to bypass authorization requirements and access underlying implementation functions. When a superuser has configured file locations using CREATE DIRECTORY, these functions allow users to take a wide range of actions, including read, write, copy, rename, and delete. @@ -72,31 +73,30 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1 Read More...
-

CVE-2023-41117

+

CVE-2023-41117

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+  Updated: 2023/08/30 +

CVE-2023-41117 - EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It contain packages, standalone packages, and functions that run SECURITY DEFINER but are inadequately secured against search_path attacks.
Read More... -
-
-

CVE-2023-41116

+

CVE-2023-41116

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) permission bypass for materialized views -

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+  Updated: 2023/08/30 +

CVE-2023-41116 - EDB Postgres Advanced Server (EPAS) permission bypass for materialized views

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  @@ -105,14 +105,14 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1 Read More...
-

CVE-2023-41115

+

CVE-2023-41115

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) permission bypass for large objects -

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+  Updated: 2023/08/30 +

CVE-2023-41115 - EDB Postgres Advanced Server (EPAS) permission bypass for large objects

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  @@ -122,21 +122,13 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1
-

CVE-2023-41114

+

CVE-2023-41114

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL -

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+  Updated: 2023/08/30 +

CVE-2023-41114 - EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  @@ -147,30 +139,28 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1
-

CVE-2023-41113

+

CVE-2023-41113

  Read Advisory -  Updated: 2023/08/30 -

EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory() -

-
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
+  Updated: 2023/08/30 +

CVE-2023-41113 - EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory()

+
All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
Summary:  An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 11.21.32, 12.x before 12.16.20, 13.x before 13.12.16, 14.x before 14.9.0, and 15.x before 15.4.0. It allows an authenticated user to to obtain information about whether certain files exist on disk, what errors if any occur when attempting to read them, and some limited information about their contents (regardless of permissions). This can occur when a superuser has configured one or more directories for filesystem access via CREATE DIRECTORY and adopted certain non-default settings for log_line_prefix and log_connections.
Read More... -
-
-

CVE-2023-31043

+

CVE-2023-31043

  Read Advisory -  Updated: 2023/05/02 -

EDB Postgres Advanced Server (EPAS) logs unredacted passwords prior to 14.6.0 -

-
EDB Postgres Advanced Server 10.23.32 to 14.5.0
+  Updated: 2023/05/02 +

CVE-2023-31043 - EDB Postgres Advanced Server (EPAS) logs unredacted passwords prior to 14.6.0

+
EDB Postgres Advanced Server 10.23.32 to 14.5.0
Summary:  @@ -178,4 +168,6 @@ EDB Postgres Advanced Server (EPAS) versions before 14.6.0 log unredacted passwo
Read More...
+ diff --git a/advocacy_docs/security/templates/advisoriesindex.njs b/advocacy_docs/security/templates/advisoriesindex.njs new file mode 100755 index 00000000000..6597c3c0fe5 --- /dev/null +++ b/advocacy_docs/security/templates/advisoriesindex.njs @@ -0,0 +1,39 @@ +--- +title: EDB Security Advisories +navTitle: Advisories +iconName: Security +hideKBLink: true +hideToC: false +navigation:{% for cve in cvesorted %} +- {{ cve }}{% endfor %} +--- + +{% set updatedYear = -1 %} + +{% for cve in cvesorted %} +{% set thiscve = cves[cve] %} +{% set lastUpdatedYear = thiscve.open_last_updated.slice(0,4) %} +{% if lastUpdatedYear != updatedYear %} +{% if updatedYear != -1 %}{% endif %} +

Updated {{ lastUpdatedYear }}

+{% set updatedYear = lastUpdatedYear %} + +{% endif %} + + +{% endfor %} +
+

{{ thiscve.vulnerability_details_cve_id }}

+ +  Read Advisory +  Updated: {{ thiscve.open_last_updated }} +

{{ thiscve.frontmatter_title }}

+
{{ thiscve.frontmatter_affectedProducts }}
+ +
+Summary:  +{{ thiscve.summary_0 }} +
+Read More... +
+ diff --git a/advocacy_docs/security/templates/securityindex.njs b/advocacy_docs/security/templates/securityindex.njs new file mode 100755 index 00000000000..041bbf2c906 --- /dev/null +++ b/advocacy_docs/security/templates/securityindex.njs @@ -0,0 +1,45 @@ +--- +title: EDB Security +navTitle: EDB Security +directoryDefaults: + iconName: Security + indexCards: none + hideKBLink: true +navigation: + - vulnerability-disclosure-policy + - advisories +--- + +EDB is committed to a security first approach, from the products we build and the platforms we operate, to the services we provide our customers. Transparency is a core principle for the program and part of this effort includes welcoming incoming reports so that we can address concerns surfaced by our customers or security researchers. You’ll also find it in our advisories, which detail issues found and the required fixes or mitigations needed to keep your data and databases safe. + +## Policies + +*

EDB Vulnerability Disclosure Policy

+This policy outlines how EnterpriseDB handles disclosures related to suspected vulnerabilities within our products, systems, or services. It also provides guidance for those who wish to perform security research, or may have discovered a potential security vulnerability impacting EDB. + +## Advisories + +*

Full list of advisories issued

+ +## Most Recent Advisories + + +{% for cve in shortcvelist %} +{% set thiscve = cves[cve] %} + +{% endfor %} +
+

{{ thiscve.vulnerability_details_cve_id }}

+ +  Read Advisory +  Updated: {{ thiscve.open_last_updated }} +

{{ thiscve.frontmatter_title }}

+
{{ thiscve.frontmatter_affectedProducts }}
+ +
+Summary:  +{{ thiscve.summary_0 }} +
+Read More... +
+ diff --git a/tools/automation/generators/advisoryindex/advisoryindex.js b/tools/automation/generators/advisoryindex/advisoryindex.js new file mode 100755 index 00000000000..c360f1af953 --- /dev/null +++ b/tools/automation/generators/advisoryindex/advisoryindex.js @@ -0,0 +1,173 @@ +const fs = require('fs'); +const matter = require('gray-matter'); +const MarkdownIt = require('markdown-it'); +const njk = require('nunjucks'); +const { basename, join } = require('path'); +const parseArgs = require('minimist'); +const { addAbortListener } = require('events'); + +var argv = parseArgs(process.argv.slice(2)); + +if (argv.root == undefined) { + console.log("Need --root"); + process.exit(1); +} + +const securityRoot = argv.root; + +let seccount=10; + +if (argv.count != undefined) { + seccount=parseInt(argv.count); +} + +// We are going to process the advisories in +const advisoriesDir = join(securityRoot, "advisories"); +// To produce an index file named +const advisoriesIndex = join(advisoriesDir, "index.mdx"); +// And another similar but shorted one named +const securityIndex = join(securityRoot, "index.mdx"); + +// Using templates in a directory called +const templatesDir = join(securityRoot, "templates"); + +function parseMarkdownFile(filePath) { + const fileContent = fs.readFileSync(filePath, 'utf8'); + const parsedMatter = matter(fileContent); + + const sections = parsedMatter.content.split('\n#').slice(0); // split at headings + const sectionDicts = sections.map(section => { + const lines = section.split('\n'); + const heading = lines[0].replace('#', '').trim(); + const content = lines.slice(1); + var parsedContent = []; + content.forEach((line, index) => { + if (line !== '') { + if (line.startsWith('* [')) { + // This is a line with a link + // For now, we drop links completely + } else if (line.indexOf(':') > 0) { + const colon = line.indexOf(':'); + let key = line.slice(0, colon); + if (key.startsWith('* ')) { + key = key.slice(2); + } + const value = line.slice(colon + 1).trim(); + + parsedContent.push({ [slugify(key)]: value }); + } else { + parsedContent.push(line); + } + } + }); + + if (heading === '') { + return { ["open"]: parsedContent }; + } + + return { [slugify(heading)]: parsedContent }; + }); + + let docMap = {} + + // add the parsedMatter data to the docmap + Object.keys(parsedMatter.data).forEach(key => { + docMap["frontmatter_" + key] = parsedMatter.data[key]; + }); + + const path = basename(filePath, ".mdx"); + + docMap["filename"] = path; + + // add the flattened sections to the docMap + sectionDicts.forEach(section => { + Object.keys(section).forEach(key => { + let value = section[key]; + if (Array.isArray(value)) { + for (let i = 0; i < value.length; i++) { + if (typeof value[i] === 'object') { + Object.keys(value[i]).forEach(subkey => { + docMap[key + '_' + subkey] = value[i][subkey]; + }) + } else { + docMap[key + '_' + i] = value[i]; + } + } + value = value.join('\n'); + } else { + docMap[key] = value; + } + }) + });; + + return docMap; +} + +// function that takes a string and returns it in lower case, with no spaces +function slugify(string) { + return string + .toLowerCase() + .replace(/[-]+/g, '_') + .replace(/\s+/g, '_') + .replace(/[^\w-]+/g, '') + ; +} + +function cleanCVE(string) { + if (string[0] == "[") { + return string.slice(1, string.indexOf("]", 1)); + } + return string; +} + +// Iterate over all the files that start cve and end with mdx in the source directory, and parse them + +njk.configure(templatesDir, { autoescape: false }); + + + +const files = fs.readdirSync(advisoriesDir).filter(fn => fn.startsWith('cve') && fn.endsWith('mdx')); +files.sort().reverse(); +const cvelist = files.map(file => { return file.replace(/\.[^/.]+$/, "") }); + +let namespace = {}; +let allDocMap = {}; + +cvelist.forEach(cve => { + const docMap = parseMarkdownFile(join(advisoriesDir, cve + '.mdx')); + docMap['vulnerability_details_cve_id'] = cleanCVE(docMap['vulnerability_details_cve_id']); + allDocMap[cve] = docMap; +}); + + +let shortcvelist = []; +let lastyear = ""; +let count = 0; +cvelist.forEach(cve => { + const year = cve.substring(3, 7); + if (lastyear=="") { + count = 0; + lastyear = year; + } else if (lastyear!=year) { + return; + } + if (count < seccount) { + shortcvelist.push(cve); + count++; + } +}); + +namespace["shortcvelist"]= shortcvelist; +namespace["cvesorted"] = cvelist; +namespace["cves"] = allDocMap; + +//console.log(JSON.stringify(namespace, null, 2)); + +const res = njk.render("advisoriesindex.njs", namespace); + +fs.writeFileSync(advisoriesIndex, res); + +const res2 = njk.render("securityindex.njs", namespace); + +fs.writeFileSync(securityIndex,res2); + diff --git a/tools/automation/generators/advisoryindex/package-lock.json b/tools/automation/generators/advisoryindex/package-lock.json new file mode 100644 index 00000000000..84e0b3a6ad6 --- /dev/null +++ b/tools/automation/generators/advisoryindex/package-lock.json @@ -0,0 +1,216 @@ +{ + "name": "jssecindexes", + "version": "1.0.0", + "lockfileVersion": 3, + "requires": true, + "packages": { + "": { + "name": "jssecindexes", + "version": "1.0.0", + "license": "ISC", + "dependencies": { + "gray-matter": "^4.0.3", + "markdown-it": "^13.0.1", + "minimist": "^1.2.8", + "nunjucks": "^3.2.4" + } + }, + "node_modules/a-sync-waterfall": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/a-sync-waterfall/-/a-sync-waterfall-1.0.1.tgz", + "integrity": "sha512-RYTOHHdWipFUliRFMCS4X2Yn2X8M87V/OpSqWzKKOGhzqyUxzyVmhHDH9sAvG+ZuQf/TAOFsLCpMw09I1ufUnA==" + }, + "node_modules/argparse": { + "version": "1.0.10", + "resolved": "https://registry.npmjs.org/argparse/-/argparse-1.0.10.tgz", + "integrity": "sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==", + "dependencies": { + "sprintf-js": "~1.0.2" + } + }, + "node_modules/asap": { + "version": "2.0.6", + "resolved": "https://registry.npmjs.org/asap/-/asap-2.0.6.tgz", + "integrity": "sha512-BSHWgDSAiKs50o2Re8ppvp3seVHXSRM44cdSsT9FfNEUUZLOGWVCsiWaRPWM1Znn+mqZ1OfVZ3z3DWEzSp7hRA==" + }, + "node_modules/commander": { + "version": "5.1.0", + "resolved": "https://registry.npmjs.org/commander/-/commander-5.1.0.tgz", + "integrity": "sha512-P0CysNDQ7rtVw4QIQtm+MRxV66vKFSvlsQvGYXZWR3qFU0jlMKHZZZgw8e+8DSah4UDKMqnknRDQz+xuQXQ/Zg==", + "engines": { + "node": ">= 6" + } + }, + "node_modules/entities": { + "version": "3.0.1", + "resolved": "https://registry.npmjs.org/entities/-/entities-3.0.1.tgz", + "integrity": "sha512-WiyBqoomrwMdFG1e0kqvASYfnlb0lp8M5o5Fw2OFq1hNZxxcNk8Ik0Xm7LxzBhuidnZB/UtBqVCgUz3kBOP51Q==", + "engines": { + "node": ">=0.12" + }, + "funding": { + "url": "https://github.com/fb55/entities?sponsor=1" + } + }, + "node_modules/esprima": { + "version": "4.0.1", + "resolved": "https://registry.npmjs.org/esprima/-/esprima-4.0.1.tgz", + "integrity": "sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==", + "bin": { + "esparse": "bin/esparse.js", + "esvalidate": "bin/esvalidate.js" + }, + "engines": { + "node": ">=4" + } + }, + "node_modules/extend-shallow": { + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-2.0.1.tgz", + "integrity": "sha512-zCnTtlxNoAiDc3gqY2aYAWFx7XWWiasuF2K8Me5WbN8otHKTUKBwjPtNpRs/rbUZm7KxWAaNj7P1a/p52GbVug==", + "dependencies": { + "is-extendable": "^0.1.0" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/gray-matter": { + "version": "4.0.3", + "resolved": "https://registry.npmjs.org/gray-matter/-/gray-matter-4.0.3.tgz", + "integrity": "sha512-5v6yZd4JK3eMI3FqqCouswVqwugaA9r4dNZB1wwcmrD02QkV5H0y7XBQW8QwQqEaZY1pM9aqORSORhJRdNK44Q==", + "dependencies": { + "js-yaml": "^3.13.1", + "kind-of": "^6.0.2", + "section-matter": "^1.0.0", + "strip-bom-string": "^1.0.0" + }, + "engines": { + "node": ">=6.0" + } + }, + "node_modules/is-extendable": { + "version": "0.1.1", + "resolved": "https://registry.npmjs.org/is-extendable/-/is-extendable-0.1.1.tgz", + "integrity": "sha512-5BMULNob1vgFX6EjQw5izWDxrecWK9AM72rugNr0TFldMOi0fj6Jk+zeKIt0xGj4cEfQIJth4w3OKWOJ4f+AFw==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/js-yaml": { + "version": "3.14.1", + "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.14.1.tgz", + "integrity": "sha512-okMH7OXXJ7YrN9Ok3/SXrnu4iX9yOk+25nqX4imS2npuvTYDmo/QEZoqwZkYaIDk3jVvBOTOIEgEhaLOynBS9g==", + "dependencies": { + "argparse": "^1.0.7", + "esprima": "^4.0.0" + }, + "bin": { + "js-yaml": "bin/js-yaml.js" + } + }, + "node_modules/kind-of": { + "version": "6.0.3", + "resolved": "https://registry.npmjs.org/kind-of/-/kind-of-6.0.3.tgz", + "integrity": "sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/linkify-it": { + "version": "4.0.1", + "resolved": "https://registry.npmjs.org/linkify-it/-/linkify-it-4.0.1.tgz", + "integrity": "sha512-C7bfi1UZmoj8+PQx22XyeXCuBlokoyWQL5pWSP+EI6nzRylyThouddufc2c1NDIcP9k5agmN9fLpA7VNJfIiqw==", + "dependencies": { + "uc.micro": "^1.0.1" + } + }, + "node_modules/markdown-it": { + "version": "13.0.1", + "resolved": "https://registry.npmjs.org/markdown-it/-/markdown-it-13.0.1.tgz", + "integrity": "sha512-lTlxriVoy2criHP0JKRhO2VDG9c2ypWCsT237eDiLqi09rmbKoUetyGHq2uOIRoRS//kfoJckS0eUzzkDR+k2Q==", + "dependencies": { + "argparse": "^2.0.1", + "entities": "~3.0.1", + "linkify-it": "^4.0.1", + "mdurl": "^1.0.1", + "uc.micro": "^1.0.5" + }, + "bin": { + "markdown-it": "bin/markdown-it.js" + } + }, + "node_modules/markdown-it/node_modules/argparse": { + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz", + "integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==" + }, + "node_modules/mdurl": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/mdurl/-/mdurl-1.0.1.tgz", + "integrity": "sha512-/sKlQJCBYVY9Ers9hqzKou4H6V5UWc/M59TH2dvkt+84itfnq7uFOMLpOiOS4ujvHP4etln18fmIxA5R5fll0g==" + }, + "node_modules/minimist": { + "version": "1.2.8", + "resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.8.tgz", + "integrity": "sha512-2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA==", + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/nunjucks": { + "version": "3.2.4", + "resolved": "https://registry.npmjs.org/nunjucks/-/nunjucks-3.2.4.tgz", + "integrity": "sha512-26XRV6BhkgK0VOxfbU5cQI+ICFUtMLixv1noZn1tGU38kQH5A5nmmbk/O45xdyBhD1esk47nKrY0mvQpZIhRjQ==", + "dependencies": { + "a-sync-waterfall": "^1.0.0", + "asap": "^2.0.3", + "commander": "^5.1.0" + }, + "bin": { + "nunjucks-precompile": "bin/precompile" + }, + "engines": { + "node": ">= 6.9.0" + }, + "peerDependencies": { + "chokidar": "^3.3.0" + }, + "peerDependenciesMeta": { + "chokidar": { + "optional": true + } + } + }, + "node_modules/section-matter": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/section-matter/-/section-matter-1.0.0.tgz", + "integrity": "sha512-vfD3pmTzGpufjScBh50YHKzEu2lxBWhVEHsNGoEXmCmn2hKGfeNLYMzCJpe8cD7gqX7TJluOVpBkAequ6dgMmA==", + "dependencies": { + "extend-shallow": "^2.0.1", + "kind-of": "^6.0.0" + }, + "engines": { + "node": ">=4" + } + }, + "node_modules/sprintf-js": { + "version": "1.0.3", + "resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.0.3.tgz", + "integrity": "sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g==" + }, + "node_modules/strip-bom-string": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/strip-bom-string/-/strip-bom-string-1.0.0.tgz", + "integrity": "sha512-uCC2VHvQRYu+lMh4My/sFNmF2klFymLX1wHJeXnbEJERpV/ZsVuonzerjfrGpIGF7LBVa1O7i9kjiWvJiFck8g==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/uc.micro": { + "version": "1.0.6", + "resolved": "https://registry.npmjs.org/uc.micro/-/uc.micro-1.0.6.tgz", + "integrity": "sha512-8Y75pvTYkLJW2hWQHXxoqRgV7qb9B+9vFEtidML+7koHUFapnVJAZ6cKs+Qjz5Aw3aZWHMC6u0wJE3At+nSGwA==" + } + } +} diff --git a/tools/automation/generators/advisoryindex/package.json b/tools/automation/generators/advisoryindex/package.json new file mode 100755 index 00000000000..f979649a8cc --- /dev/null +++ b/tools/automation/generators/advisoryindex/package.json @@ -0,0 +1,17 @@ +{ + "name": "jssecindexes", + "version": "1.0.0", + "description": "", + "main": "advisoryindex.js", + "scripts": { + "test": "echo \"Error: no test specified\" && exit 1" + }, + "author": "", + "license": "ISC", + "dependencies": { + "gray-matter": "^4.0.3", + "markdown-it": "^13.0.1", + "minimist": "^1.2.8", + "nunjucks": "^3.2.4" + } +} From f3d7f29ac566a772e8f8428511d292b21d1bf5eb Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Mon, 11 Sep 2023 19:44:57 +0100 Subject: [PATCH 139/255] Fixes to title rendering Signed-off-by: Dj Walker-Morgan --- advocacy_docs/security/advisories/index.mdx | 22 +++++++++---------- advocacy_docs/security/index.mdx | 18 +++++++-------- .../generators/advisoryindex/advisoryindex.js | 3 +++ 3 files changed, 23 insertions(+), 20 deletions(-) diff --git a/advocacy_docs/security/advisories/index.mdx b/advocacy_docs/security/advisories/index.mdx index 02ac823fd9e..637af7e7864 100644 --- a/advocacy_docs/security/advisories/index.mdx +++ b/advocacy_docs/security/advisories/index.mdx @@ -35,7 +35,7 @@ navigation:   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41120 - EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission

+

EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -54,7 +54,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41119 - EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser

+

EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -73,7 +73,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41118 - EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass

+

EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -92,7 +92,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41117 - EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path

+

EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -111,7 +111,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41116 - EDB Postgres Advanced Server (EPAS) permission bypass for materialized views

+

EDB Postgres Advanced Server (EPAS) permission bypass for materialized views

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -130,7 +130,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41115 - EDB Postgres Advanced Server (EPAS) permission bypass for large objects

+

EDB Postgres Advanced Server (EPAS) permission bypass for large objects

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -149,7 +149,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41114 - EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL

+

EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -168,7 +168,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41113 - EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory()

+

EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory()

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -187,7 +187,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/05/02 -

CVE-2023-31043 - EDB Postgres Advanced Server (EPAS) logs unredacted passwords prior to 14.6.0

+

EDB Postgres Advanced Server (EPAS) logs unredacted passwords prior to 14.6.0

EDB Postgres Advanced Server 10.23.32 to 14.5.0
@@ -211,7 +211,7 @@ EDB Postgres Advanced Server (EPAS) versions before 14.6.0 log unredacted passwo   Read Advisory   Updated: 2022/01/01 -

CVE-2019-10128 - EDB supplied PostgreSQL inherits ACL for installation directory

+

EDB supplied PostgreSQL inherits ACL for installation directory

PostgreSQL
@@ -235,7 +235,7 @@ A vulnerability was found in PostgreSQL versions 11.x prior to 11.3. The Windows   Read Advisory   Updated: 2018/10/15 -

CVE-2007-4639 - EDB Advanced Server 8.2 improperly handles debugging function calls

+

EDB Advanced Server 8.2 improperly handles debugging function calls

EDB Advanced Server 8.2
diff --git a/advocacy_docs/security/index.mdx b/advocacy_docs/security/index.mdx index 00537b22c9c..015f43f180c 100644 --- a/advocacy_docs/security/index.mdx +++ b/advocacy_docs/security/index.mdx @@ -31,7 +31,7 @@ This policy outlines how EnterpriseDB handles disclosures related to suspected v   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41120 - EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission

+

EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -47,7 +47,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41119 - EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser

+

EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -63,7 +63,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41118 - EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass

+

EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -79,7 +79,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41117 - EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path

+

EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -95,7 +95,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41116 - EDB Postgres Advanced Server (EPAS) permission bypass for materialized views

+

EDB Postgres Advanced Server (EPAS) permission bypass for materialized views

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -111,7 +111,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41115 - EDB Postgres Advanced Server (EPAS) permission bypass for large objects

+

EDB Postgres Advanced Server (EPAS) permission bypass for large objects

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -127,7 +127,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41114 - EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL

+

EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -143,7 +143,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/08/30 -

CVE-2023-41113 - EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory()

+

EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory()

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
@@ -159,7 +159,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1   Read Advisory   Updated: 2023/05/02 -

CVE-2023-31043 - EDB Postgres Advanced Server (EPAS) logs unredacted passwords prior to 14.6.0

+

EDB Postgres Advanced Server (EPAS) logs unredacted passwords prior to 14.6.0

EDB Postgres Advanced Server 10.23.32 to 14.5.0
diff --git a/tools/automation/generators/advisoryindex/advisoryindex.js b/tools/automation/generators/advisoryindex/advisoryindex.js index c360f1af953..0f416ee08e3 100755 --- a/tools/automation/generators/advisoryindex/advisoryindex.js +++ b/tools/automation/generators/advisoryindex/advisoryindex.js @@ -135,7 +135,10 @@ let allDocMap = {}; cvelist.forEach(cve => { const docMap = parseMarkdownFile(join(advisoriesDir, cve + '.mdx')); + // make sure the cve id isn't a link docMap['vulnerability_details_cve_id'] = cleanCVE(docMap['vulnerability_details_cve_id']); + // trim the cve id off the front of the title + docMap['frontmatter_title']=docMap['frontmatter_title'].slice(docMap['frontmatter_title'].indexOf(" - ")+3); allDocMap[cve] = docMap; }); From cc4ba15b68518542bc82d38206d24815dc979ebe Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 13 Sep 2023 10:58:58 +0100 Subject: [PATCH 140/255] Fixes as per comments Signed-off-by: Dj Walker-Morgan --- .../security/advisories/cve20074639.mdx | 12 +- .../security/advisories/cve201910128.mdx | 12 +- .../security/advisories/cve202331043.mdx | 12 +- advocacy_docs/security/advisories/index.mdx | 25 ++-- advocacy_docs/security/index.mdx | 19 +-- .../security/templates/advisoriesindex.njs | 13 +- .../security/templates/securityindex.njs | 11 +- .../generators/advisoryindex/advisoryindex.js | 116 ++++++++---------- 8 files changed, 108 insertions(+), 112 deletions(-) diff --git a/advocacy_docs/security/advisories/cve20074639.mdx b/advocacy_docs/security/advisories/cve20074639.mdx index 591e5d8dc02..1c57efdc3c2 100644 --- a/advocacy_docs/security/advisories/cve20074639.mdx +++ b/advocacy_docs/security/advisories/cve20074639.mdx @@ -14,10 +14,14 @@ EDB Postgres Advanced Server 8.2 (EPAS) does not properly handle certain debuggi ## Vulnerability details -CVE-ID: [CVE-2007-4639](https://nvd.nist.gov/vuln/detail/CVE-2007-4639) -CVSS Base Score: Undefined -CVSS Temporal Score: Undefined -CVSS Environmental Score: Undefined +CVE-ID: [CVE-2007-4639](https://nvd.nist.gov/vuln/detail/CVE-2007-4639) + +CVSS Base Score: Undefined + +CVSS Temporal Score: Undefined + +CVSS Environmental Score: Undefined + CVSS Vector: Undefined ## Affected products and versions diff --git a/advocacy_docs/security/advisories/cve201910128.mdx b/advocacy_docs/security/advisories/cve201910128.mdx index ac0edcd989b..d87a9c9da71 100644 --- a/advocacy_docs/security/advisories/cve201910128.mdx +++ b/advocacy_docs/security/advisories/cve201910128.mdx @@ -14,10 +14,14 @@ A vulnerability was found in PostgreSQL versions 11.x prior to 11.3. The Windows ## Vulnerability details -CVE-ID: [CVE-2019-10128](https://nvd.nist.gov/vuln/detail/CVE-2019-10128) -CVSS Base Score: 7.8 -CVSS Temporal Score: Undefined -CVSS Environmental Score: Undefined +CVE-ID: [CVE-2019-10128](https://nvd.nist.gov/vuln/detail/CVE-2019-10128) + +CVSS Base Score: 7.8 + +CVSS Temporal Score: Undefined + +CVSS Environmental Score: Undefined + CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H ## Affected products and versions diff --git a/advocacy_docs/security/advisories/cve202331043.mdx b/advocacy_docs/security/advisories/cve202331043.mdx index bf46090ac4b..1edaf3fd5c5 100644 --- a/advocacy_docs/security/advisories/cve202331043.mdx +++ b/advocacy_docs/security/advisories/cve202331043.mdx @@ -14,10 +14,14 @@ EDB Postgres Advanced Server (EPAS) versions before 14.6.0 log unredacted passwo ## Vulnerability details -CVE-ID: [CVE-2023-31043](https://nvd.nist.gov/vuln/detail/CVE-2023-31043) -CVSS Base Score: 7.5 -CVSS Temporal Score: Undefined -CVSS Environmental Score: Undefined +CVE-ID: [CVE-2023-31043](https://nvd.nist.gov/vuln/detail/CVE-2023-31043) + +CVSS Base Score: 7.5 + +CVSS Temporal Score: Undefined + +CVSS Environmental Score: Undefined + CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N ## Affected products and versions diff --git a/advocacy_docs/security/advisories/index.mdx b/advocacy_docs/security/advisories/index.mdx index 637af7e7864..0b7733b715f 100644 --- a/advocacy_docs/security/advisories/index.mdx +++ b/advocacy_docs/security/advisories/index.mdx @@ -1,4 +1,5 @@ --- +WARNING: THIS IS AN AUTOMATICALLY GENERATED FILE - DO NOT MANUALLY EDIT - SEE tools/automation/generators/advisoryindex title: EDB Security Advisories navTitle: Advisories iconName: Security @@ -34,7 +35,7 @@ navigation:

CVE-2023-41120

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -53,7 +54,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-41119

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -72,7 +73,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-41118

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -91,7 +92,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-41117

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -110,7 +111,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-41116

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) permission bypass for materialized views

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -129,7 +130,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-41115

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) permission bypass for large objects

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -148,7 +149,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-41114

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -167,7 +168,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-41113

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory()

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -186,7 +187,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-31043

  Read Advisory -  Updated: 2023/05/02 +  Updated: 2023/05/02

EDB Postgres Advanced Server (EPAS) logs unredacted passwords prior to 14.6.0

EDB Postgres Advanced Server 10.23.32 to 14.5.0
 @@ -210,7 +211,7 @@ EDB Postgres Advanced Server (EPAS) versions before 14.6.0 log unredacted passwo

CVE-2019-10128

  Read Advisory -  Updated: 2022/01/01 +  Updated: 2022/01/01

EDB supplied PostgreSQL inherits ACL for installation directory

PostgreSQL
 @@ -234,13 +235,13 @@ A vulnerability was found in PostgreSQL versions 11.x prior to 11.3. The Windows

CVE-2007-4639

  Read Advisory -  Updated: 2018/10/15 +  Updated: 2018/10/15

EDB Advanced Server 8.2 improperly handles debugging function calls

EDB Advanced Server 8.2
Summary:  -EDB Postgres Advanced Server 8.2 (EPAS) does not properly handle certain debugging function calls that occur before a call to `pldbg_create_listener`, which allows remote authenticated users to cause a denial of service (daemon crash) and possibly execute arbitrary code via a SELECT statement that invokes a `pldbg_` function, as demonstrated by (1) `pldbg_get_stack` and (2) `pldbg_abort_target`, which triggers use of an uninitialized pointer. +EDB Postgres Advanced Server 8.2 (EPAS) does not properly handle certain debugging function calls that occur before a call to pldbg_create_listener, which allows remote authenticated users to cause a denial of service (daemon crash) and possibly execute arbitrary code via a SELECT statement that invokes a pldbg_ function, as demonstrated by (1) pldbg_get_stack and (2) pldbg_abort_target, which triggers use of an uninitialized pointer.
Read More...
diff --git a/advocacy_docs/security/index.mdx b/advocacy_docs/security/index.mdx index 015f43f180c..10992ea9b62 100644 --- a/advocacy_docs/security/index.mdx +++ b/advocacy_docs/security/index.mdx @@ -1,4 +1,5 @@ --- +WARNING: THIS IS AN AUTOMATICALLY GENERATED FILE - DO NOT MANUALLY EDIT - SEE tools/automation/generators/advisoryindex title: EDB Security navTitle: EDB Security directoryDefaults: @@ -30,7 +31,7 @@ This policy outlines how EnterpriseDB handles disclosures related to suspected v

CVE-2023-41120

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) DBMS_PROFILER data may be removed without permission

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -46,7 +47,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-41119

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) dbms_aq helper function may run arbitrary SQL as a superuser

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -62,7 +63,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-41118

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) UTL_FILE permission bypass

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -78,7 +79,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-41117

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) SECURITY DEFINER functions and procedures may be hijacked via search_path

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -94,7 +95,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-41116

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) permission bypass for materialized views

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -110,7 +111,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-41115

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) permission bypass for large objects

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -126,7 +127,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-41114

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) authenticated users may fetch any URL

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -142,7 +143,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-41113

  Read Advisory -  Updated: 2023/08/30 +  Updated: 2023/08/30

EDB Postgres Advanced Server (EPAS) permissions bypass via accesshistory()

All versions of EnterpriseDB Postgres Advanced Server (EPAS) prior to 11.21.32, 12.16.20, 13.12.17, 14.9.0, 15.4.0
 @@ -158,7 +159,7 @@ An issue was discovered in EnterpriseDB Postgres Advanced Server (EPAS) before 1

CVE-2023-31043

  Read Advisory -  Updated: 2023/05/02 +  Updated: 2023/05/02

EDB Postgres Advanced Server (EPAS) logs unredacted passwords prior to 14.6.0

EDB Postgres Advanced Server 10.23.32 to 14.5.0
 diff --git a/advocacy_docs/security/templates/advisoriesindex.njs b/advocacy_docs/security/templates/advisoriesindex.njs index 6597c3c0fe5..07449f319a6 100755 --- a/advocacy_docs/security/templates/advisoriesindex.njs +++ b/advocacy_docs/security/templates/advisoriesindex.njs @@ -1,4 +1,5 @@ --- +WARNING: THIS IS AN AUTOMATICALLY GENERATED FILE - DO NOT MANUALLY EDIT - SEE tools/automation/generators/advisoryindex title: EDB Security Advisories navTitle: Advisories iconName: Security @@ -12,7 +13,7 @@ navigation:{% for cve in cvesorted %} {% for cve in cvesorted %} {% set thiscve = cves[cve] %} -{% set lastUpdatedYear = thiscve.open_last_updated.slice(0,4) %} +{% set lastUpdatedYear = thiscve.open.last_updated.slice(0,4) %} {% if lastUpdatedYear != updatedYear %} {% if updatedYear != -1 %}{% endif %}

Updated {{ lastUpdatedYear }}

@@ -21,16 +22,16 @@ navigation:{% for cve in cvesorted %} {% endif %} -

{{ thiscve.vulnerability_details_cve_id }}

+

{{ thiscve.vulnerability_details.cve_id }}

  Read Advisory -  Updated: {{ thiscve.open_last_updated }} -

{{ thiscve.frontmatter_title }}

-
{{ thiscve.frontmatter_affectedProducts }}
+  Updated: {{ thiscve.open.last_updated }} +

{{ thiscve.frontmatter.title }}

+
{{ thiscve.frontmatter.affectedProducts }}
Summary:  -{{ thiscve.summary_0 }} +{{ thiscve.summary[0].replaceAll(r/`([^`]*)`/g,"$1") }}
Read More...
diff --git a/advocacy_docs/security/templates/securityindex.njs b/advocacy_docs/security/templates/securityindex.njs index 041bbf2c906..adb91f287be 100755 --- a/advocacy_docs/security/templates/securityindex.njs +++ b/advocacy_docs/security/templates/securityindex.njs @@ -1,4 +1,5 @@ --- +WARNING: THIS IS AN AUTOMATICALLY GENERATED FILE - DO NOT MANUALLY EDIT - SEE tools/automation/generators/advisoryindex title: EDB Security navTitle: EDB Security directoryDefaults: @@ -27,16 +28,16 @@ This policy outlines how EnterpriseDB handles disclosures related to suspected v {% for cve in shortcvelist %} {% set thiscve = cves[cve] %} -

{{ thiscve.vulnerability_details_cve_id }}

+

{{ thiscve.vulnerability_details.cve_id }}

  Read Advisory -  Updated: {{ thiscve.open_last_updated }} -

{{ thiscve.frontmatter_title }}

-
{{ thiscve.frontmatter_affectedProducts }}
+  Updated: {{ thiscve.open.last_updated }} +

{{ thiscve.frontmatter.title }}

+
{{ thiscve.frontmatter.affectedProducts }}
Summary:  -{{ thiscve.summary_0 }} +{{ thiscve.summary[0].replaceAll(r/`([^`]*)`/g,"$1") }}
Read More...
diff --git a/tools/automation/generators/advisoryindex/advisoryindex.js b/tools/automation/generators/advisoryindex/advisoryindex.js index 0f416ee08e3..34904088866 100755 --- a/tools/automation/generators/advisoryindex/advisoryindex.js +++ b/tools/automation/generators/advisoryindex/advisoryindex.js @@ -15,12 +15,13 @@ if (argv.root == undefined) { const securityRoot = argv.root; -let seccount=10; +let seccount = 10; if (argv.count != undefined) { - seccount=parseInt(argv.count); + seccount = parseInt(argv.count); } +const md = new MarkdownIt(); // We are going to process the advisories in const advisoriesDir = join(securityRoot, "advisories"); // To produce an index file named @@ -34,72 +35,50 @@ const templatesDir = join(securityRoot, "templates"); function parseMarkdownFile(filePath) { const fileContent = fs.readFileSync(filePath, 'utf8'); const parsedMatter = matter(fileContent); - - const sections = parsedMatter.content.split('\n#').slice(0); // split at headings - const sectionDicts = sections.map(section => { - const lines = section.split('\n'); - const heading = lines[0].replace('#', '').trim(); - const content = lines.slice(1); - var parsedContent = []; - content.forEach((line, index) => { - if (line !== '') { - if (line.startsWith('* [')) { - // This is a line with a link - // For now, we drop links completely - } else if (line.indexOf(':') > 0) { - const colon = line.indexOf(':'); - let key = line.slice(0, colon); - if (key.startsWith('* ')) { - key = key.slice(2); - } - const value = line.slice(colon + 1).trim(); - - parsedContent.push({ [slugify(key)]: value }); + const parsed = md.parse(parsedMatter.content, {}); + + let heading_capture = false; + let currentHeading = "open"; + let currentSectionMap = {} + let currentSectionArray = []; + + let docMap=parsed.reduce((currentValue, block) => { + if (block.type == "inline") { + if (heading_capture) { + currentHeading = slugify(block.content); + heading_capture=false; + } else { + let match = block.content.match("^([A-Za-z0-9- ]*): *(.*)$"); + if (match) { + let key = slugify(match[1]); + let value = match[2]; + currentSectionMap[key] = value; } else { - parsedContent.push(line); + currentSectionArray.push(block.content); } } - }); - - if (heading === '') { - return { ["open"]: parsedContent }; + } else if (block.type == "heading_open") { + if (currentSectionArray.length!=0) { + value=currentSectionArray; + currentSectionArray = []; + } else { + value=currentSectionMap; + currentSectionMap = {}; + } + heading_capture = true; + currentValue[currentHeading]=value; + } else if (block.type == "heading_close") { } - - return { [slugify(heading)]: parsedContent }; - }); - - let docMap = {} + return currentValue; + }, {}) // add the parsedMatter data to the docmap - Object.keys(parsedMatter.data).forEach(key => { - docMap["frontmatter_" + key] = parsedMatter.data[key]; - }); + docMap["frontmatter"]=parsedMatter.data; const path = basename(filePath, ".mdx"); docMap["filename"] = path; - // add the flattened sections to the docMap - sectionDicts.forEach(section => { - Object.keys(section).forEach(key => { - let value = section[key]; - if (Array.isArray(value)) { - for (let i = 0; i < value.length; i++) { - if (typeof value[i] === 'object') { - Object.keys(value[i]).forEach(subkey => { - docMap[key + '_' + subkey] = value[i][subkey]; - }) - } else { - docMap[key + '_' + i] = value[i]; - } - } - value = value.join('\n'); - } else { - docMap[key] = value; - } - }) - });; - return docMap; } @@ -113,11 +92,11 @@ function slugify(string) { ; } -function cleanCVE(string) { - if (string[0] == "[") { - return string.slice(1, string.indexOf("]", 1)); +function cleanCVE(cvestring) { + if (cvestring[0] == "[") { + return cvestring.slice(1, cvestring.indexOf("]", 1)); } - return string; + return cvestring; } // Iterate over all the files that start cve and end with mdx in the source directory, and parse them @@ -135,10 +114,10 @@ let allDocMap = {}; cvelist.forEach(cve => { const docMap = parseMarkdownFile(join(advisoriesDir, cve + '.mdx')); - // make sure the cve id isn't a link - docMap['vulnerability_details_cve_id'] = cleanCVE(docMap['vulnerability_details_cve_id']); + // make sure the cve id isn't a link + docMap['vulnerability_details']['cve_id'] = cleanCVE(docMap['vulnerability_details']['cve_id']); // trim the cve id off the front of the title - docMap['frontmatter_title']=docMap['frontmatter_title'].slice(docMap['frontmatter_title'].indexOf(" - ")+3); + docMap['frontmatter']['title'] = docMap['frontmatter']['title'].slice(docMap['frontmatter']['title'].indexOf(" - ") + 3); allDocMap[cve] = docMap; }); @@ -148,10 +127,10 @@ let lastyear = ""; let count = 0; cvelist.forEach(cve => { const year = cve.substring(3, 7); - if (lastyear=="") { + if (lastyear == "") { count = 0; lastyear = year; - } else if (lastyear!=year) { + } else if (lastyear != year) { return; } if (count < seccount) { @@ -160,17 +139,18 @@ cvelist.forEach(cve => { } }); -namespace["shortcvelist"]= shortcvelist; +namespace["shortcvelist"] = shortcvelist; namespace["cvesorted"] = cvelist; namespace["cves"] = allDocMap; //console.log(JSON.stringify(namespace, null, 2)); + const res = njk.render("advisoriesindex.njs", namespace); fs.writeFileSync(advisoriesIndex, res); const res2 = njk.render("securityindex.njs", namespace); -fs.writeFileSync(securityIndex,res2); +fs.writeFileSync(securityIndex, res2); From 5cb7557e6c47cfa0c8c7aa569018e65e0abc96b1 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 13 Sep 2023 12:04:56 +0100 Subject: [PATCH 141/255] Switch to ESM, added default dir handling Signed-off-by: Dj Walker-Morgan --- .../generators/advisoryindex/advisoryindex.js | 43 +++++++++++-------- .../generators/advisoryindex/package.json | 1 + 2 files changed, 25 insertions(+), 19 deletions(-) diff --git a/tools/automation/generators/advisoryindex/advisoryindex.js b/tools/automation/generators/advisoryindex/advisoryindex.js index 34904088866..19ac1ff61b2 100755 --- a/tools/automation/generators/advisoryindex/advisoryindex.js +++ b/tools/automation/generators/advisoryindex/advisoryindex.js @@ -1,19 +1,23 @@ -const fs = require('fs'); -const matter = require('gray-matter'); -const MarkdownIt = require('markdown-it'); -const njk = require('nunjucks'); -const { basename, join } = require('path'); -const parseArgs = require('minimist'); -const { addAbortListener } = require('events'); +import fs from "fs"; +import matter from "gray-matter"; +import MarkdownIt from "markdown-it"; +import njk from "nunjucks"; +import path from 'path'; +import parseArgs from 'minimist'; +import { fileURLToPath } from 'url'; + +// Modules hack for dirname via https://flaviocopes.com/fix-dirname-not-defined-es-module-scope/ +const __filename = fileURLToPath(import.meta.url); +const __dirname = path.dirname(__filename); var argv = parseArgs(process.argv.slice(2)); -if (argv.root == undefined) { - console.log("Need --root"); - process.exit(1); -} +let securityRoot = argv.root; -const securityRoot = argv.root; +if (securityRoot == undefined) { + securityRoot=path.normalize(path.join(__dirname,"..","..","..","..","advocacy_docs","security")); + console.log(`Using ${securityRoot} as working directory`); +} let seccount = 10; @@ -23,14 +27,14 @@ if (argv.count != undefined) { const md = new MarkdownIt(); // We are going to process the advisories in -const advisoriesDir = join(securityRoot, "advisories"); +const advisoriesDir = path.join(securityRoot, "advisories"); // To produce an index file named -const advisoriesIndex = join(advisoriesDir, "index.mdx"); +const advisoriesIndex = path.join(advisoriesDir, "index.mdx"); // And another similar but shorted one named -const securityIndex = join(securityRoot, "index.mdx"); +const securityIndex = path.join(securityRoot, "index.mdx"); // Using templates in a directory called -const templatesDir = join(securityRoot, "templates"); +const templatesDir = path.join(securityRoot, "templates"); function parseMarkdownFile(filePath) { const fileContent = fs.readFileSync(filePath, 'utf8'); @@ -58,6 +62,7 @@ function parseMarkdownFile(filePath) { } } } else if (block.type == "heading_open") { + let value=""; if (currentSectionArray.length!=0) { value=currentSectionArray; currentSectionArray = []; @@ -75,9 +80,9 @@ function parseMarkdownFile(filePath) { // add the parsedMatter data to the docmap docMap["frontmatter"]=parsedMatter.data; - const path = basename(filePath, ".mdx"); + const cvepath = path.basename(filePath, ".mdx"); - docMap["filename"] = path; + docMap["filename"] = cvepath; return docMap; } @@ -113,7 +118,7 @@ let namespace = {}; let allDocMap = {}; cvelist.forEach(cve => { - const docMap = parseMarkdownFile(join(advisoriesDir, cve + '.mdx')); + const docMap = parseMarkdownFile(path.join(advisoriesDir, cve + '.mdx')); // make sure the cve id isn't a link docMap['vulnerability_details']['cve_id'] = cleanCVE(docMap['vulnerability_details']['cve_id']); // trim the cve id off the front of the title diff --git a/tools/automation/generators/advisoryindex/package.json b/tools/automation/generators/advisoryindex/package.json index f979649a8cc..44055582bd7 100755 --- a/tools/automation/generators/advisoryindex/package.json +++ b/tools/automation/generators/advisoryindex/package.json @@ -3,6 +3,7 @@ "version": "1.0.0", "description": "", "main": "advisoryindex.js", + "type": "module", "scripts": { "test": "echo \"Error: no test specified\" && exit 1" }, From ff1adb626ae433b59cd61d43d7177a88e6ee6143 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 21 Sep 2023 15:43:26 +0530 Subject: [PATCH 142/255] PEM - Added content as per PEM-4835 --- product_docs/docs/pem/9/troubleshooting.mdx | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/product_docs/docs/pem/9/troubleshooting.mdx b/product_docs/docs/pem/9/troubleshooting.mdx index 7e80f7a6d70..22f43f94b29 100644 --- a/product_docs/docs/pem/9/troubleshooting.mdx +++ b/product_docs/docs/pem/9/troubleshooting.mdx @@ -135,3 +135,15 @@ When connecting to a PostgreSQL server, you might get one of these error message For more information, see the PostgreSQL documentation about [client authentication](http://www.postgresql.org/docs/current/interactive/client-authentication.html). - **FATAL: password authentication failed**: The `password authentication failed for user` error message indicates there might be a problem with the password you entered. Retry the password to confirm you entered it correctly. If the error message returns, make sure that you have the correct password, that you are authorized to access the server, and that the access was correctly configured in the server's `postgresql.conf` configuration file. + +## PEM web server status check + +Run this command to check whether the PEM webserver is up and running: + +```shell +curl https://:8443/pem/misc/ping -k -i +__OUTPUT__ +PING +``` + +Where, `SERVER_ADDR` is the IP address of your PEM server. The output `PING` confirms the PEM web server is up and running. \ No newline at end of file From 7d690ee2e8a567a13549d7fdf00ab136e4c655d4 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Thu, 21 Sep 2023 09:00:19 +0100 Subject: [PATCH 143/255] Imported and rearranged sidebar Signed-off-by: Dj Walker-Morgan --- .../tpa/23/{reference => }/INSTALL-repo.mdx | 81 +++---- product_docs/docs/tpa/23/INSTALL.mdx | 2 +- .../docs/tpa/23/firstclusterdeployment.mdx | 222 ++++++++++++++++++ product_docs/docs/tpa/23/index.mdx | 3 + product_docs/docs/tpa/23/opensourcetpa.mdx | 32 +++ .../docs/tpa/23/reference/INSTALL-docker.mdx | 2 +- .../docs/tpa/23/reference/tpaexec-support.mdx | 4 +- .../docs/tpa/23/tpaexec-configure.mdx | 2 +- 8 files changed, 295 insertions(+), 53 deletions(-) rename product_docs/docs/tpa/23/{reference => }/INSTALL-repo.mdx (52%) create mode 100644 product_docs/docs/tpa/23/firstclusterdeployment.mdx create mode 100644 product_docs/docs/tpa/23/opensourcetpa.mdx diff --git a/product_docs/docs/tpa/23/reference/INSTALL-repo.mdx b/product_docs/docs/tpa/23/INSTALL-repo.mdx similarity index 52% rename from product_docs/docs/tpa/23/reference/INSTALL-repo.mdx rename to product_docs/docs/tpa/23/INSTALL-repo.mdx index 63d1b3f5010..28f1ac0ce2a 100644 --- a/product_docs/docs/tpa/23/reference/INSTALL-repo.mdx +++ b/product_docs/docs/tpa/23/INSTALL-repo.mdx @@ -1,4 +1,5 @@ --- +navTitle: Install from Source title: Installing TPA from source originalFilePath: INSTALL-repo.md @@ -9,78 +10,62 @@ repository. !!! Note - EDB customers must [install TPA from packages](../INSTALL/) in + EDB customers must [install TPA from packages](INSTALL/) in order to receive EDB support for the software. To run TPA from source, you must install all of the dependencies (e.g., Python 3.6+) that the packages would handle for you, or download -the source and [run TPA in a Docker container](INSTALL-docker/). +the source and [run TPA in a Docker container](reference/INSTALL-docker/). (Either way will work fine on Linux and macOS.) ## Quickstart -First, you must install the various dependencies that would have been -installed automatically along with the TPA packages. (You can use -something other than `sudo` to run these commands as root, if you -prefer.) +First, you must install the various dependencies Python 3, Python +venv, git, openvpn and patch. Installing from EDB repositories would +would install these automatically along with the TPA +packages. -```bash -# Debian or Ubuntu -$ sudo apt-get install python3 python3-pip python3-venv \ - git openvpn patch +Before you install TPA, you must install the required packages: -# RedHat, Rocky or AlmaLinux (python3 for RHEL7, python36 for RHEL8) -$ sudo yum install python36 python3-pip \ - epel-release git openvpn patch +- **Debian/Ubuntu**
`sudo apt-get install python3 python3-pip python3-venv git openvpn patch` +- **Redhat, Rocky or AlmaLinux (RHEL7)**
`sudo yum install python3 python3-pip epel-release git openvpn patch` +- **Redhat, Rocky or AlmaLinux (RHEL8)**
`sudo yum install python36 python3-pip epel-release git openvpn patch` -# MacOS X -$ brew tap discoteq/discoteq -$ brew install python@3 openvpn flock coreutils gpatch git -``` +## Clone and setup -Next, install TPA itself: +With prerequisites installed, you can now clone the repository. -```bash -$ git clone ssh://git@github.com/EnterpriseDB/tpa.git -$ ./tpa/bin/tpaexec setup -$ ./tpa/bin/tpaexec selftest ``` +git clone https://github.com/enterprisedb/tpa.git ~/tpa +``` + +This creates a `tpa` directory in your home directory. + +If you prefer to checkout with ssh use:
-## Step-by-step +``` +git clone ssh://git@github.com/EnterpriseDB/tpa.git ~/tpa +``` -Install the various dependencies as described above. +Add the bin directory, found within in your newly created clone, to your path with: -If your system does not have Python 3.6+ packages, you can use `pyenv` -to install a more recent Python in your home directory (see below), or -you can [run TPA in a Docker container](INSTALL-docker/). +`export PATH=$PATH:$HOME/tpa/bin` -Next, clone the TPA repository into, say, `~/tpa`. (It doesn't -matter where you put it, but don't use `/opt/EDB/TPA` or -`/opt/2ndQuadrant/TPA`, to avoid conflicts if you install the TPA -packages in future.) +Add this line to your `.bashrc` file (or other profile file for your preferred shell). -```bash -$ git clone ssh://git@github.com/EnterpriseDB/tpa.git ~/tpa -``` +You can now create a working tpa environment by running: -(If you're installing from source, please clone the repository instead -of downloading an archive of the source.) +`tpaexec setup` -The remaining steps are the same as if you had installed the package. +This will create the Python virtual environment that TPA will use in future. All needed packages are installed in this environment. To test this configured correctly, run the following: -```bash -# Add tpaexec to your PATH for convenience -# (Put this in your ~/.bashrc too) -$ export PATH=$PATH:$HOME/tpa/bin +`tpaexec selftest` -$ tpaexec setup -$ tpaexec selftest -``` +You now have tpaexec installed. -If the self-test completes without any errors, your TPA installation -is ready for use. +## Dependencies -## Python 3.6+ +### Python 3.6+ TPA requires Python 3.6 or later, available on most modern distributions. If you don't have it, you can use @@ -112,7 +97,7 @@ If you were not already using pyenv, please remember to add `pyenv` to your PATH in .bashrc and call `eval "$(pyenv init -)"` as described in the [pyenv documentation](https://github.com/pyenv/pyenv#installation). -## Virtual environment options +### Virtual environment options By default, `tpaexec setup` will use the builtin Python 3 `-m venv` to create a venv under `$TPA_DIR/tpa-venv`, and activate it diff --git a/product_docs/docs/tpa/23/INSTALL.mdx b/product_docs/docs/tpa/23/INSTALL.mdx index 6398a34f496..f7967e3f294 100644 --- a/product_docs/docs/tpa/23/INSTALL.mdx +++ b/product_docs/docs/tpa/23/INSTALL.mdx @@ -10,7 +10,7 @@ To use TPA, you need to install from packages or source and run the packages. If you have an EDB subscription plan, and therefore have access to the EDB repositories, you should follow these instructions. To install TPA from source, please refer to -[Installing TPA from Source](reference/INSTALL-repo/). +[Installing TPA from Source](INSTALL-repo/). See [Distribution support](reference/distributions/) for information on what platforms are supported. diff --git a/product_docs/docs/tpa/23/firstclusterdeployment.mdx b/product_docs/docs/tpa/23/firstclusterdeployment.mdx new file mode 100644 index 00000000000..3656599e79a --- /dev/null +++ b/product_docs/docs/tpa/23/firstclusterdeployment.mdx @@ -0,0 +1,222 @@ +--- +navTitle: Tutorial +title: A First Cluster Deployment +originalFilePath: firstclusterdeployment.md + +--- + +In this short tutorial, we are going to work through deploying a simple [M1 architecture](architecture-M1/) deployment onto a local Docker installation. By the end you will have four containers, one primary database, two replicas and a backup node, configured and ready for you to explore. + +For this example, we will run TPA on an Ubuntu system, but the considerations are similar for most Linux systems. + +### Installing TPA + +If you're an EDB customer, you'll want to follow the [EDB Repo instructions](INSTALL/) which will install the TPA packages straight from EDB's repositories. + +If you are an open source user of TPA, there's [instructions on how to build from the source](INSTALL-repo/) which you can download from Github.com. + +Follow those guides and then return here. + +### Installing Docker + +As we said, We are going to deploy the example deployment onto Docker and unless you already have Docker installed we'll need to set that up. + +On Debian or Ubuntu, install Docker by running: + +``` +sudo apt update +sudo apt install docker.io +``` + +For other Linux distributions, consult the [Docker Engine Install page](https://docs.docker.com/engine/install/). + +You will want to add your user to the docker group with: + +``` +sudo usermod -aG docker +newgrp docker +``` + +### CgroupVersion + +Currently, TPA requires Cgroups Version 1 be configured on your system, + +Run: + +``` +mount | grep cgroup | head -1 +``` + +and if you do not see a reference to `tmpfs` in the output, you'll need to disable cgroups v2. + +Run: + +``` +echo 'GRUB_CMDLINE_LINUX=systemd.unified_cgroup_hierarchy=false' | sudo tee /etc/default/grub.d/cgroup.cfg +``` + +To make the appropriate changes, then update Grub and reboot your system with: + +``` +sudo update-grub +sudo reboot +``` + +!!! Warning + + Giving a user the ability to speak to the Docker daemon + lets them trivially gain root on the Docker host. Only trusted users + should have access to the Docker daemon. + +### Creating a configuration with TPA + +The next step in this process is to create a configuration. TPA does most of the work for you through its `configure` command. All you have to do is supply command line flags and options to select, in broad terms, what you want to deploy. Here's our `tpaexec configure` command: + +``` +tpaexec configure demo --architecture M1 --platform docker --postgresql 15 --enable-repmgr --no-git +``` + +This creates a configuration called `demo` which has the [M1 architecture](architecture-M1/). It will therefore have a primary, replica and backup node. + +The `--platform docker` tells TPA that this configuration should be created on a local Docker instance; it will provision all the containers and OS requirements. Other platforms include [AWS](platform-aws), which does the same with Amazon Web Services and [Bare](platform-bare), which skips to operating system provisioning and goes straight to installing software on already configured Linux hosts. + +With `--postgresql 15`, we instruct TPA to use Community Postgres, version 15. There are several options here in terms of selecting software, but this is the most straightforward default for open-source users. + +Adding `--enable-repmgr` tells TPA to use configure the deployment to use [Replication Manager](https://www.repmgr.org/) to hand replication and failover. + +Finally, `--no-git` turns off the feature in TPA which allows you to revision control your configuration through git. + +Run this command, and apparently, nothing will happen on the command line. But you will find a directory called `demo` has been created containing some files including a `config.yml` file which is a blueprint for our new deployment. + +## Provisioning the deployment + +Now we are ready to create the containers (or virtual machines) on which we will run our new deployment. This can be achieved with the `provision` command. Run: + +``` +tpaexec provision demo +``` + +You will see TPA work through the various operations needed to prepare for deployment of your configuration. + +## Deploying + +Once provisioned, you can move on to deployment. This installs, if needed, operating systems and system packages. It then installs the requested Postgres architecture and performs all the needed configuration. + +``` +tpaexec deploy demo +``` + +You will see TPA work through the various operations needed to deploy your configuration. + +## Testing + +You can quickly test your newly deployed configuration using the tpaexec `test` command which will run pgbench on your new database. + +``` +tpaexec test demo +``` + +## Connecting + +To get to a psql prompt, the simplest route is to log into one of the containers (or VMs or host depending on configuration) using docker or SSH. Run + +``` +tpaexec ping demo +``` + +to ping all the connectable hosts in the deployment: You will get output that looks something like: + +``` +$ tpaexec ping demo +unfair | SUCCESS => { + "changed": false, + "ping": "pong" +} +uptake | SUCCESS => { + "changed": false, + "ping": "pong" +} +quondam | SUCCESS => { + "changed": false, + "ping": "pong" +} +uptight | SUCCESS => { + "changed": false, + "ping": "pong" +} +``` + +Select one of the nodes which responded with `SUCCESS`. We shall use `uptake` for this example. + +If you are only planning on using docker, use the command `docker exec -it uptake /bin/bash`, substituting in the appropriate hostname. + +Another option, that works with all types of TPA deployment is to use SSH. To do that, first change current directory to the created configuration directory. + +For example, our configuration is called demo, so we go to that directory. In there, we run `ssh -F ssh_config ourhostname` to connect. + +``` +cd demo +ssh -F ssh_config uptake +Last login: Wed Sep 6 10:08:01 2023 from 172.17.0.1 +[root@uptake ~]# +``` + +In both cases, you will be logged in as a root user on the container. + +We can now change user to the `postgres` user using `sudo -iu postgres`. As `postgres` we can run `psql`. TPA has already configured that user with a `.pgpass` file so there's no need to present a password. + +``` +[root@uptake ~]# +postgres@uptake:~ $ psql +psql (15.4) +Type "help" for help. + +postgres=# +``` + +And we are connected to our database. + +You can connect from the host system without SSHing into one of the containers. Obtain the IP address of the host you want to connect to from the `ssh_config` file. + +``` +$ grep "^ *Host" demo/ssh_config +Host * +Host uptight + HostName 172.17.0.9 +Host unfair + HostName 172.17.0.4 +Host quondam + HostName 172.17.0.10 +Host uptake + HostName 172.17.0.11 +``` + +We are going to connect to uptake, so the IP address is 172.17.0.11. + +You will also need to retrieve the password for the postgres user too. Run `tpaexec show-password demo postgres` to get the stored password from the system. + +``` +tpaexec show-password demo postgres +a9LmI1X^uMOpPoEnLuRdL%L$oRQak3om +``` + +Assuming you have a Postgresql client installed, you can then run: + +``` +psql --host 172.17.0.11 -U postgres +Password for user postgres: +``` + +Enter the password you previously retrieved. + +``` +psql (14.9 (Ubuntu 14.9-0ubuntu0.22.04.1), server 15.4) +WARNING: psql major version 14, server major version 15. + Some psql features might not work. +SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, bits: 256, compression: off) +Type "help" for help. + +postgres=# +``` + +You are now connected from the Docker host to Postgres running in one of the TPA deployed Docker containers. diff --git a/product_docs/docs/tpa/23/index.mdx b/product_docs/docs/tpa/23/index.mdx index f7dfb75ecfb..06019dc8b2b 100644 --- a/product_docs/docs/tpa/23/index.mdx +++ b/product_docs/docs/tpa/23/index.mdx @@ -3,7 +3,10 @@ navigation: - index - rel_notes - INSTALL + - opensourcetpa + - INSTALL-repo - '#Creating a cluster' + - firstclusterdeployment - tpaexec-configure - tpaexec-provision - tpaexec-deploy diff --git a/product_docs/docs/tpa/23/opensourcetpa.mdx b/product_docs/docs/tpa/23/opensourcetpa.mdx new file mode 100644 index 00000000000..831ed557ee5 --- /dev/null +++ b/product_docs/docs/tpa/23/opensourcetpa.mdx @@ -0,0 +1,32 @@ +--- +navTitle: Open Source +title: Open source TPA +originalFilePath: opensourcetpa.md + +--- + +## What is Trusted Postgres Architect (TPA)? + +TPA is an orchestration tool developed by [EnterpriseDB (EDB)](https://www.enterprisedb.com/) that uses Ansible to deploy Postgres clusters according to EDB's recommendations. + +TPA embodies the best practices followed by EDB, informed by many years of hard-earned experience with deploying and supporting Postgres. These recommendations are as applicable to quick testbed setups as to production environments. + +## Next Steps + +- [Installing TPA from Source](INSTALL-repo/) +- [Deploying your first cluster](firstclusterdeployment/) +- [TPA's full documentation online](https://www.enterprisedb.com/docs/tpa/latest/) + +## TPA Open Source FAQs + +### Can I use this if I'm not an EDB customer? + +Yes, TPA is an open source project under the GPLv3 license. It supports deploying clusters comprised of open source software, or EDB's proprietary products, or combinations. + +### Can I report an issue? + +Yes, if you're an EDB customer then please contact support. Otherwise please open a GitHub Issue. + +### Can I contribute? + +Sure, we'd love to hear from you but please open an issue before you start coding. We are quite selective with what TPA can/should do so bug fixes are more likely to get accepted than new features. diff --git a/product_docs/docs/tpa/23/reference/INSTALL-docker.mdx b/product_docs/docs/tpa/23/reference/INSTALL-docker.mdx index 34b1b2be4cd..c96498b79ba 100644 --- a/product_docs/docs/tpa/23/reference/INSTALL-docker.mdx +++ b/product_docs/docs/tpa/23/reference/INSTALL-docker.mdx @@ -6,7 +6,7 @@ originalFilePath: INSTALL-docker.md If you are using a system for which there are no [TPA packages](../INSTALL/) available, and it's difficult to run TPA after -[installing from source](INSTALL-repo/) (for example, because it's not +[installing from source](../INSTALL-repo/) (for example, because it's not easy to obtain a working Python 3.6+ interpreter), your last resort may be to build a Docker image and run TPA inside a Docker container. diff --git a/product_docs/docs/tpa/23/reference/tpaexec-support.mdx b/product_docs/docs/tpa/23/reference/tpaexec-support.mdx index 383ead3df73..196c050140f 100644 --- a/product_docs/docs/tpa/23/reference/tpaexec-support.mdx +++ b/product_docs/docs/tpa/23/reference/tpaexec-support.mdx @@ -11,9 +11,9 @@ originalFilePath: tpaexec-support.md TPA can install and configure the following major components. -- Postgres 15, 14, 13, 12, 11 +- Postgres 16, 15, 14, 13, 12, 11 -- EPAS (EDB Postgres Advanced Server) 15, 14, 13, 12 +- EPAS (EDB Postgres Advanced Server) 16, 15, 14, 13, 12 - PGD 5, 4, 3.7 diff --git a/product_docs/docs/tpa/23/tpaexec-configure.mdx b/product_docs/docs/tpa/23/tpaexec-configure.mdx index d1e72dd042d..df8b0027ba5 100644 --- a/product_docs/docs/tpa/23/tpaexec-configure.mdx +++ b/product_docs/docs/tpa/23/tpaexec-configure.mdx @@ -251,7 +251,7 @@ details. #### Postgres flavour and version TPA supports PostgreSQL, EDB Postgres Extended, and EDB Postgres -Advanced Server (EPAS) versions 11 through 15. +Advanced Server (EPAS) versions 11 through 16. You must specify both the flavour (or distribution) and major version of Postgres to install, for example: From a72c3ba842572d033823b6ec84f77886bea28987 Mon Sep 17 00:00:00 2001 From: Simon Notley <43099400+sonotley@users.noreply.github.com> Date: Thu, 21 Sep 2023 15:12:23 +0100 Subject: [PATCH 144/255] TPA 23.23 rel notes --- product_docs/docs/tpa/23/rel_notes/index.mdx | 2 ++ .../tpa/23/rel_notes/tpa_23.23_rel_notes.mdx | 23 +++++++++++++++++++ 2 files changed, 25 insertions(+) create mode 100644 product_docs/docs/tpa/23/rel_notes/tpa_23.23_rel_notes.mdx diff --git a/product_docs/docs/tpa/23/rel_notes/index.mdx b/product_docs/docs/tpa/23/rel_notes/index.mdx index a0aad80b43e..3ac7cfb5b11 100644 --- a/product_docs/docs/tpa/23/rel_notes/index.mdx +++ b/product_docs/docs/tpa/23/rel_notes/index.mdx @@ -2,6 +2,7 @@ title: Trusted Postgres Architect release notes navTitle: "Release notes" navigation: + - tpa_23.23_rel_notes - tpa_23.22_rel_notes - tpa_23.21_rel_notes - tpa_23.20_rel_notes @@ -20,6 +21,7 @@ The Trusted Postgres Architect documentation describes the latest version of Tru | Version | Release date | | ---------------------------- | ------------ | +| [23.23](tpa_23.22_rel_notes) | 21 Sep 2023 | | [23.22](tpa_23.22_rel_notes) | 06 Sep 2023 | | [23.21](tpa_23.21_rel_notes) | 05 Sep 2023 | | [23.20](tpa_23.20_rel_notes) | 01 Aug 2023 | diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.23_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.23_rel_notes.mdx new file mode 100644 index 00000000000..14ea25356b6 --- /dev/null +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.23_rel_notes.mdx @@ -0,0 +1,23 @@ +--- +title: Trusted Postgres Architect 23.23 release notes +navTitle: "Version 23.23" +--- + +Released: 21 Sep 2023 + + +New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.23 include the following: + +| Type | Description | +| ---- |------------ | +| Enhancement | TPA now supports PostgreSQL 16. Please note, PostgreSQL 16 packages are not yet available in all supported repos, so not all configurations will work until this is the case. | +| Change | When Postgres 16 or above is selected, TPA will not add any 2ndQuadrant repos by default. TPA will explicitly set `tpa_2q_repositories: []` in this case. | +| Change | EFM is now configured to use JDK 11 by default on platforms where it is available. | +| Change | Where no EDB Repositories are use, TPA will not exclude any packages from PGDG (previously Barman and psycopg2 were excluded). | +| Change | Added package names for etcd and Patroni to support installation on SLES. | +| Bug Fix | Fixed an issue whereby Apache HTTPD service for PEM Server would not start on boot. | +| Bug Fix | Fixed an issue whereby pg_backup_api tests were run with incorrect permissions causing them to fail. | +| Bug Fix | Fixed an issue whereby Apache HTTPD service for pg_backup_api would not start on boot. | +| Bug Fix | Fixed an issue whereby `bdr.standby_slot_names` and `bdr.standby_slots_min_confirmed` checks used the incorrect schema on bdr3 clusters. | +| Bug Fix | Fixed an issue whereby configuration keys for extensions were passed to Patroni in the incorrect format, resulting in 'WARNING: Removing unexpected parameter'. | +| Bug Fix | Fixed an issue when using the intermediate base image option for `docker_images` whereby the resulting image name was incorrect. | \ No newline at end of file From aaa60ff969678aefd7ab457c35c4165299e2140b Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Thu, 21 Sep 2023 15:20:07 +0100 Subject: [PATCH 145/255] Update product_docs/docs/tpa/23/rel_notes/index.mdx --- product_docs/docs/tpa/23/rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/tpa/23/rel_notes/index.mdx b/product_docs/docs/tpa/23/rel_notes/index.mdx index 3ac7cfb5b11..c35d67d7f63 100644 --- a/product_docs/docs/tpa/23/rel_notes/index.mdx +++ b/product_docs/docs/tpa/23/rel_notes/index.mdx @@ -21,7 +21,7 @@ The Trusted Postgres Architect documentation describes the latest version of Tru | Version | Release date | | ---------------------------- | ------------ | -| [23.23](tpa_23.22_rel_notes) | 21 Sep 2023 | +| [23.23](tpa_23.23_rel_notes) | 21 Sep 2023 | | [23.22](tpa_23.22_rel_notes) | 06 Sep 2023 | | [23.21](tpa_23.21_rel_notes) | 05 Sep 2023 | | [23.20](tpa_23.20_rel_notes) | 01 Aug 2023 | From a3b838bd1f72be66fd93c5d2ad1ab0df0a523f10 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 25 Sep 2023 12:20:11 +0530 Subject: [PATCH 146/255] EPAS patch release --- .../epas_rel_notes/epas11_21_33_rel_notes.mdx | 15 +++++++++++++++ .../docs/epas/11/epas_rel_notes/index.mdx | 1 + .../epas_rel_notes/epas12_16_21_rel_notes.mdx | 15 +++++++++++++++ .../docs/epas/12/epas_rel_notes/index.mdx | 1 + .../epas_rel_notes/epas13_12_18_rel_notes.mdx | 15 +++++++++++++++ .../docs/epas/13/epas_rel_notes/index.mdx | 1 + .../14/epas_rel_notes/epas14_9_1_rel_notes.mdx | 16 ++++++++++++++++ .../docs/epas/14/epas_rel_notes/index.mdx | 1 + .../15/epas_rel_notes/epas15_4_1_rel_notes.mdx | 18 ++++++++++++++++++ .../docs/epas/15/epas_rel_notes/index.mdx | 1 + 10 files changed, 84 insertions(+) create mode 100644 product_docs/docs/epas/11/epas_rel_notes/epas11_21_33_rel_notes.mdx create mode 100644 product_docs/docs/epas/12/epas_rel_notes/epas12_16_21_rel_notes.mdx create mode 100644 product_docs/docs/epas/13/epas_rel_notes/epas13_12_18_rel_notes.mdx create mode 100644 product_docs/docs/epas/14/epas_rel_notes/epas14_9_1_rel_notes.mdx create mode 100644 product_docs/docs/epas/15/epas_rel_notes/epas15_4_1_rel_notes.mdx diff --git a/product_docs/docs/epas/11/epas_rel_notes/epas11_21_33_rel_notes.mdx b/product_docs/docs/epas/11/epas_rel_notes/epas11_21_33_rel_notes.mdx new file mode 100644 index 00000000000..f063770bf4e --- /dev/null +++ b/product_docs/docs/epas/11/epas_rel_notes/epas11_21_33_rel_notes.mdx @@ -0,0 +1,15 @@ +--- +title: "EDB Postgres Advanced Server 11.21.33 release notes" +navTitle: Version 11.21.33 +hideToC: true +--- + +Released: 22 Sep 2023 + +EDB Postgres Advanced Server 11.21.33 includes the following enhancements and bug fixes: + +| Type | Description | Addresses   | | +| ------------ | --------------------------------------------------------------------------------------------------- | --------------------- | --- | +| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB*Loader. | #91832 | | +| Bug fix | Fixed memory leak in sub-transaction with usage of EXCEPTION in package. | #94255 | | +| Bug fix | Fixed the cache lookup error for event triggers with proper initialization of the variables in SPL. | | | diff --git a/product_docs/docs/epas/11/epas_rel_notes/index.mdx b/product_docs/docs/epas/11/epas_rel_notes/index.mdx index b321278359f..7a1b8eb69de 100644 --- a/product_docs/docs/epas/11/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/11/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release Notes title: "EDB Postgres Advanced Server Release Notes" navigation: +- epas11_21_33_rel_notes - epas11_21_32_rel_notes - epas11_20_31_rel_notes - epas11_19_30_rel_notes diff --git a/product_docs/docs/epas/12/epas_rel_notes/epas12_16_21_rel_notes.mdx b/product_docs/docs/epas/12/epas_rel_notes/epas12_16_21_rel_notes.mdx new file mode 100644 index 00000000000..125288cdbce --- /dev/null +++ b/product_docs/docs/epas/12/epas_rel_notes/epas12_16_21_rel_notes.mdx @@ -0,0 +1,15 @@ +--- +title: "EDB Postgres Advanced Server 12.16.21 release notes" +navTitle: Version 12.16.21 +hideToC: true +--- + +Released: 22 Sep 2023 + +EDB Postgres Advanced Server 12.16.21 includes the following enhancements and bug fixes: + +| Type | Description | Addresses   | | +| ------------ | --------------------------------------------------------------------------------------------------- | --------------------- | --- | +| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB*Loader. | #91832 | | +| Bug fix | Fixed memory leak in sub-transaction with usage of EXCEPTION in package. | #94255 | | +| Bug fix | Fixed the cache lookup error for event triggers with proper initialization of the variables in SPL. | | | diff --git a/product_docs/docs/epas/12/epas_rel_notes/index.mdx b/product_docs/docs/epas/12/epas_rel_notes/index.mdx index 2c30ddf4612..296e0119a13 100644 --- a/product_docs/docs/epas/12/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/12/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release Notes title: "EDB Postgres Advanced Server Release Notes" navigation: +- epas12_16_21_rel_notes - epas12_16_20_rel_notes - epas12_15_19_rel_notes - epas12_14_18_rel_notes diff --git a/product_docs/docs/epas/13/epas_rel_notes/epas13_12_18_rel_notes.mdx b/product_docs/docs/epas/13/epas_rel_notes/epas13_12_18_rel_notes.mdx new file mode 100644 index 00000000000..3fe582a1d7d --- /dev/null +++ b/product_docs/docs/epas/13/epas_rel_notes/epas13_12_18_rel_notes.mdx @@ -0,0 +1,15 @@ +--- +title: "EDB Postgres Advanced Server 13.12.18 release notes" +navTitle: Version 13.12.18 +hideToC: true +--- + +Released: 22 Sep 2023 + +EDB Postgres Advanced Server 13.12.18 includes the following enhancements and bug fixes: + +| Type | Description | Addresses   | | +| ------------ | --------------------------------------------------------------------------------------------------- | --------------------- | --- | +| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB*Loader. | #91832 | | +| Bug fix | Fixed memory leak in sub-transaction with usage of EXCEPTION in package. | #94255 | | +| Bug fix | Fixed the cache lookup error for event triggers with proper initialization of the variables in SPL. | | | diff --git a/product_docs/docs/epas/13/epas_rel_notes/index.mdx b/product_docs/docs/epas/13/epas_rel_notes/index.mdx index e0a3eb281bd..5030959fed5 100644 --- a/product_docs/docs/epas/13/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/13/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release Notes title: "EDB Postgres Advanced Server Release Notes" navigation: +- epas13_12_18_rel_notes - epas13_12_17_rel_notes - epas13_11_15_rel_notes - epas13_10_14_rel_notes diff --git a/product_docs/docs/epas/14/epas_rel_notes/epas14_9_1_rel_notes.mdx b/product_docs/docs/epas/14/epas_rel_notes/epas14_9_1_rel_notes.mdx new file mode 100644 index 00000000000..3c7b765c279 --- /dev/null +++ b/product_docs/docs/epas/14/epas_rel_notes/epas14_9_1_rel_notes.mdx @@ -0,0 +1,16 @@ +--- +title: "EDB Postgres Advanced Server 14.9.1 release notes" +navTitle: Version 14.9.1 +hideToC: true +--- + +Released: 22 Sep 2023 + +EDB Postgres Advanced Server 14.9.1 includes the following enhancements and bug fixes: + +| Type | Description | Addresses   | | +| ------------ | --------------------------------------------------------------------------------------------------- | --------------------- | --- | +| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB*Loader. | #91832 | | +| Bug fix | Fixed memory leak in sub-transaction with usage of EXCEPTION in package. | #94255 | | +| Bug fix | Fixed the cache lookup error for event triggers with proper initialization of the variables in SPL. | | | +| Bug fix | Fixed the buffer overrun hazard in EDB*Wrap code. | | | \ No newline at end of file diff --git a/product_docs/docs/epas/14/epas_rel_notes/index.mdx b/product_docs/docs/epas/14/epas_rel_notes/index.mdx index a11ad85cf6e..1068db90685 100644 --- a/product_docs/docs/epas/14/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/14/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release notes title: "EDB Postgres Advanced Server release notes" navigation: +- epas14_9_1_rel_notes - epas14_9_0_rel_notes - epas14_8_0_rel_notes - epas14_7_0_rel_notes diff --git a/product_docs/docs/epas/15/epas_rel_notes/epas15_4_1_rel_notes.mdx b/product_docs/docs/epas/15/epas_rel_notes/epas15_4_1_rel_notes.mdx new file mode 100644 index 00000000000..291f5f5a05a --- /dev/null +++ b/product_docs/docs/epas/15/epas_rel_notes/epas15_4_1_rel_notes.mdx @@ -0,0 +1,18 @@ +--- +title: "EDB Postgres Advanced Server 15.4.1 release notes" +navTitle: Version 15.4.1 +hideToC: true +--- + +Released: 22 Sep 2023 + +EDB Postgres Advanced Server 15.4.1 includes the following enhancements and bug fixes: + +| Type | Description | Addresses   | | +| ------------ | --------------------------------------------------------------------------------------------------- | --------------------- | --- | +| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB*Loader. | #91832 | | +| Bug fix | Fixed memory leak in sub-transaction with usage of EXCEPTION in package. | #94255 | | +| Bug fix | Fixed the cache lookup error for event triggers with proper initialization of the variables in SPL. | | | +| Bug fix | Fixed the buffer overrun hazard in EDB*Wrap code. | | | +| Bug fix | Fixed the function pg_get_expre() to avoid "unrecognized node type" error. | #96138 | | +| Bug fix | Fixed segment size handling for pg_upgrade with TDE. | #96376 | | diff --git a/product_docs/docs/epas/15/epas_rel_notes/index.mdx b/product_docs/docs/epas/15/epas_rel_notes/index.mdx index 6739f08a0e5..5a81098f5a0 100644 --- a/product_docs/docs/epas/15/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/15/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release notes title: "EDB Postgres Advanced Server release notes" navigation: +- epas15_4_1_rel_notes - epas15_4_0_rel_notes - epas15_3_0_rel_notes - epas15_2_0_rel_notes From 980e59ac46f27d79cb62c7634dc1d28d4d48457e Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 25 Sep 2023 16:10:27 +0530 Subject: [PATCH 147/255] EPAS - Patch release update --- .../docs/epas/11/epas_rel_notes/index.mdx | 51 ++++++++++--------- .../docs/epas/12/epas_rel_notes/index.mdx | 39 +++++++------- .../docs/epas/13/epas_rel_notes/index.mdx | 31 +++++------ .../docs/epas/14/epas_rel_notes/index.mdx | 23 +++++---- .../docs/epas/15/epas_rel_notes/index.mdx | 11 ++-- 5 files changed, 80 insertions(+), 75 deletions(-) diff --git a/product_docs/docs/epas/11/epas_rel_notes/index.mdx b/product_docs/docs/epas/11/epas_rel_notes/index.mdx index 7a1b8eb69de..55b932fecc1 100644 --- a/product_docs/docs/epas/11/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/11/epas_rel_notes/index.mdx @@ -23,28 +23,29 @@ EDB Postgres Advanced Server 11 is built on the open source PostgreSQL 11. EDB P The EDB Postgres Advanced Server (Advanced Server) documentation describes the latest version of Advanced Server 11 including minor releases and patches. The release notes in this section provide information on what was new in each release. -| Version | Release Date | Upstream Merge | -| ------- | ------------ | -------------- | -| [11.21.32](epas11_21_32_rel_notes.mdx) | 21 Aug 2023 | [11.21](https://www.postgresql.org/docs/11/release-11-21.html) | -| [11.20.31](epas11_20_31_rel_notes.mdx) | 11 May 2023 | [11.20](https://www.postgresql.org/docs/11/release-11-20.html) | -| [11.19.30](epas11_19_30_rel_notes.mdx) | 10 Feb 2023 | [11.19](https://www.postgresql.org/docs/11/release-11-19.html) | -| [11.18.29](epas11_18_29_rel_notes.mdx) | 10 Nov 2022 | [11.18](https://www.postgresql.org/docs/11/release-11-18.html) | -| [11.17.28](epas11_17_28_rel_notes.mdx) | 11 Aug 2022 | [11.17](https://www.postgresql.org/docs/11/release-11-17.html) | -| [11.16.26](epas11_16_26_rel_notes.mdx) | 12 May 2022 | [11.16](https://www.postgresql.org/docs/11/release-11-16.html) | -| [11.15.25](09_epas11.15.25_rel_notes.mdx) | 10 Feb 2022 | [11.15](https://www.postgresql.org/docs/11/release-11-15.html) | -| [11.14.24](10_epas11.14.24_rel_notes.mdx) | 11 Nov 2021| [11.14](https://www.postgresql.org/docs/11/release-11-14.html) | -| [11.13.23](11_epas11.13.23_rel_notes.mdx) | 08 Sep 2021| [11.13](https://www.postgresql.org/docs/11/release-11-13.html) | -| [11.12.22](13_epas11.12.22_rel_notes.mdx) | 05 May 2021| [11.12](https://www.postgresql.org/docs/11/release-11-12.html) | -| [11.12.21](15_epas11.12.21_rel_notes.mdx) | 15 Apr 2021| [11.12](https://www.postgresql.org/docs/11/release-11-12.html) | -| [11.11.20](17_epas11.11.20_rel_notes.mdx) | 12 Feb 2021| [11.11](https://www.postgresql.org/docs/11/release-11-11.html) | -| [11.10.19](19_epas11.10.19_rel_notes.mdx) | 20 Nov 2020| [11.10](https://www.postgresql.org/docs/11/release-11-10.html) | -| [11.9.17](21_epas11.9.17_rel_notes.mdx) | 18 Aug 2020| [11.9](https://www.postgresql.org/docs/11/release-11-9.html) | -| [11.9.16](23_epas11.9.16_rel_notes.mdx) | 17 Aug 2020| [11.9](https://www.postgresql.org/docs/11/release-11-9.html) | -| [11.8.15](25_epas11.8.15_rel_notes.mdx) | 18 May 2020| [11.8](https://www.postgresql.org/docs/11/release-11-8.html) | -| [11.7.14](27_epas11.7.14_rel_notes.mdx) | 14 Feb 2020| [11.7](https://www.postgresql.org/docs/11/release-11-7.html) | -| [11.6.13](29_epas11.6.13_rel_notes.mdx) | 19 Nov 2019| [11.6](https://www.postgresql.org/docs/11/release-11-6.html) | -| [11.5.12](31_epas11.5.12_rel_notes.mdx) | 26 Aug 2019| [11.5](https://www.postgresql.org/docs/11/release-11-5.html) | -| [11.4.11](33_epas11.4.11_rel_notes.mdx) | 25 Jun 2019| [11.4](https://www.postgresql.org/docs/11/release-11-4.html) | -| [11.3.10](35_epas11.3.10_rel_notes.mdx) | 13 May 2019| [11.3](https://www.postgresql.org/docs/11/release-11-3.html) | -| [11.2.9](37_epas11.2.9_rel_notes.mdx) | 22 Feb 2019| [11.2](https://www.postgresql.org/docs/11/release-11-2.html) | -| [11.1.7](39_epas11.1.7_rel_notes.mdx) | 28 Nov 2018| [11.1](https://www.postgresql.org/docs/11/release-11-1.html) | \ No newline at end of file +| Version | Release Date | Upstream Merge | +| ----------------------------------------- | ------------ | -------------------------------------------------------------- | +| [11.21.33](epas11_21_33_rel_notes.mdx) | 25 Sep 2023 | | +| [11.21.32](epas11_21_32_rel_notes.mdx) | 21 Aug 2023 | [11.21](https://www.postgresql.org/docs/11/release-11-21.html) | +| [11.20.31](epas11_20_31_rel_notes.mdx) | 11 May 2023 | [11.20](https://www.postgresql.org/docs/11/release-11-20.html) | +| [11.19.30](epas11_19_30_rel_notes.mdx) | 10 Feb 2023 | [11.19](https://www.postgresql.org/docs/11/release-11-19.html) | +| [11.18.29](epas11_18_29_rel_notes.mdx) | 10 Nov 2022 | [11.18](https://www.postgresql.org/docs/11/release-11-18.html) | +| [11.17.28](epas11_17_28_rel_notes.mdx) | 11 Aug 2022 | [11.17](https://www.postgresql.org/docs/11/release-11-17.html) | +| [11.16.26](epas11_16_26_rel_notes.mdx) | 12 May 2022 | [11.16](https://www.postgresql.org/docs/11/release-11-16.html) | +| [11.15.25](09_epas11.15.25_rel_notes.mdx) | 10 Feb 2022 | [11.15](https://www.postgresql.org/docs/11/release-11-15.html) | +| [11.14.24](10_epas11.14.24_rel_notes.mdx) | 11 Nov 2021 | [11.14](https://www.postgresql.org/docs/11/release-11-14.html) | +| [11.13.23](11_epas11.13.23_rel_notes.mdx) | 08 Sep 2021 | [11.13](https://www.postgresql.org/docs/11/release-11-13.html) | +| [11.12.22](13_epas11.12.22_rel_notes.mdx) | 05 May 2021 | [11.12](https://www.postgresql.org/docs/11/release-11-12.html) | +| [11.12.21](15_epas11.12.21_rel_notes.mdx) | 15 Apr 2021 | [11.12](https://www.postgresql.org/docs/11/release-11-12.html) | +| [11.11.20](17_epas11.11.20_rel_notes.mdx) | 12 Feb 2021 | [11.11](https://www.postgresql.org/docs/11/release-11-11.html) | +| [11.10.19](19_epas11.10.19_rel_notes.mdx) | 20 Nov 2020 | [11.10](https://www.postgresql.org/docs/11/release-11-10.html) | +| [11.9.17](21_epas11.9.17_rel_notes.mdx) | 18 Aug 2020 | [11.9](https://www.postgresql.org/docs/11/release-11-9.html) | +| [11.9.16](23_epas11.9.16_rel_notes.mdx) | 17 Aug 2020 | [11.9](https://www.postgresql.org/docs/11/release-11-9.html) | +| [11.8.15](25_epas11.8.15_rel_notes.mdx) | 18 May 2020 | [11.8](https://www.postgresql.org/docs/11/release-11-8.html) | +| [11.7.14](27_epas11.7.14_rel_notes.mdx) | 14 Feb 2020 | [11.7](https://www.postgresql.org/docs/11/release-11-7.html) | +| [11.6.13](29_epas11.6.13_rel_notes.mdx) | 19 Nov 2019 | [11.6](https://www.postgresql.org/docs/11/release-11-6.html) | +| [11.5.12](31_epas11.5.12_rel_notes.mdx) | 26 Aug 2019 | [11.5](https://www.postgresql.org/docs/11/release-11-5.html) | +| [11.4.11](33_epas11.4.11_rel_notes.mdx) | 25 Jun 2019 | [11.4](https://www.postgresql.org/docs/11/release-11-4.html) | +| [11.3.10](35_epas11.3.10_rel_notes.mdx) | 13 May 2019 | [11.3](https://www.postgresql.org/docs/11/release-11-3.html) | +| [11.2.9](37_epas11.2.9_rel_notes.mdx) | 22 Feb 2019 | [11.2](https://www.postgresql.org/docs/11/release-11-2.html) | +| [11.1.7](39_epas11.1.7_rel_notes.mdx) | 28 Nov 2018 | [11.1](https://www.postgresql.org/docs/11/release-11-1.html) | \ No newline at end of file diff --git a/product_docs/docs/epas/12/epas_rel_notes/index.mdx b/product_docs/docs/epas/12/epas_rel_notes/index.mdx index 296e0119a13..1575946a373 100644 --- a/product_docs/docs/epas/12/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/12/epas_rel_notes/index.mdx @@ -26,22 +26,23 @@ EDB Postgres Advanced Server 12 adds a number of new outstanding features, inclu The EDB Postgres Advanced Server (Advanced Server) documentation describes the latest version of Advanced Server 12 including minor releases and patches. The release notes in this section provide information on what was new in each release. -| Version | Release Date | Upstream Merges | -| ------- | ------------ | --------------- | -| [12.16.20](epas12_16_20_rel_notes.mdx) | 21 Aug 2023 | [12.16](https://www.postgresql.org/docs/12/release-12-16.html) -| [12.15.19](epas12_15_19_rel_notes.mdx) | 11 May 2023 | [12.15](https://www.postgresql.org/docs/12/release-12-15.html) | -| [12.14.18](epas12_14_18_rel_notes.mdx) | 10 Feb 2023 | [12.14](https://www.postgresql.org/docs/12/release-12-14.html) | -| [12.13.17](epas12_13_17_rel_notes.mdx) | 10 Nov 2022 | [12.13](https://www.postgresql.org/docs/12/release-12-13.html) | -| [12.12.16](epas12_12_16_rel_notes.mdx) | 11 Aug 2022 | [12.12](https://www.postgresql.org/docs/12/release-12-12.html) | -| [12.11.15](epas12_11_15_rel_notes.mdx) | 12 May 2022 | [12.11](https://www.postgresql.org/docs/12/release-12-11.html) | -| [12.10.14](05_epas12.10.14_rel_notes.mdx) | 10 Feb 2022 | [12.10](https://www.postgresql.org/docs/12/release-12-10.html) | | [12.10.14](05_epas12.10.14_rel_notes.mdx) | 10 Feb 2022 | [12.10](https://www.postgresql.org/docs/12/release-12-10.html) | -| [12.9.13](06_epas12.9.13_rel_notes.mdx) | 11 Nov 2021| [12.9](https://www.postgresql.org/docs/12/release-12-9.html) | -| [12.8.12](07_epas12.8.12_rel_notes.mdx) | 28 Sep 2021| [12.8](https://www.postgresql.org/docs/12/release-12-8.html) | -| [12.7.10](08_epas12.7.10_rel_notes.mdx) | 25 May 2021| [12.7](https://www.postgresql.org/docs/12/release-12-7.html) | -| [12.7](09_epas12.7_rel_notes.mdx) | 14 May 2021| [12.7](https://www.postgresql.org/docs/12/release-12-7.html) | -| [12.6.7](10_epas12.6.7_rel_notes.mdx) | 12 Feb 2021| [12.6](https://www.postgresql.org/docs/12/release-12-6.html) | -| [12.5.6](11_epas12.5.6_rel_notes.mdx) | 20 Nov 2020| [12.5](https://www.postgresql.org/docs/12/release-12-5.html) | -| [12.4.5](13_epas12.4.5_rel_notes.mdx) | 17 Aug 2020| [12.4](https://www.postgresql.org/docs/12/release-12-4.html) | -| [12.3.4](15_epas12.3.4_rel_notes.mdx) | 18 May 2020| [12.3](https://www.postgresql.org/docs/12/release-12-3.html) | -| [12.2.3](17_epas12.2.3_rel_notes.mdx) | 14 Feb 2020| [12.2](https://www.postgresql.org/docs/12/release-12-2.html) | -| [12.1.2](19_epas12.1.2_rel_notes.mdx) | 10 Dec 2019| [12.0](https://www.postgresql.org/docs/12/release-12.html) | \ No newline at end of file +| Version | Release Date | Upstream Merges | +| ----------------------------------------- | ------------ | -------------------------------------------------------------- | +| [12.16.21](epas12_16_21_rel_notes.mdx) | 25 Sep 2023 | | +| [12.16.20](epas12_16_20_rel_notes.mdx) | 21 Aug 2023 | [12.16](https://www.postgresql.org/docs/12/release-12-16.html) | +| [12.15.19](epas12_15_19_rel_notes.mdx) | 11 May 2023 | [12.15](https://www.postgresql.org/docs/12/release-12-15.html) | +| [12.14.18](epas12_14_18_rel_notes.mdx) | 10 Feb 2023 | [12.14](https://www.postgresql.org/docs/12/release-12-14.html) | +| [12.13.17](epas12_13_17_rel_notes.mdx) | 10 Nov 2022 | [12.13](https://www.postgresql.org/docs/12/release-12-13.html) | +| [12.12.16](epas12_12_16_rel_notes.mdx) | 11 Aug 2022 | [12.12](https://www.postgresql.org/docs/12/release-12-12.html) | +| [12.11.15](epas12_11_15_rel_notes.mdx) | 12 May 2022 | [12.11](https://www.postgresql.org/docs/12/release-12-11.html) | +| [12.10.14](05_epas12.10.14_rel_notes.mdx) | 10 Feb 2022 | [12.10](https://www.postgresql.org/docs/12/release-12-10.html) | +| [12.9.13](06_epas12.9.13_rel_notes.mdx) | 11 Nov 2021 | [12.9](https://www.postgresql.org/docs/12/release-12-9.html) | +| [12.8.12](07_epas12.8.12_rel_notes.mdx) | 28 Sep 2021 | [12.8](https://www.postgresql.org/docs/12/release-12-8.html) | +| [12.7.10](08_epas12.7.10_rel_notes.mdx) | 25 May 2021 | [12.7](https://www.postgresql.org/docs/12/release-12-7.html) | +| [12.7](09_epas12.7_rel_notes.mdx) | 14 May 2021 | [12.7](https://www.postgresql.org/docs/12/release-12-7.html) | +| [12.6.7](10_epas12.6.7_rel_notes.mdx) | 12 Feb 2021 | [12.6](https://www.postgresql.org/docs/12/release-12-6.html) | +| [12.5.6](11_epas12.5.6_rel_notes.mdx) | 20 Nov 2020 | [12.5](https://www.postgresql.org/docs/12/release-12-5.html) | +| [12.4.5](13_epas12.4.5_rel_notes.mdx) | 17 Aug 2020 | [12.4](https://www.postgresql.org/docs/12/release-12-4.html) | +| [12.3.4](15_epas12.3.4_rel_notes.mdx) | 18 May 2020 | [12.3](https://www.postgresql.org/docs/12/release-12-3.html) | +| [12.2.3](17_epas12.2.3_rel_notes.mdx) | 14 Feb 2020 | [12.2](https://www.postgresql.org/docs/12/release-12-2.html) | +| [12.1.2](19_epas12.1.2_rel_notes.mdx) | 10 Dec 2019 | [12.0](https://www.postgresql.org/docs/12/release-12.html) | \ No newline at end of file diff --git a/product_docs/docs/epas/13/epas_rel_notes/index.mdx b/product_docs/docs/epas/13/epas_rel_notes/index.mdx index 5030959fed5..e01a27636e7 100644 --- a/product_docs/docs/epas/13/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/13/epas_rel_notes/index.mdx @@ -19,18 +19,19 @@ EDB Postgres Advanced Server 13 is built on open-source PostgreSQL 13, which int The EDB Postgres Advanced Server (Advanced Server) documentation describes the latest version of Advanced Server 13 including minor releases and patches. The release notes in this section provide information on what was new in each release. -| Version | Release Date | Upstream Merges | -| ------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------- | -| [13.12.17](epas13_12_17_rel_notes) | 21 Aug 2023 | [13.12](https://www.postgresql.org/docs/release/13.12/) | -| [13.11.15](epas13_11_15_rel_notes) | 11 May 2023 | [13.11](https://www.postgresql.org/docs/release/13.11/) | -| [13.10.14](epas13_10_14_rel_notes) | 10 Feb 2023 | [13.10](https://www.postgresql.org/docs/release/13.10/) | -| [13.9.13](epas13_9_13_rel_notes) | 10 Nov 2022 | [13.9](https://www.postgresql.org/docs/release/13.9/) | -| [13.8.12](epas13_8_12_rel_notes) | 11 Aug 2022 | [13.8](https://www.postgresql.org/docs/release/13.8/) | -| [13.7.11](epas13_7_11_rel_notes) | 23 May 2022 | [13.7](https://www.postgresql.org/docs/release/13.7/) -| [13.6.10](13_epas13.6.10_rel_notes) | 10 Feb 2022 | [13.6](https://www.postgresql.org/docs/13/release-13-6.html) | -| [13.5.9](14_epas13.5.9_rel_notes) | 11 Nov 2021 | [13.5](https://www.postgresql.org/docs/13/release-13-5.html) | -| [13.4.8](15_epas13.4.8_rel_notes) | 28 Sep 2021 | [13.4](https://www.postgresql.org/docs/13/release-13-4.html) | -| [13.3.7](16_epas13.3.7_rel_notes) | 25 May 2021 | NA | -| [13.3.6](17_epas13.3.6_rel_notes) | 14 May 2021 | [13.3](https://www.postgresql.org/docs/13/release-13-3.html) | -| [13.2.5](19_epas13.2.5_rel_notes) | 02 Feb 2021 | [13.2](https://www.postgresql.org/docs/13/release-13-2.html) | -| [13.1.4](20_epas13_rel_notes) | 12 Dec 2020 | [13](https://www.postgresql.org/docs/13/release-13.html), [13.1](https://www.postgresql.org/docs/13/release-13-1.html) | \ No newline at end of file +| Version | Release Date | Upstream Merges | +| ----------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------------- | +| [13.12.18](epas13_12_17_rel_notes) | 25 Sep 2023 | | +| [13.12.17](epas13_12_17_rel_notes) | 21 Aug 2023 | [13.12](https://www.postgresql.org/docs/release/13.12/) | +| [13.11.15](epas13_11_15_rel_notes) | 11 May 2023 | [13.11](https://www.postgresql.org/docs/release/13.11/) | +| [13.10.14](epas13_10_14_rel_notes) | 10 Feb 2023 | [13.10](https://www.postgresql.org/docs/release/13.10/) | +| [13.9.13](epas13_9_13_rel_notes) | 10 Nov 2022 | [13.9](https://www.postgresql.org/docs/release/13.9/) | +| [13.8.12](epas13_8_12_rel_notes) | 11 Aug 2022 | [13.8](https://www.postgresql.org/docs/release/13.8/) | +| [13.7.11](epas13_7_11_rel_notes) | 23 May 2022 | [13.7](https://www.postgresql.org/docs/release/13.7/) | +| [13.6.10](13_epas13.6.10_rel_notes) | 10 Feb 2022 | [13.6](https://www.postgresql.org/docs/13/release-13-6.html) | +| [13.5.9](14_epas13.5.9_rel_notes) | 11 Nov 2021 | [13.5](https://www.postgresql.org/docs/13/release-13-5.html) | +| [13.4.8](15_epas13.4.8_rel_notes) | 28 Sep 2021 | [13.4](https://www.postgresql.org/docs/13/release-13-4.html) | +| [13.3.7](16_epas13.3.7_rel_notes) | 25 May 2021 | NA | +| [13.3.6](17_epas13.3.6_rel_notes) | 14 May 2021 | [13.3](https://www.postgresql.org/docs/13/release-13-3.html) | +| [13.2.5](19_epas13.2.5_rel_notes) | 02 Feb 2021 | [13.2](https://www.postgresql.org/docs/13/release-13-2.html) | +| [13.1.4](20_epas13_rel_notes) | 12 Dec 2020 | [13](https://www.postgresql.org/docs/13/release-13.html), [13.1](https://www.postgresql.org/docs/13/release-13-1.html) | \ No newline at end of file diff --git a/product_docs/docs/epas/14/epas_rel_notes/index.mdx b/product_docs/docs/epas/14/epas_rel_notes/index.mdx index 1068db90685..39941cf3e43 100644 --- a/product_docs/docs/epas/14/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/14/epas_rel_notes/index.mdx @@ -18,17 +18,18 @@ EDB Postgres Advanced Server 14 is built on open-source PostgreSQL 14, which int The EDB Postgres Advanced Server (EDB Postgres Advanced Server) documentation describes the latest version of EDB Postgres Advanced Server 14 including minor releases and patches. The release notes in this section provide information on what was new in each release. -| Version | Release date | Upstream merges | -| ------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------- | -| [14.9.0](epas14_9_0_rel_notes) | 21 Aug 2023 | [14.9](https://www.postgresql.org/docs/14/release-14-9.html) | -| [14.8.0](epas14_8_0_rel_notes) | 11 May 2023 | [14.8](https://www.postgresql.org/docs/14/release-14-8.html) | -| [14.7.0](epas14_7_0_rel_notes) | 10 Feb 2023 | [14.7](https://www.postgresql.org/docs/14/release-14-7.html) | -| [14.6.0](epas14_6_0_rel_notes) | 10 Nov 2022 | [14.6](https://www.postgresql.org/docs/14/release-14-6.html) | -| [14.5.0](epas14_5_0_rel_notes) | 11 Aug 2022 | [14.5](https://www.postgresql.org/docs/14/release-14-5.html) | -| [14.4.0](epas14_4_0_rel_notes) | 16 Jun 2022 | [14.4](https://www.postgresql.org/docs/14/release-14-4.html) | -| [14.3.0](epas14_3_0_rel_notes) | 12 May 2022 | [14.3](https://www.postgresql.org/docs/14/release-14-3.html) | -| [14.2.1](19_epas14.2.1_rel_notes) | 10 Feb 2022 | [14.2](https://www.postgresql.org/docs/14/release-14-2.html) | -| [14.1.0](20_epas14_rel_notes) | 01 Dec 2021 | [14.0](https://www.postgresql.org/docs/14/release-14.html), [14.1](https://www.postgresql.org/docs/14/release-14-1.html) | +| Version | Release date | Upstream merges | +| --------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------ | +| [14.9.1](epas14_9_1_rel_notes) | 25 Sep 2023 | | +| [14.9.0](epas14_9_0_rel_notes) | 21 Aug 2023 | [14.9](https://www.postgresql.org/docs/14/release-14-9.html) | +| [14.8.0](epas14_8_0_rel_notes) | 11 May 2023 | [14.8](https://www.postgresql.org/docs/14/release-14-8.html) | +| [14.7.0](epas14_7_0_rel_notes) | 10 Feb 2023 | [14.7](https://www.postgresql.org/docs/14/release-14-7.html) | +| [14.6.0](epas14_6_0_rel_notes) | 10 Nov 2022 | [14.6](https://www.postgresql.org/docs/14/release-14-6.html) | +| [14.5.0](epas14_5_0_rel_notes) | 11 Aug 2022 | [14.5](https://www.postgresql.org/docs/14/release-14-5.html) | +| [14.4.0](epas14_4_0_rel_notes) | 16 Jun 2022 | [14.4](https://www.postgresql.org/docs/14/release-14-4.html) | +| [14.3.0](epas14_3_0_rel_notes) | 12 May 2022 | [14.3](https://www.postgresql.org/docs/14/release-14-3.html) | +| [14.2.1](19_epas14.2.1_rel_notes) | 10 Feb 2022 | [14.2](https://www.postgresql.org/docs/14/release-14-2.html) | +| [14.1.0](20_epas14_rel_notes) | 01 Dec 2021 | [14.0](https://www.postgresql.org/docs/14/release-14.html), [14.1](https://www.postgresql.org/docs/14/release-14-1.html) | ## Support announcements diff --git a/product_docs/docs/epas/15/epas_rel_notes/index.mdx b/product_docs/docs/epas/15/epas_rel_notes/index.mdx index 5a81098f5a0..22493878768 100644 --- a/product_docs/docs/epas/15/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/15/epas_rel_notes/index.mdx @@ -12,11 +12,12 @@ EDB Postgres Advanced Server 15 is built on open-source PostgreSQL 15, which int The EDB Postgres Advanced Server documentation describes the latest version of EDB Postgres Advanced Server 15 including minor releases and patches. These release notes provide information on what was new in each release. -| Version | Release date | Upstream merges | -| ------------------------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [15.4.0](epas15_4_0_rel_notes) | 21 Aug 2023 | [15.4](https://www.postgresql.org/docs/release/15.4/) -| [15.3.0](epas15_3_0_rel_notes) | 11 May 2023 | [15.3](https://www.postgresql.org/docs/release/15.3/) | -| [15.2.0](epas15_2_0_rel_notes) | 14 Feb 2023 | [15.0](https://www.postgresql.org/docs/release/15.0/), [15.1](https://www.postgresql.org/docs/release/15.1/), [15.2](https://www.postgresql.org/docs/release/15.2/) | +| Version | Release date | Upstream merges | +| ------------------------------ | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [15.4.1](epas15_4_1_rel_notes) | 25 Sep 2023 | | +| [15.4.0](epas15_4_0_rel_notes) | 21 Aug 2023 | [15.4](https://www.postgresql.org/docs/release/15.4/) | +| [15.3.0](epas15_3_0_rel_notes) | 11 May 2023 | [15.3](https://www.postgresql.org/docs/release/15.3/) | +| [15.2.0](epas15_2_0_rel_notes) | 14 Feb 2023 | [15.0](https://www.postgresql.org/docs/release/15.0/), [15.1](https://www.postgresql.org/docs/release/15.1/), [15.2](https://www.postgresql.org/docs/release/15.2/) | ## Component certification From aeead8d684ce9a1ad65aef637ce326c8f8c2217f Mon Sep 17 00:00:00 2001 From: Jimmy Angelakos Date: Mon, 25 Sep 2023 12:51:42 +0100 Subject: [PATCH 148/255] Update 05_using_efm.mdx inserting newline because otherwise the formatting of the next line breaks --- product_docs/docs/efm/4/05_using_efm.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/product_docs/docs/efm/4/05_using_efm.mdx b/product_docs/docs/efm/4/05_using_efm.mdx index e12d056f786..360c2d49faf 100644 --- a/product_docs/docs/efm/4/05_using_efm.mdx +++ b/product_docs/docs/efm/4/05_using_efm.mdx @@ -169,6 +169,7 @@ To stop the Failover Manager agent on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLi Until you invoke the `efm disallow-node` command (removing the node's address from the Allowed Node host list), you can use the `service edb-efm-4. start` command to restart the node later without first running the `efm allow-node` command again. + Stopping an agent doesn't signal the cluster that the agent has failed unless the [primary.shutdown.as.failure](04_configuring_efm/01_cluster_properties/#primary_shutdown_as_failure) property is set to `true`. ### Stopping a Failover Manager cluster From e06f8b12726cf315213b592e7d4c831494eb41c3 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 25 Sep 2023 11:09:23 -0400 Subject: [PATCH 149/255] New style for release notes adding full title and date --- .../edb_plus/41/02_release_notes/edbplus_41.2_rel_notes.mdx | 5 ++++- .../docs/efm/4/efm_rel_notes/03_efm_47_rel_notes.mdx | 5 ++++- .../2/hadoop_rel_notes/hadoop_rel_notes_2.3.1.mdx | 5 ++++- .../42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes.mdx | 6 ++++-- product_docs/docs/livecompare/2/rel_notes/2.5_rel_notes.mdx | 5 ++++- .../4/01_mp_release_notes/mp_4.5.1_rel_notes.mdx | 5 ++++- .../55/mtk_rel_notes/mtk_5561_rel_notes.mdx | 3 ++- .../5/mongo_rel_notes/mongo5.5.1_rel_notes.mdx | 5 ++++- .../2/mysql_rel_notes/mysql2.9.1_rel_notes.mdx | 4 +++- .../15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx | 6 +++++- .../13/01_odbc_rel_notes/odbc_13.2.0.02_rel_notes.mdx | 5 ++++- product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx | 5 ++++- .../pgbouncer/1/pgbouncer_rel_notes/06_11900_rel_notes.mdx | 5 ++++- product_docs/docs/pgd/5/rel_notes/pgd_5.2.0_rel_notes.mdx | 4 +++- product_docs/docs/pge/15/release_notes/rel_notes15.4.mdx | 4 +++- .../docs/pgpool/4/pgpool_rel_notes/442_rel_notes.mdx | 4 +++- .../docs/postgis/3.2/01_release_notes/rel_notes321.mdx | 6 +++++- .../1/rel_notes/1_20_2_rel_notes.mdx | 2 ++ 18 files changed, 66 insertions(+), 18 deletions(-) diff --git a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.2_rel_notes.mdx b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.2_rel_notes.mdx index 701148a1e35..22dcfee2ef0 100644 --- a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.2_rel_notes.mdx +++ b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.2_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 41.2.0" +title: "EDB*Plus 41.2.0 release notes" +navTitle: Version 41.2.0 --- +Released: 23 Aug 2023 + New features, enhancements, bug fixes, and other changes in EDB\*Plus 41.2.0 include: | Type | Description | diff --git a/product_docs/docs/efm/4/efm_rel_notes/03_efm_47_rel_notes.mdx b/product_docs/docs/efm/4/efm_rel_notes/03_efm_47_rel_notes.mdx index 305ee44da66..d788214da54 100644 --- a/product_docs/docs/efm/4/efm_rel_notes/03_efm_47_rel_notes.mdx +++ b/product_docs/docs/efm/4/efm_rel_notes/03_efm_47_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 4.7" +title: "Failover Manager 4.7 release notes" +navTitle: Version 4.7 --- +Released: 20 Jun 2023 + Enhancements, bug fixes, and other changes in EFM 4.7 include: | Type | Description | diff --git a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.3.1.mdx b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.3.1.mdx index 8094257927e..9d4565fc96d 100644 --- a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.3.1.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.3.1.mdx @@ -1,7 +1,10 @@ --- -title: "Version 2.3.1" +title: "Hadoop Foreign Data Wrapper 2.3.1 release notes" +navTitle: Version 2.3.1 --- +Released: 20 Jul 2023 + Enhancements, bug fixes, and other changes in Hadoop Foreign Data Wrapper 2.3.1 include: | Type | Description | diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes.mdx index b133e234bad..7b50ffbaff7 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes.mdx @@ -1,8 +1,10 @@ --- -title: "Version 42.5.4.1" - +title: "EDB JDBC Connector 42.5.4.1 release notes" +navTitle: Version 42.5.4.1 --- +Released: 16 Mar 2023 + The EDB JDBC connector provides connectivity between a Java application and an EDB Postgres Advanced Server database. New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.5.4.1 include: diff --git a/product_docs/docs/livecompare/2/rel_notes/2.5_rel_notes.mdx b/product_docs/docs/livecompare/2/rel_notes/2.5_rel_notes.mdx index ac97a2f16e3..7b8a29223a7 100644 --- a/product_docs/docs/livecompare/2/rel_notes/2.5_rel_notes.mdx +++ b/product_docs/docs/livecompare/2/rel_notes/2.5_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 2.5" +title: "LiveCompare 2.5 release notes" +navTitle: Version 2.5 --- +Released: 09 May 2023 + LiveCompare 2.5 includes the following new features, enhancements, bug fixes, and other changes: | Type | Description | diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.1_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.1_rel_notes.mdx index d87b81e6040..497cf44d406 100644 --- a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.1_rel_notes.mdx +++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.1_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 4.5.1" +title: "Migration Portal 4.5.1 release notes" +navTitle: Version 4.5.1 --- +Released: 12 Jul 2023 + New features, enhancements, bug fixes, and other changes in Migration Portal 4.5.1 include the following: diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_5561_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_5561_rel_notes.mdx index 18bff63a20a..19561b998c9 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_5561_rel_notes.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_5561_rel_notes.mdx @@ -1,5 +1,6 @@ --- -title: "Version 55.6.1" +title: "Migration Toolkit 55.6.1 release notes" +navTitle: Version 55.6.1 --- Released: 06 Sep 2023 diff --git a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.5.1_rel_notes.mdx b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.5.1_rel_notes.mdx index aec83cd0cc8..cf183a1c833 100644 --- a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.5.1_rel_notes.mdx +++ b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.5.1_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 5.5.0" +title: "MongoDB Foreign Data Wrapper 5.5.1 release notes" +navTitle: Version 5.5.1 --- +Released: 20 Jul 2023 + Enhancements, bug fixes, and other changes in MongoDB Foreign Data Wrapper 5.5.0 include: diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.9.1_rel_notes.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.9.1_rel_notes.mdx index fab5abfd2ca..3ab050daab0 100644 --- a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.9.1_rel_notes.mdx +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.9.1_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 2.9.1" +title: "MySQL Foreign Data Wrapper 2.9.1 release notes" +navTitle: Version 2.9.1 --- +Released: 20 Jul 2023 Enhancements, bug fixes, and other changes in MySQL Foreign Data Wrapper 2.9.1 include: diff --git a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx index 8d7d07d7528..9559d58e38a 100644 --- a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx +++ b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.4_ocl_release_notes.mdx @@ -1,6 +1,10 @@ --- -title: "Version 15.2.0.4" +title: "EDB OCL Connector 15.2.0.4 release notes" +navTitle: Version 15.2.0.4 --- + +Released: 24 Aug 2023 + The EDB OCL Connector provides an API similar to the Oracle Call Interface. New features, enhancements, bug fixes, and other changes in the EDB OCL Connector 15.2.0.4 include: diff --git a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/odbc_13.2.0.02_rel_notes.mdx b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/odbc_13.2.0.02_rel_notes.mdx index 459e472283f..79aa0f0d4d1 100644 --- a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/odbc_13.2.0.02_rel_notes.mdx +++ b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/odbc_13.2.0.02_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 13.02.0000.02" +title: "EDB ODBC Connector 13.02.0000.02 release notes" +navTitle: Version 13.02.0000.02 --- +Released: 14 Feb 2023 + EDB ODBC Connector 13.02.0000.02 includes the following enhancement: | Type | Description | diff --git a/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx index 2d7a69d1158..ef0dbf8d0a5 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/930_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 9.3.0" +title: "Postgres Enterprise Manager 9.3.0 release notes" +navTitle: Version 9.3.0 --- +Released: 31 Aug 2023 + New features, enhancements, bug fixes, and other changes in PEM 9.3.0 include: | Type | Description | diff --git a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/06_11900_rel_notes.mdx b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/06_11900_rel_notes.mdx index 8628f8f1254..5ac825f3e9a 100644 --- a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/06_11900_rel_notes.mdx +++ b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/06_11900_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 1.19.0.0" +title: "EDB PgBouncer 1.19.0.0 release notes" +navTitle: Version 1.19.0.0 --- +Released: 07 Jun 2023 + EDB PgBouncer 1.19.0.0 includes the following upstream merge and security fix: | Type | Description | diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.2.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.2.0_rel_notes.mdx index 7ed48a0c20f..46a162b3572 100644 --- a/product_docs/docs/pgd/5/rel_notes/pgd_5.2.0_rel_notes.mdx +++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.2.0_rel_notes.mdx @@ -1,8 +1,10 @@ --- -title: "Release notes for EDB Postgres Distributed version 5.2.0" +title: "EDB Postgres Distributed 5.2.0 release notes" navTitle: "Version 5.2.0" --- +Released: 04 Aug 2023 + EDB Postgres Distributed version 5.2.0 is a minor version of EDB Postgres Distributed. ## Highlights of EDB Postgres Distributed 5.2 diff --git a/product_docs/docs/pge/15/release_notes/rel_notes15.4.mdx b/product_docs/docs/pge/15/release_notes/rel_notes15.4.mdx index f26c12e7833..c1a9b229e90 100644 --- a/product_docs/docs/pge/15/release_notes/rel_notes15.4.mdx +++ b/product_docs/docs/pge/15/release_notes/rel_notes15.4.mdx @@ -1,8 +1,10 @@ --- -title: "EDB Postgres Extended Server version 15.4" +title: "EDB Postgres Extended Server 15.4 release notes" navTitle: Version 15.4 --- +Released: 21 Aug 2023 + New features, enhancements, bug fixes, and other changes in EDB Postgres Extended Server 15.2 include: | Type | Description | diff --git a/product_docs/docs/pgpool/4/pgpool_rel_notes/442_rel_notes.mdx b/product_docs/docs/pgpool/4/pgpool_rel_notes/442_rel_notes.mdx index 4c32989e90c..3f5381509c3 100644 --- a/product_docs/docs/pgpool/4/pgpool_rel_notes/442_rel_notes.mdx +++ b/product_docs/docs/pgpool/4/pgpool_rel_notes/442_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 4.4.2" +title: "EDB PgPool-II 4.4.2 release notes" +navTitle: Version 4.4.2 --- +Released: 14 Feb 2023 EDB Pgpool-II 4.4.2 includes the following upstream merge: diff --git a/product_docs/docs/postgis/3.2/01_release_notes/rel_notes321.mdx b/product_docs/docs/postgis/3.2/01_release_notes/rel_notes321.mdx index 0bb1b1ccbb4..f0f2d886288 100644 --- a/product_docs/docs/postgis/3.2/01_release_notes/rel_notes321.mdx +++ b/product_docs/docs/postgis/3.2/01_release_notes/rel_notes321.mdx @@ -1,6 +1,10 @@ --- -title: "Version 3.2.1" +title: "PostGIS 3.2.1 release notes" +navTitle: Version 3.2.1 --- + +Released: 04 Aug 2022 + EDB PostGIS is a PostgreSQL extension that allows you to store geographic information systems (GIS) objects in an EDB Postgres Advanced Server database. New features, enhancements, bug fixes, and other changes in PostGIS 3.2.1 include: diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_20_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_20_2_rel_notes.mdx index 305d0cd0f6f..db055bed359 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_20_2_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_20_2_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.20.2 release notes" navTitle: "Version 1.20.2" --- +Released: 27 Jul 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | From 6925da49ef31b9d4f64d4bbfe5b3a45804c29513 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 26 Sep 2023 14:45:04 -0400 Subject: [PATCH 150/255] Fixed typo in PEM content --- product_docs/docs/pem/9/troubleshooting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/troubleshooting.mdx b/product_docs/docs/pem/9/troubleshooting.mdx index 22f43f94b29..fd40fa4aa91 100644 --- a/product_docs/docs/pem/9/troubleshooting.mdx +++ b/product_docs/docs/pem/9/troubleshooting.mdx @@ -146,4 +146,4 @@ __OUTPUT__ PING ``` -Where, `SERVER_ADDR` is the IP address of your PEM server. The output `PING` confirms the PEM web server is up and running. \ No newline at end of file +Where `SERVER_ADDR` is the IP address of your PEM server. The output `PING` confirms the PEM web server is up and running. \ No newline at end of file From be5eb0f11731db3250015dc60ca549bb53edd22a Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 26 Sep 2023 14:57:29 -0400 Subject: [PATCH 151/255] Added slash to EDB*Loader and EDB*Wrap Added where throughout doc as appropriate, plus the new release notes --- .../docs/epas/11/epas_rel_notes/epas11_21_33_rel_notes.mdx | 2 +- .../docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx | 4 ++-- .../docs/epas/12/epas_rel_notes/epas12_16_21_rel_notes.mdx | 2 +- .../docs/epas/13/epas_rel_notes/epas13_12_18_rel_notes.mdx | 2 +- .../docs/epas/14/epas_rel_notes/epas14_9_1_rel_notes.mdx | 4 ++-- .../docs/epas/15/epas_rel_notes/epas15_2_0_rel_notes.mdx | 4 ++-- .../docs/epas/15/epas_rel_notes/epas15_4_1_rel_notes.mdx | 4 ++-- .../database_administration_tools/09_tools_and_utilities.mdx | 4 ++-- .../database_administration_tools/edb_loader_overview.mdx | 2 +- .../epas/15/working_with_oracle_data/loading_bulk_data.mdx | 2 +- .../15/working_with_oracle_data/proprietary_source_code.mdx | 2 +- 11 files changed, 16 insertions(+), 16 deletions(-) diff --git a/product_docs/docs/epas/11/epas_rel_notes/epas11_21_33_rel_notes.mdx b/product_docs/docs/epas/11/epas_rel_notes/epas11_21_33_rel_notes.mdx index f063770bf4e..2fcc46dd017 100644 --- a/product_docs/docs/epas/11/epas_rel_notes/epas11_21_33_rel_notes.mdx +++ b/product_docs/docs/epas/11/epas_rel_notes/epas11_21_33_rel_notes.mdx @@ -10,6 +10,6 @@ EDB Postgres Advanced Server 11.21.33 includes the following enhancements and bu | Type | Description | Addresses   | | | ------------ | --------------------------------------------------------------------------------------------------- | --------------------- | --- | -| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB*Loader. | #91832 | | +| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB\*Loader. | #91832 | | | Bug fix | Fixed memory leak in sub-transaction with usage of EXCEPTION in package. | #94255 | | | Bug fix | Fixed the cache lookup error for event triggers with proper initialization of the variables in SPL. | | | diff --git a/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx b/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx index 1529dea519e..5fa9ae8922c 100644 --- a/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx +++ b/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx @@ -1,5 +1,5 @@ --- -title: "EDB*Loader" +title: "EDB\*Loader" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. @@ -447,7 +447,7 @@ ZONED EXTERNAL [()] | ZONED [([,])] **Note**: If the `DATE` or `TIMESTAMP` field type is specified along with a SQL expression for the column, then `datemask` must be specified after `DATE` or `TIMESTAMP` and before the SQL expression. See the following discussion of the `expr` parameter. - When using the `TIMESTAMP` field datatype, if you specify `time_stamp timestamp "yyyymmddhh24miss"` the `datemask` is converted to the SQL expression. However, in case of `time_stamp timestamp "select to_timestamp(:time_stamp, 'yyyymmddhh24miss')"`, the EDB*Loader cannot differentiate between datemask and the SQL expression. It treats the third field (SQL expression in the example) as datemask and prepares the SQL expression, which will not be valid. Where: + When using the `TIMESTAMP` field datatype, if you specify `time_stamp timestamp "yyyymmddhh24miss"` the `datemask` is converted to the SQL expression. However, in case of `time_stamp timestamp "select to_timestamp(:time_stamp, 'yyyymmddhh24miss')"`, the EDB\*Loader cannot differentiate between datemask and the SQL expression. It treats the third field (SQL expression in the example) as datemask and prepares the SQL expression, which will not be valid. Where: - `first field` specifies the column name - `second field` specifies the datatype diff --git a/product_docs/docs/epas/12/epas_rel_notes/epas12_16_21_rel_notes.mdx b/product_docs/docs/epas/12/epas_rel_notes/epas12_16_21_rel_notes.mdx index 125288cdbce..8015feb7fc7 100644 --- a/product_docs/docs/epas/12/epas_rel_notes/epas12_16_21_rel_notes.mdx +++ b/product_docs/docs/epas/12/epas_rel_notes/epas12_16_21_rel_notes.mdx @@ -10,6 +10,6 @@ EDB Postgres Advanced Server 12.16.21 includes the following enhancements and bu | Type | Description | Addresses   | | | ------------ | --------------------------------------------------------------------------------------------------- | --------------------- | --- | -| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB*Loader. | #91832 | | +| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB\*Loader. | #91832 | | | Bug fix | Fixed memory leak in sub-transaction with usage of EXCEPTION in package. | #94255 | | | Bug fix | Fixed the cache lookup error for event triggers with proper initialization of the variables in SPL. | | | diff --git a/product_docs/docs/epas/13/epas_rel_notes/epas13_12_18_rel_notes.mdx b/product_docs/docs/epas/13/epas_rel_notes/epas13_12_18_rel_notes.mdx index 3fe582a1d7d..017a199cc02 100644 --- a/product_docs/docs/epas/13/epas_rel_notes/epas13_12_18_rel_notes.mdx +++ b/product_docs/docs/epas/13/epas_rel_notes/epas13_12_18_rel_notes.mdx @@ -10,6 +10,6 @@ EDB Postgres Advanced Server 13.12.18 includes the following enhancements and bu | Type | Description | Addresses   | | | ------------ | --------------------------------------------------------------------------------------------------- | --------------------- | --- | -| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB*Loader. | #91832 | | +| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB\*Loader. | #91832 | | | Bug fix | Fixed memory leak in sub-transaction with usage of EXCEPTION in package. | #94255 | | | Bug fix | Fixed the cache lookup error for event triggers with proper initialization of the variables in SPL. | | | diff --git a/product_docs/docs/epas/14/epas_rel_notes/epas14_9_1_rel_notes.mdx b/product_docs/docs/epas/14/epas_rel_notes/epas14_9_1_rel_notes.mdx index 3c7b765c279..5ef2e1712e9 100644 --- a/product_docs/docs/epas/14/epas_rel_notes/epas14_9_1_rel_notes.mdx +++ b/product_docs/docs/epas/14/epas_rel_notes/epas14_9_1_rel_notes.mdx @@ -10,7 +10,7 @@ EDB Postgres Advanced Server 14.9.1 includes the following enhancements and bug | Type | Description | Addresses   | | | ------------ | --------------------------------------------------------------------------------------------------- | --------------------- | --- | -| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB*Loader. | #91832 | | +| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB\*Loader. | #91832 | | | Bug fix | Fixed memory leak in sub-transaction with usage of EXCEPTION in package. | #94255 | | | Bug fix | Fixed the cache lookup error for event triggers with proper initialization of the variables in SPL. | | | -| Bug fix | Fixed the buffer overrun hazard in EDB*Wrap code. | | | \ No newline at end of file +| Bug fix | Fixed the buffer overrun hazard in EDB\*Wrap code. | | | \ No newline at end of file diff --git a/product_docs/docs/epas/15/epas_rel_notes/epas15_2_0_rel_notes.mdx b/product_docs/docs/epas/15/epas_rel_notes/epas15_2_0_rel_notes.mdx index 402c04ce197..18564da0f65 100644 --- a/product_docs/docs/epas/15/epas_rel_notes/epas15_2_0_rel_notes.mdx +++ b/product_docs/docs/epas/15/epas_rel_notes/epas15_2_0_rel_notes.mdx @@ -11,8 +11,8 @@ EDB Postgres Advanced Server 15.2.0 includes the following enhancements and bug | -------------- | -------------------------------------------------------------------------------------------------------------------------------------| --------------------- | | Upstream merge | Merged with community PostgreSQL 15.2. See the [PostgreSQL 15 Release Notes](https://www.postgresql.org/docs/15/release-15.html) for more information. | | | Feature | Transparent Data Encryption (TDE) encrypts any user data stored in the database system. This encryption is transparent to the user. User data includes the actual data stored in tables and other objects, as well as system catalog data such as the names of objects. See [TDE docs](/tde/latest) for more information. | Security | -| Enhancement | EDB Postgres Advanced Server now allows non-superusers to load data using EDB*Loader. | edbldr | -| Enhancement | Enabled multi-insert support for the dynamic partition for EDB*Loader and COPY command. | | +| Enhancement | EDB Postgres Advanced Server now allows non-superusers to load data using EDB\*Loader. | edbldr | +| Enhancement | Enabled multi-insert support for the dynamic partition for EDB\*Loader and COPY command. | | | Enhancement | EDB Postgres Advanced Server now lets you obfuscate the LDAP password in the `pg_hba.conf` file. You can supply a module that transforms the `ldapbindpasswd` value in the `pg_hba.conf` file before the value is passed to the LDAP server. See [Obfuscating the LDAP password](../database_administration/01_configuration_parameters/01_setting_new_parameters/#obfuscating-the-ldap-password). | Security | | Enhancement | Added OCI dblink configuration file approach to restrict pushdowns. This enhancement adds the infrastructure to the configuration file in which you can define the list of operators and functions that can push down to the remote server. It also allows you to add to or modify the list as needed. | | | Enhancement | Added support for WHERE clause to the UPDATE and INSERT of MERGE command for Oracle compatibility.| Oracle compatibility | diff --git a/product_docs/docs/epas/15/epas_rel_notes/epas15_4_1_rel_notes.mdx b/product_docs/docs/epas/15/epas_rel_notes/epas15_4_1_rel_notes.mdx index 291f5f5a05a..888eaa41db5 100644 --- a/product_docs/docs/epas/15/epas_rel_notes/epas15_4_1_rel_notes.mdx +++ b/product_docs/docs/epas/15/epas_rel_notes/epas15_4_1_rel_notes.mdx @@ -10,9 +10,9 @@ EDB Postgres Advanced Server 15.4.1 includes the following enhancements and bug | Type | Description | Addresses   | | | ------------ | --------------------------------------------------------------------------------------------------- | --------------------- | --- | -| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB*Loader. | #91832 | | +| Bug fix | Hexadecimal values are now allowed as record and field delimiter in EDB\*Loader. | #91832 | | | Bug fix | Fixed memory leak in sub-transaction with usage of EXCEPTION in package. | #94255 | | | Bug fix | Fixed the cache lookup error for event triggers with proper initialization of the variables in SPL. | | | -| Bug fix | Fixed the buffer overrun hazard in EDB*Wrap code. | | | +| Bug fix | Fixed the buffer overrun hazard in EDB\*Wrap code. | | | | Bug fix | Fixed the function pg_get_expre() to avoid "unrecognized node type" error. | #96138 | | | Bug fix | Fixed segment size handling for pg_upgrade with TDE. | #96376 | | diff --git a/product_docs/docs/epas/15/tools_utilities_and_components/database_administration_tools/09_tools_and_utilities.mdx b/product_docs/docs/epas/15/tools_utilities_and_components/database_administration_tools/09_tools_and_utilities.mdx index 4c115d0a04a..55745a0d639 100644 --- a/product_docs/docs/epas/15/tools_utilities_and_components/database_administration_tools/09_tools_and_utilities.mdx +++ b/product_docs/docs/epas/15/tools_utilities_and_components/database_administration_tools/09_tools_and_utilities.mdx @@ -13,6 +13,6 @@ redirects: Oracle-compatible tools and utility programs allow you to work with EDB Postgres Advanced Server in a familiar environment. The tools supported by EDB Postgres Advanced Server include: - [EDB\*Plus](https://www.enterprisedb.com/docs/edb_plus/latest/) -- [EDB*Loader](../../database_administration/02_edb_loader/) -- [EDB*Wrap](../../epas_security_guide/03_edb_wrap/) +- [EDB\*Loader](../../database_administration/02_edb_loader/) +- [EDB\*Wrap](../../epas_security_guide/03_edb_wrap/) - [The Dynamic Runtime Instrumentation Tools Architecture (DRITA)](../../managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/) diff --git a/product_docs/docs/epas/15/tools_utilities_and_components/database_administration_tools/edb_loader_overview.mdx b/product_docs/docs/epas/15/tools_utilities_and_components/database_administration_tools/edb_loader_overview.mdx index 68c0af4fb35..873ddc56b72 100644 --- a/product_docs/docs/epas/15/tools_utilities_and_components/database_administration_tools/edb_loader_overview.mdx +++ b/product_docs/docs/epas/15/tools_utilities_and_components/database_administration_tools/edb_loader_overview.mdx @@ -3,6 +3,6 @@ title: "EDB*Loader" description: "Provides an overview of the EDB*Loader high-performance bulk data loader" --- -EDB*Loader is a high-performance bulk data loader that provides an interface compatible with Oracle databases for EDB Postgres Advanced Server. The EDB*Loader command line utility loads data from an input source, typically a file, into one or more tables using a subset of the parameters offered by Oracle SQL*Loader. +EDB\*Loader is a high-performance bulk data loader that provides an interface compatible with Oracle databases for EDB Postgres Advanced Server. The EDB*Loader command line utility loads data from an input source, typically a file, into one or more tables using a subset of the parameters offered by Oracle SQL*Loader. For details about using the tool, see [Loading bulk data](../../database_administration/02_edb_loader/). \ No newline at end of file diff --git a/product_docs/docs/epas/15/working_with_oracle_data/loading_bulk_data.mdx b/product_docs/docs/epas/15/working_with_oracle_data/loading_bulk_data.mdx index 044efa20b12..783c1b5634e 100644 --- a/product_docs/docs/epas/15/working_with_oracle_data/loading_bulk_data.mdx +++ b/product_docs/docs/epas/15/working_with_oracle_data/loading_bulk_data.mdx @@ -1,7 +1,7 @@ --- navTitle: Loading bulk data title: "Loading bulk data (EDB*Loader)" -description: "Overview of loading bulk data with EDB*Loader" +description: "Overview of loading bulk data with EDB\*Loader" --- EDB\*Loader is a high-performance bulk data loader that provides an interface compatible with Oracle databases for EDB Postgres Advanced Server. The EDB\*Loader command line utility loads data from an input source, typically a file, into one or more tables using a subset of the parameters offered by Oracle SQL\*Loader. diff --git a/product_docs/docs/epas/15/working_with_oracle_data/proprietary_source_code.mdx b/product_docs/docs/epas/15/working_with_oracle_data/proprietary_source_code.mdx index 40c075f656d..c493aad88af 100644 --- a/product_docs/docs/epas/15/working_with_oracle_data/proprietary_source_code.mdx +++ b/product_docs/docs/epas/15/working_with_oracle_data/proprietary_source_code.mdx @@ -6,5 +6,5 @@ description: "Overview of the EDB*Wrap utility, which you use to protect proprie The EDB\*Wrap utility protects proprietary source code and programs like functions, stored procedures, triggers, and packages from unauthorized scrutiny. The EDB\*Wrap program translates a plaintext file that contains SPL or PL/pgSQL source code into a file that contains the same code in a form that's nearly impossible to read. Once you have the obfuscated form of the code, you can send that code to the PostgreSQL server, and the server stores those programs in obfuscated form. While EDB\*Wrap does obscure code, table definitions are still exposed. -See [EDB*Wrap](../epas_security_guide/03_edb_wrap/) for details about using the utility. +See [EDB\*Wrap](../epas_security_guide/03_edb_wrap/) for details about using the utility. From 8cb1717895a7337e6d6c41aafdc0acd20c6850cb Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 26 Sep 2023 14:58:25 -0400 Subject: [PATCH 152/255] Update 02_edb_loader.mdx --- .../docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx b/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx index 5fa9ae8922c..498e8872232 100644 --- a/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx +++ b/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx @@ -1,5 +1,5 @@ --- -title: "EDB\*Loader" +title: "EDB*Loader" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. From 160f8348021d201702655b574363eefadc268ad2 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 26 Sep 2023 15:00:56 -0400 Subject: [PATCH 153/255] Update 02_edb_loader.mdx --- .../docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx b/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx index 498e8872232..647369d4cfc 100644 --- a/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx +++ b/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx @@ -95,7 +95,7 @@ The following are examples of types of database errors that abort the transactio -## Building the EDB\*Loader Control File +## Building the EDB\*Loader control file When you invoke EDB\*Loader, the list of arguments provided must include the name of a control file. The control file includes the instructions that EDB\*Loader uses to load the table (or tables) from the input data file. The control file includes information such as: From 8ad0203ec9953cc9707e6781aadfa63389f9d38f Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 26 Sep 2023 15:01:43 -0400 Subject: [PATCH 154/255] Update 02_edb_loader.mdx --- .../docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx b/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx index 647369d4cfc..f5d42d653f6 100644 --- a/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx +++ b/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx @@ -447,7 +447,7 @@ ZONED EXTERNAL [()] | ZONED [([,])] **Note**: If the `DATE` or `TIMESTAMP` field type is specified along with a SQL expression for the column, then `datemask` must be specified after `DATE` or `TIMESTAMP` and before the SQL expression. See the following discussion of the `expr` parameter. - When using the `TIMESTAMP` field datatype, if you specify `time_stamp timestamp "yyyymmddhh24miss"` the `datemask` is converted to the SQL expression. However, in case of `time_stamp timestamp "select to_timestamp(:time_stamp, 'yyyymmddhh24miss')"`, the EDB\*Loader cannot differentiate between datemask and the SQL expression. It treats the third field (SQL expression in the example) as datemask and prepares the SQL expression, which will not be valid. Where: + When using the `TIMESTAMP` field datatype, if you specify `time_stamp timestamp "yyyymmddhh24miss"` the `datemask` is converted to the SQL expression. However, in case of `time_stamp timestamp "select to_timestamp(:time_stamp, 'yyyymmddhh24miss')"`, EDB\*Loader can't differentiate between datemask and the SQL expression. It treats the third field (SQL expression in the example) as datemask and prepares the SQL expression, which will not be valid. Where: - `first field` specifies the column name - `second field` specifies the datatype From 39b5901e12106a6ea590166c8283aed465a2ae61 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 26 Sep 2023 15:02:25 -0400 Subject: [PATCH 155/255] Update 02_edb_loader.mdx --- .../docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx b/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx index f5d42d653f6..6148da965fb 100644 --- a/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx +++ b/product_docs/docs/epas/12/epas_compat_tools_guide/02_edb_loader.mdx @@ -95,7 +95,7 @@ The following are examples of types of database errors that abort the transactio -## Building the EDB\*Loader control file +## Building the EDB\*Loader Control File When you invoke EDB\*Loader, the list of arguments provided must include the name of a control file. The control file includes the instructions that EDB\*Loader uses to load the table (or tables) from the input data file. The control file includes information such as: From bd7d7d901fd450bffa8f0d643f74454d39c3d1af Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 26 Sep 2023 15:03:39 -0400 Subject: [PATCH 156/255] Update loading_bulk_data.mdx --- .../docs/epas/15/working_with_oracle_data/loading_bulk_data.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/15/working_with_oracle_data/loading_bulk_data.mdx b/product_docs/docs/epas/15/working_with_oracle_data/loading_bulk_data.mdx index 783c1b5634e..044efa20b12 100644 --- a/product_docs/docs/epas/15/working_with_oracle_data/loading_bulk_data.mdx +++ b/product_docs/docs/epas/15/working_with_oracle_data/loading_bulk_data.mdx @@ -1,7 +1,7 @@ --- navTitle: Loading bulk data title: "Loading bulk data (EDB*Loader)" -description: "Overview of loading bulk data with EDB\*Loader" +description: "Overview of loading bulk data with EDB*Loader" --- EDB\*Loader is a high-performance bulk data loader that provides an interface compatible with Oracle databases for EDB Postgres Advanced Server. The EDB\*Loader command line utility loads data from an input source, typically a file, into one or more tables using a subset of the parameters offered by Oracle SQL\*Loader. From ba321062721d98a4f499a3c080d9b3070614eccf Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 26 Sep 2023 15:24:14 -0400 Subject: [PATCH 157/255] Fxed a couple of typos --- .../release/using_cluster/06_analyze_with_superset.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/biganimal/release/using_cluster/06_analyze_with_superset.mdx b/product_docs/docs/biganimal/release/using_cluster/06_analyze_with_superset.mdx index cecf5a2d7c9..5ce5edd3db0 100644 --- a/product_docs/docs/biganimal/release/using_cluster/06_analyze_with_superset.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/06_analyze_with_superset.mdx @@ -30,11 +30,11 @@ To connect to a BigAnimal cluster: 2. Select **Analyze > Connections**. 3. Select **+ Database**. 4. In the Add Database dialog box, enter a value for **Database Name**. -5. To connect to the database, you need database user with a password. Enter the connection string for your cluster in the **SQLALCHEMY URI** field, using the following format: +5. To connect to the database, you need a database user with a password. Enter the connection string for your cluster in the **SQLALCHEMY URI** field, using the following format: `postgresql://{}:{}@{}:{}/{}?sslmode=verify-full` !!!note - Your password is always encrypted before storage and never leaves your cloud environment. It's used only by the Superset software running in your BigAnimal infrastructure. As a defense-in-depth mechanism, we recommend using a Postgres user dedicated to Superset with a minimal set of privileges to just the database you're connecting. Never use your edb_admin, superuser or equivalent user with Superset. + Your password is always encrypted before storage and never leaves your cloud environment. It's used only by the Superset software running in your BigAnimal infrastructure. As a defense-in-depth mechanism, we recommend using a Postgres user dedicated to Superset with a minimal set of privileges to just the database you're connecting. Never use your edb_admin superuser or equivalent user with Superset. !!! 6. Check the connection by selecting **Test Connection**. Select **Add** if the connection was successful. From 1004107deb99d10b1d2bc6fc5e389bd892b239a6 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 26 Sep 2023 16:07:36 -0400 Subject: [PATCH 158/255] Fixed word order in recommendation --- .../docs/biganimal/release/overview/02_high_availability.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/overview/02_high_availability.mdx b/product_docs/docs/biganimal/release/overview/02_high_availability.mdx index a2dd68bd6a6..02a0ef2ec2f 100644 --- a/product_docs/docs/biganimal/release/overview/02_high_availability.mdx +++ b/product_docs/docs/biganimal/release/overview/02_high_availability.mdx @@ -53,7 +53,7 @@ Distributed high-availability clusters are powered by [EDB Postgres Distributed] Distributed high-availability clusters support both EDB Postgres Advanced Server and EDB Postgres Extended Server database distributions. -Distributed high-availability clusters contain one or two data groups. Your data groups can contain either three data nodes or two data nodes and one witness node. One of these data nodes is the leader at any given time, while the rest are shadow nodes. We don't recommend you use two data nodes and one witness node in production unless you use asynchronous [commit scopes](/pgd/latest/durability/commit-scopes/). +Distributed high-availability clusters contain one or two data groups. Your data groups can contain either three data nodes or two data nodes and one witness node. One of these data nodes is the leader at any given time, while the rest are shadow nodes. We recommend that you don't you use two data nodes and one witness node in production unless you use asynchronous [commit scopes](/pgd/latest/durability/commit-scopes/). [PGD Proxy](/pgd/latest/routing/proxy) routes all application traffic to the leader node, which acts as the principal write target to reduce the potential for data conflicts. PGD Proxy leverages a distributed consensus model to determine availability of the data nodes in the cluster. On failure or unavailability of the leader, PGD Proxy elects a new leader and redirects application traffic. Together with the core capabilities of EDB Postgres Distributed, this mechanism of routing application traffic to the leader node enables fast failover and switchover. From e5503c082604d9f885c86df18e8d2e7b5237253f Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 26 Sep 2023 16:20:58 -0400 Subject: [PATCH 159/255] small cleanup to new content --- .../advanced_storage_pack/using.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/advocacy_docs/pg_extensions/advanced_storage_pack/using.mdx b/advocacy_docs/pg_extensions/advanced_storage_pack/using.mdx index e97f24674aa..0be70dd73d6 100644 --- a/advocacy_docs/pg_extensions/advanced_storage_pack/using.mdx +++ b/advocacy_docs/pg_extensions/advanced_storage_pack/using.mdx @@ -7,7 +7,7 @@ The following are scenarios where the EDB Advanced Storage Pack TAMs are useful. ## Refdata example -A scenario where Refdata is useful is when creating a reference table of all +A scenario where Refdata is useful is creating a reference table of all the New York Stock Exchange (NYSE) stock symbols and their corporate names. This data is expected to change very rarely and be referenced frequently from a table tracking all stock trades for the entire market. @@ -32,7 +32,7 @@ CREATE INDEX ON nyse_trade USING BTREE(nyse_symbol_id); ``` When `heap` is used for `nyse_symbol`, manipulating rows in `nyse_trade` causes -row locks to be created in `nyse_symbol`, but only row locks are used in +row locks to be created in `nyse_symbol`. But only row locks are used in `nyse_symbol`: ```sql @@ -82,7 +82,7 @@ CREATE TABLE nyse_symbol ( ) USING refdata; ``` -In this case, manipulating data in `nyse_trade` does not generate row locks in `nyse_symbol`. But manipulating `nyse_symbol` directly cause an `EXCLUSIVE` lock to be acquired on the entire relation: +In this case, manipulating data in `nyse_trade` doesn't generate row locks in `nyse_symbol`. But manipulating `nyse_symbol` directly causes an `EXCLUSIVE` lock to be acquired on the entire relation: ```sql =# BEGIN; @@ -143,7 +143,7 @@ SELECT autocluster.autocluster( ``` !!! Note -The `cols` parameter specifies which table is clustered. In this case, `{1}` corresponds to the first column of the table, `thermostat_id`, which is the most common access pattern. +The `cols` parameter specifies the table that's clustered. In this case, `{1}` corresponds to the first column of the table, `thermostat_id`, which is the most common access pattern. !!! Populate the table with the `thermostat_id` and `recordtime` data: @@ -243,11 +243,11 @@ ANALYZE nyse_trade; ``` Given that the inserts intercalated `nyse_symbol_id`, a query that consults one -stock would touch most pages if the table used `heap`, but would touch far +stock touches most pages if the table uses heap, but touches far fewer pages using Autocluster. The following query operates on attributes that must be fetched from the table -after an index scan, and shows the number of buffers touched: +after an index scan and shows the number of buffers touched: ```sql EXPLAIN (ANALYZE, BUFFERS, TIMING OFF, SUMMARY OFF, COSTS OFF) @@ -255,7 +255,7 @@ EXPLAIN (ANALYZE, BUFFERS, TIMING OFF, SUMMARY OFF, COSTS OFF) FROM nyse_trade WHERE nyse_symbol_id = 10; ``` -This is the query plan using `autocluster`: +This is the query plan using Autocluster: ``` QUERY PLAN @@ -272,7 +272,7 @@ This is the query plan using `autocluster`: (9 rows) ``` -For contrast, this is the query plan using `heap`: +For contrast, this is the query plan using heap: ``` QUERY PLAN From 157a85bc5c878baa4d5baace833abeb1e1e3227e Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 26 Sep 2023 16:27:32 -0400 Subject: [PATCH 160/255] edits to upgrade topic --- .../7/installing/upgrading_replication_server/index.mdx | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx index 30d71015fa9..34ed798c930 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx @@ -10,12 +10,12 @@ redirects: You can install Replication Server 7 when you have existing single-master or multi-master replication systems that are running under Replication Server version 7. -It is assumed that you are installing Replication Server 7.x on the same host machine that is currently running the earlier version of Replication Server you are upgrading from and that you will then manage the existing replication systems using Replication Server 7.x. +It's assumed that you're installing Replication Server 7.x on the same host machine that's currently running the earlier version of Replication Server you're upgrading from and that you plan to then manage the existing replication systems using Replication Server 7.x. -If you are using a version of Replication Server earlier than 6.2.15, first upgrade to 6.2.15 or a later 6.2.x point version before upgrading to 7.x. +If you're using a version of Replication Server earlier than 6.2.15, first upgrade to 6.2.15 or a later 6.2.x point version before upgrading to 7.x. !!!note - Version 7.x provides a non-breaking upgrade path for existing 6.2.x based cluster deployments; however, we strongly recommended that you verify the upgrade in a staging or nonproduction environment before applying the upgrade in a production environment. There is no downgrade path from version 7.x to version 6.2.x so it is essential to test the upgrade first before applying it to the production environment. + Version 7.x provides a non-breaking upgrade path for existing 6.2.x based cluster deployments. However, we strongly recommended that you verify the upgrade in a staging or nonproduction environment before applying the upgrade in a production environment. There's no downgrade path from version 7.x to version 6.2.x, so it's essential to test the upgrade first before applying it to the production environment. @@ -27,5 +27,3 @@ For more details on upgrading Replication Server, see: - [Upgrading with the graphical user interface installer](upgrading_with_gui_installer) After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it (for Linux) or rename the driver (for Windows). See [Installing a JDBC driver](../installing_jdbc_driver/) for more information. - - From 8e2849ab829633f2f286b45421ecd1d7760b32ed Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 26 Sep 2023 17:08:49 -0400 Subject: [PATCH 161/255] Edits to Kasten by Veeam guide --- .../KastenbyVeeam/02-PartnerInformation.mdx | 12 ++--- .../KastenbyVeeam/03-SolutionSummary.mdx | 6 +-- .../04-ConfiguringVeeamKasten.mdx | 48 +++++++++---------- .../KastenbyVeeam/05-UsingVeeamKasten.mdx | 41 ++++++++-------- .../06-CertificationEnvironment.mdx | 4 +- .../KastenbyVeeam/07-SupportandLogging.mdx | 20 ++++---- .../partner_docs/KastenbyVeeam/index.mdx | 7 ++- 7 files changed, 70 insertions(+), 68 deletions(-) diff --git a/advocacy_docs/partner_docs/KastenbyVeeam/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/02-PartnerInformation.mdx index 509aaaba12c..2da4e7d0e36 100644 --- a/advocacy_docs/partner_docs/KastenbyVeeam/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/02-PartnerInformation.mdx @@ -1,12 +1,12 @@ --- -title: 'Partner Information' -description: 'Details of the Partner' +title: 'Partner information' +description: 'Details of the partner' --- |   |   | | ----------- | ----------- | -| **Partner Name** | Kasten by Veeam | -| **Web Site** | https://www.kasten.io/ | -| **Partner Product** | Kasten K10 | +| **Partner name** | Kasten by Veeam | +| **Website** | https://www.kasten.io/ | +| **Partner product** | Kasten K10 | | **Version** | Kasten 6.0 | -| **Product Description** | Kasten K10 is a Cloud Native data management platform for Day 2 operations. Purpose built for Kubernetes, Kasten backups and restores your applications, handles disaster recovery and manages application migration. Kasten can be implemented with EDB Postgres for Kubernetes to create fast backups and restores. | +| **Product description** | Kasten K10 is a cloud-native data management platform for Day 2 operations. Built for Kubernetes, Kasten backs up and restores your applications, handles disaster recovery, and manages application migration. Kasten can be implemented with EDB Postgres for Kubernetes to create fast backups and restores. | diff --git a/advocacy_docs/partner_docs/KastenbyVeeam/03-SolutionSummary.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/03-SolutionSummary.mdx index 9e2d3a5a7de..5775170c63e 100644 --- a/advocacy_docs/partner_docs/KastenbyVeeam/03-SolutionSummary.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/03-SolutionSummary.mdx @@ -1,10 +1,10 @@ --- -title: 'Solution Summary' +title: 'Solution summary' description: 'Explanation of the solution and its purpose' --- -Kasten by Veeam is a data management platform built for Kubernetes that can provide enterprise operations teams with an easy-to-use and secure system for backup and restore of Kubernetes applications. Kasten can be used in conjunction with EDB Postgres for Kubernetes and the EDB external backup adapter to successfully backup and restore data. +Kasten by Veeam is a data management platform built for Kubernetes that can provide enterprise operations teams with an easy-to-use and secure system for backup and restore of Kubernetes applications. Kasten can be used with EDB Postgres for Kubernetes and the EDB external backup adapter to successfully back up and restore data. -The EDB Postgres for Kubernetes [external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) allows for a third party tool, such as Kasten by Veeam, to discover an API that is needed in order to create a successful backup. +The EDB Postgres for Kubernetes [external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) allows for a third-party tool, such as Kasten by Veeam, to discover an API that's needed to create a successful backup. ![Kasten K10 Architecture](Images/KastenSolutionSummaryImagenew.png) diff --git a/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx index fc6a1fbfcef..73fe4f893c4 100644 --- a/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx @@ -1,6 +1,6 @@ --- title: 'Configuration' -description: 'Walkthrough on configuring the integration' +description: 'Walkthrough of configuring the integration' --- Implementing EDB Postgres for Kubernetes with Kasten by Veeam requires the following components: @@ -16,32 +16,32 @@ Implementing EDB Postgres for Kubernetes with Kasten by Veeam requires the follo - Kasten K10 installed on your system !!! Note - For this integration, use the **example.yaml** files provided in each section for the appropriate Kasten configuration pieces, and change any environment variables per your specific needs. + For this integration, use the `example.yaml` files provided for the appropriate Kasten configuration pieces, and change any environment variables per your specific needs. - The **Add the Backup Decorator Annotations to the Cluster** section is the important section for the Kasten addon integration. + [Add the backup decorator annotations to the cluster](#add-the-backup-decorator-annotations-to-the-cluster) is important for the Kasten add-on integration. - Refer to the [EDB Postgres for Kubernetes external backup adapter](https://www.enterprisedb.com/docs/postgres_for_kubernetes/latest/addons/#external-backup-adapter) docs to view more detailed information on the EDB Postgres for Kubernetes backup adaptor addon functionality and additional details on its configuraton parameters. + Refer to the [EDB Postgres for Kubernetes external backup adapter](/postgres_for_kubernetes/latest/addons/#external-backup-adapter) documentation for more detailed information on the EDB Postgres for Kubernetes backup adaptor add-on functionality and additional details on its configuraton parameters. -## Install the Operator +## Install the operator -1. Install the EDB Postgres for Kubernetes operator. +Install the EDB Postgres for Kubernetes operator. ```bash kubectl apply -f https://get.enterprisedb.io/cnp/postgresql-operator-1.20.2.yaml ``` -Running this command will create the operator namespace where the controller will be running. +Running this command creates the operator namespace where the controller runs. -## Create an EDB Cluster, Client and Add Data +## Create an EDB cluster and client and add data -1. Initiate the below lines of code in your Kubernetes environment to create a specific namespace and apply your `.yaml` file. +1. In your Kubernetes environment, create a specific namespace and apply your `.yaml` file: ```bash kubctl create ns edb kubectl apply -f cluster-example.yaml -n edb ``` -### Example **cluster-example.yaml** file: +Example `cluster-example.yaml` file: ```bash # Example of PostgreSQL cluster @@ -94,7 +94,9 @@ kubectl cnp certificate cluster-app \ ```bash kubectl create -f client.yaml -n edb ``` -### Example **client.yaml** file: + +Example `client.yaml` file: + ```bash apiVersion: apps/v1 kind: Deployment @@ -148,7 +150,7 @@ spec: defaultMode: 0600 ``` -6. Add some data into the cluster to test the backup and restore, the following is sample data that was used for this example. +6. Add some data into the cluster to test the backup and restore. The following is sample data that was used for this example: ```bash kubectl exec -it deploy/cert-test -- bash @@ -168,11 +170,11 @@ select * from links; exit ``` -## Add the Backup Decorator Annotations to the Cluster +## Add the backup decorator annotations to the cluster -If you create the cluster from the previous section the **cluster-example.yaml** already includes the Kasten addon therefore you can skip this part. If you are working with your own cluster you will need to add the Kasten addon. +If you created the cluster from the previous process, `cluster-example.yaml` already includes the Kasten add-on, and you can skip this part. If you're working with your own cluster, you need to add the Kasten add-on. -1. Add the following annotations to your cluster, in the above **cluster-example.yaml** there is an example of where to add the annotation. +1. Add the following annotations to your cluster. The previous `cluster-example.yaml` file shows an example of where to add the annotation. ```bash "k8s.enterprisedb.io/addons": '["kasten"]' @@ -180,13 +182,13 @@ If you create the cluster from the previous section the **cluster-example.yaml** ## Install the EDB blueprint -1. Enter the following command in your environment: +1. In your environment, enter: ```bash kubectl create -f edb-hooks.yaml ``` -### Example **edb-hooks.yaml** file: +Example `edb-hooks.yaml` file: ```bash apiVersion: cr.kanister.io/v1alpha1 @@ -260,14 +262,12 @@ actions: done exit 0 ``` -## Create a Backup Policy with the EDB hooks - -1. Launch your Kasten K10 interface. +## Create a backup policy with the EDB hooks -2. Create a policy for the EDB namespace, you will need to set up a location profile for the export and kanister actions. - -Add the hooks example: - ![Kasten Backup Policy with EDB Hooks](Images/KastenBackupPolicywithHooks.png) +1. Launch the Kasten K10 interface. +2. Create a policy for the EDB namespace. You need to set up a location profile for the export and kanister actions. +3. Add the hooks example: + ![Kasten Backup Policy with EDB Hooks](Images/KastenBackupPolicywithHooks.png) diff --git a/advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx index 0f9ea225747..5d77e8f48cb 100644 --- a/advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten.mdx @@ -3,43 +3,42 @@ title: 'Using' description: 'Walkthrough of example usage scenarios' --- -When you have configured your Kubernetes environment per the `Configuring` section you will then be able to start taking backups and completing restores. +After you configure your Kubernetes environment, you can start taking backups and completing restores. -## Launch a Backup +## Launch a backup 1. Launch your Kasten K10 interface. -2. Use Kasten K10 to launch a backup that creates two restore points, a local and a remote. +2. Use Kasten K10 to launch a backup that creates two restore points: a local and a remote. -3. You now have a backup we can use to validate a restore in the next section. +3. You now have a backup to use to validate a restore. ![Launch a Backup](Images/LaunchaBackup.png) -!!! Note - The Kasten by Veeam backup process is explained below: - 1. EDB elects a replica for the backup. - 2. Kasten will discover the replica. - 3. Kasten calls the EDB pre-backup command on the discovered replica. - 4. The replica becomes ready for the backup. - 5. Kasten takes the backup. - 6. Kasten calls the EDB post backup command on the replica. - 7. The replica leaves the backup mode. - 8. The backup is then over and is consistent for a restore. +## Backup process summary + +The Kasten by Veeam backup process is: +1. EDB elects a replica for the backup. +2. Kasten discovers the replica. +3. Kasten calls the EDB pre-backup command on the discovered replica. +4. The replica becomes ready for the backup. +5. Kasten takes the backup. +6. Kasten calls the EDB post-backup command on the replica. +7. The replica leaves the backup mode. +8. The backup is over and is consistent for a restore. -## Restore Database +## Restore database -1. To get ready for Kasten K10 to complete a restore, we will remove the EDB namespace in this example. +1. To get ready for Kasten K10 to complete a restore, remove the EDB namespace: ```bash kubectl delete ns edb ``` -2. In the Kasten K10 interface go to your remote restore point. +2. In the Kasten K10 interface, go to your remote restore point. -3. On the remote restore point select `restore`. +3. On the remote restore point, select **restore**. -4. After the restore is complete, all of your data will be present. +4. After the restore is complete, all of your data is present. ![Kasten Data Restore Point](Images/KastenRestorePoint.png) - - diff --git a/advocacy_docs/partner_docs/KastenbyVeeam/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/06-CertificationEnvironment.mdx index 2f1d83e235b..83826f4956f 100644 --- a/advocacy_docs/partner_docs/KastenbyVeeam/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/06-CertificationEnvironment.mdx @@ -1,11 +1,11 @@ --- -title: 'Certification Environment' +title: 'Certification environment' description: 'Overview of the certification environment' --- |   |   | | ----------- | ----------- | -| **Certification Test Date** | August 28, 2023 | +| **Certification test date** | August 28, 2023 | | **EDB Postgres for Kubernetes** | 1.20.2 | | **EDB Postgres for Kubernetes External Backup Adapter** | | **Kasten by Veeam Kasten K10** | 6.0 | diff --git a/advocacy_docs/partner_docs/KastenbyVeeam/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/07-SupportandLogging.mdx index 630405dd64c..f4f329b68b9 100644 --- a/advocacy_docs/partner_docs/KastenbyVeeam/07-SupportandLogging.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/07-SupportandLogging.mdx @@ -1,21 +1,25 @@ --- -title: 'Support and Logging Details' +title: 'Support and logging details' description: 'Details of the support process and logging information' --- ## Support -Technical support for the use of these products is provided by both EDB and Veeam. A proper support contract is required to be in place at both EDB and Veeam. A support ticket can be opened on either side to start the process. If it is determined through the support ticket that resources from the other vendor is required, the customer should open a support ticket with that vendor through normal support channels. This will allow both companies to work together to help the customer as needed. +Technical support for the use of these products is provided by both EDB and Veeam. A support contract must be in place at both EDB and Veeam. You can open a support ticket with either company to start the process. If it's determined through the support ticket that resources from the other vendor are required, open a support ticket with that vendor through normal support channels. This approach allows both companies to work together to help you as needed. ## Logging -**EDB Postgres Advanced Server Logs** +The following log files are available. -Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance and from here you can navigate to `log`, `current_logfiles` or you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs. An example of the full path to view EDB Postgres Advanced Server logs: `/var/lib/edb/as15/data/log`. +### EDB Postgres Advanced Server logs -**PostgreSQL Server Logs** +Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance. From there, you can navigate to `log` or `current_logfiles`. Or, you can navigate to the `postgresql.conf` file, which you can use to customize logging options or enable `edb_audit` logs. -The default log directories for PostgreSQL logs vary depending on the operating system: +An example of the full path to view EDB Postgres Advanced Server logs is `/var/lib/edb/as15/data/log`. + +### PostgreSQL Server logs + +The default log directories for PostgreSQL logs depend on the operating system: - Debian-based system: `/var/log/postgresql/postgresql-x.x.main.log. X.x.` @@ -23,7 +27,7 @@ The default log directories for PostgreSQL logs vary depending on the operating - Windows: `C:\Program Files\PostgreSQL\9.3\data\pg_log` -**Kasten by Veeam Logs** +### Kasten by Veeam logs -On the Kasten K10 UI navigate to `Settings` then `Support` then click `Download Logs`. +On the Kasten K10 interface, select **Settings > Support**, and then select **Download Logs**. ![Veeam Kasten Logs](Images/VeeamKastenLogging.png) diff --git a/advocacy_docs/partner_docs/KastenbyVeeam/index.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/index.mdx index c5b88448b4d..054ba07e381 100644 --- a/advocacy_docs/partner_docs/KastenbyVeeam/index.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/index.mdx @@ -5,10 +5,9 @@ directoryDefaults: iconName: handshake --- -

- -

+![Partner Program Logo](Images/PartnerProgram.jpg.png) +

EDB GlobalConnect Technology Partner Implementation Guide

Kasten by Veeam for Kasten K10

-

This document is intended to augment each vendor’s product documentation in order to guide the reader in getting the products working together. It is not intended to show the optimal configuration for the certified integration.

\ No newline at end of file +

This document is intended to augment each vendor’s product documentation to guide you in getting the products working together. It isn't intended to show the optimal configuration for the certified integration.

\ No newline at end of file From fd0137c520b2661c5b24786d2ca48548676db302 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Wed, 27 Sep 2023 09:00:44 +0530 Subject: [PATCH 162/255] Update product_docs/docs/biganimal/release/overview/02_high_availability.mdx --- .../docs/biganimal/release/overview/02_high_availability.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/overview/02_high_availability.mdx b/product_docs/docs/biganimal/release/overview/02_high_availability.mdx index 02a0ef2ec2f..f4edbb1ab23 100644 --- a/product_docs/docs/biganimal/release/overview/02_high_availability.mdx +++ b/product_docs/docs/biganimal/release/overview/02_high_availability.mdx @@ -53,7 +53,7 @@ Distributed high-availability clusters are powered by [EDB Postgres Distributed] Distributed high-availability clusters support both EDB Postgres Advanced Server and EDB Postgres Extended Server database distributions. -Distributed high-availability clusters contain one or two data groups. Your data groups can contain either three data nodes or two data nodes and one witness node. One of these data nodes is the leader at any given time, while the rest are shadow nodes. We recommend that you don't you use two data nodes and one witness node in production unless you use asynchronous [commit scopes](/pgd/latest/durability/commit-scopes/). +Distributed high-availability clusters contain one or two data groups. Your data groups can contain either three data nodes or two data nodes and one witness node. One of these data nodes is the leader at any given time, while the rest are shadow nodes. We recommend that you don't use two data nodes and one witness node in production unless you use asynchronous [commit scopes](/pgd/latest/durability/commit-scopes/). [PGD Proxy](/pgd/latest/routing/proxy) routes all application traffic to the leader node, which acts as the principal write target to reduce the potential for data conflicts. PGD Proxy leverages a distributed consensus model to determine availability of the data nodes in the cluster. On failure or unavailability of the leader, PGD Proxy elects a new leader and redirects application traffic. Together with the core capabilities of EDB Postgres Distributed, this mechanism of routing application traffic to the leader node enables fast failover and switchover. From 633fd6f7699daa619aa930652cccf4edd51c771a Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Wed, 27 Sep 2023 09:25:59 +0530 Subject: [PATCH 163/255] Update edb_loader_overview.mdx --- .../database_administration_tools/edb_loader_overview.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/epas/15/tools_utilities_and_components/database_administration_tools/edb_loader_overview.mdx b/product_docs/docs/epas/15/tools_utilities_and_components/database_administration_tools/edb_loader_overview.mdx index 873ddc56b72..d36f8bac96d 100644 --- a/product_docs/docs/epas/15/tools_utilities_and_components/database_administration_tools/edb_loader_overview.mdx +++ b/product_docs/docs/epas/15/tools_utilities_and_components/database_administration_tools/edb_loader_overview.mdx @@ -3,6 +3,6 @@ title: "EDB*Loader" description: "Provides an overview of the EDB*Loader high-performance bulk data loader" --- -EDB\*Loader is a high-performance bulk data loader that provides an interface compatible with Oracle databases for EDB Postgres Advanced Server. The EDB*Loader command line utility loads data from an input source, typically a file, into one or more tables using a subset of the parameters offered by Oracle SQL*Loader. +EDB\*Loader is a high-performance bulk data loader that provides an interface compatible with Oracle databases for EDB Postgres Advanced Server. The EDB\*Loader command line utility loads data from an input source, typically a file, into one or more tables using a subset of the parameters offered by Oracle SQL\*Loader. -For details about using the tool, see [Loading bulk data](../../database_administration/02_edb_loader/). \ No newline at end of file +For details about using the tool, see [Loading bulk data](../../database_administration/02_edb_loader/). From be6894e1aa877cdd777f2c2e575623439587cc20 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Wed, 27 Sep 2023 10:49:28 -0400 Subject: [PATCH 164/255] BAH content in Connecting from Azure --- .../01_connecting_from_azure/index.mdx | 33 ++++++++++++++----- 1 file changed, 24 insertions(+), 9 deletions(-) diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx index 936aa93b8c3..df19f823b59 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx @@ -1,6 +1,7 @@ --- title: Connecting from Azure navTitle: From Azure +deepToC: true redirects: - /biganimal/release/using_cluster/connecting_your_cluster/01_connecting_from_azure - /biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/01_private_endpoint @@ -10,8 +11,6 @@ Three different methods enable you to connect to your cluster from your applicat ## Azure private endpoint (recommended) -While other methods for connecting your cluster from your application's virtual network in Azure are available, we strongly recommend using the Azure private endpoint method. - Azure private endpoint is a network interface that securely connects a private IP address from your Azure virtual network (VNet) to an external service. You grant access only to a single cluster instead of the entire BigAnimal resource virtual network, thus ensuring maximum network isolation. Other advantages include: - You need to configure the Private Link only once. Then you can use multiple private endpoints to connect applications from many different VNets. @@ -23,8 +22,24 @@ Private endpoints are the same mechanism used by first-party Azure services such If you set up a private endpoint and want to change to a public network, you must remove the private endpoint resources before making the change. !!! +### Using BigAnimal's cloud account + +When using BigAnimal's cloud account, when creating a cluster, you provide BigAnimal with your Azure subscription ID (see [Networking](/biganimal/latest/getting_started/creating_a_cluster/#network-logs--telemetry-section)). BigAnimal, in turn, provides you with a private link alias, which you can use to connect to your cluster privately. + +1. When creating your cluster, on the Cluster Settings tab, in the Network section: + 1. Select **Private**. + + 1. Enter your application's Azure subscription ID. + +1. After the cluster is created, go to the cluster details to see the corresponding endpoint service name. You need the service name while creating a private endpoint. + +1. Create a private endpoint in the client's VPC. The steps for creating a private endpoint in the client's VPC are the same whether you're using BigAnimal's cloud or your own. See [Step 1: Create an Azure private endpoint](#step-1-create-an-azure-private-endpoint) and [Step 2: Create an Azure Private DNS Zone for the private endpoint](#step-2-create-an-azure-private-dns-zone-for-the-private-endpoint). + +1. In your application's Azure account, select **Private Link Center**, and then select **Private endpoints**. Select the endpoint you created previously, and use the service name provided in the details section in BigAnimal to access your cluster. + +### Using your Azure account -## Private endpoint example +#### Example This example shows how to connect your cluster using Azure private endpoint. @@ -46,7 +61,7 @@ Assume that your cluster is on a subscription called `development` and is being - Virtual network subnet: `snet-client` -### Prerequisites +#### Prerequisites To walk through an example in your own environment, you need: @@ -67,11 +82,11 @@ To walk through an example in your own environment, you need: In this example, you create an Azure private endpoint in your client VM's virtual network. After you create the private endpoint, you can use its private IP address to access the Postgres cluster. You must perform this procedure for every virtual network you want to connect from. -### Step 1: Create an Azure private endpoint +#### Step 1: Create an Azure private endpoint Create an Azure private endpoint in each client virtual network that needs to connect to your BigAnimal cluster. You can create the private endpoint using either the [Azure portal](#using-the-azure-portal) or the [Azure CLI](#using-the-azure-cli). -#### Using the Azure portal +##### Using the Azure portal 1. If you prefer to create the private endpoint using the Azure portal, on the upper-left side of the screen, select **Create a resource > Networking > Private Link**. Alternatively. in the search box enter `Private Link`. @@ -129,7 +144,7 @@ you created by entering the following details: 10. Proceed to [Accessing the cluster](#accessing-the-cluster). -#### Using the Azure CLI +##### Using the Azure CLI If you prefer to create the private endpoint using the Azure CLI, either use your local terminal with an Azure CLI profile already configured or open a new Azure Cloud Shell using the Azure portal. @@ -160,7 +175,7 @@ az network private-endpoint create \ - `subscription` is the Azure subscription in which to create the private endpoint. -### Accessing the cluster +#### Accessing the cluster You have successfully built a tunnel between your client VM's virtual network and the cluster. You can now access the cluster from the private endpoint in your client VM. The private endpoint's private IP address is associated with an independent virtual network NIC. Get the private endpoint's private IP address using the following commands: ```shell @@ -185,7 +200,7 @@ edb_admin=> ``` -### Step 2: Create an Azure Private DNS Zone for the private endpoint +#### Step 2: Create an Azure Private DNS Zone for the private endpoint EDB strongly recommends using a [private Azure DNS zone](https://docs.microsoft.com/en-us/azure/dns/private-dns-privatednszone) with the private endpoint to establish a connection with a cluster. You can't validate TLS certificates using `verify-full` when connecting to an IP address. From 4ffacea8508ff740062b6d9d35dd54fcd9321fb9 Mon Sep 17 00:00:00 2001 From: Petr Jelinek Date: Tue, 22 Aug 2023 23:00:41 +0300 Subject: [PATCH 165/255] Fix notes for bdr.run_on_nodes and bdr.run_on_group The text was copy pasted from `bdr.run_on_all_nodes` and the wording and warnings need to be somewhat different for these two functions --- .../docs/pgd/5/reference/functions.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/product_docs/docs/pgd/5/reference/functions.mdx b/product_docs/docs/pgd/5/reference/functions.mdx index 8c0638a731c..0f11f729c99 100644 --- a/product_docs/docs/pgd/5/reference/functions.mdx +++ b/product_docs/docs/pgd/5/reference/functions.mdx @@ -486,13 +486,13 @@ defaults are used. This function doesn't go through normal replication. It uses direct client connection to all known nodes. By default, the connection is created -with `bdr.ddl_replication = off`, since the commands are already being sent -to all of the nodes in the cluster. +with `bdr.ddl_replication = off`, to avoid replication issues when the same +replicated DDL command is sent to multiple nodes. Be careful when using this function since you risk breaking replication -and causing inconsistencies between nodes. Use either transparent DDL -replication or `bdr.replicate_ddl_command()` to replicate DDL. -DDL might be blocked in a future release. +and causing inconsistencies between nodes. For global schema changes, use +either transparent DDL replication or `bdr.replicate_ddl_command()` to +replicate DDL. ### `bdr.run_on_group` @@ -525,13 +525,13 @@ defaults are used. This function doesn't go through normal replication. It uses direct client connection to all known nodes. By default, the connection is created -with `bdr.ddl_replication = off`, since the commands are already being sent -to all of the nodes in the cluster. +with `bdr.ddl_replication = off`, to avoid replication issues when the same +replicated DDL command is sent to multiple nodes. Be careful when using this function since you risk breaking replication -and causing inconsistencies between nodes. Use either transparent DDL -replication or `bdr.replicate_ddl_command()` to replicate DDL. -DDL might be blocked in a future release. +and causing inconsistencies between nodes. For global schema changes, use +either transparent DDL replication or `bdr.replicate_ddl_command()` to +replicate DDL. ### `bdr.global_lock_table` From 95e3156b61927363eb7ba1f48fd4b6e775d8a5a7 Mon Sep 17 00:00:00 2001 From: Josh Heyer <63653723+josh-heyer@users.noreply.github.com> Date: Wed, 27 Sep 2023 07:54:51 -0700 Subject: [PATCH 166/255] Clarify scope of sentence Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> --- product_docs/docs/pgd/5/reference/functions.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/reference/functions.mdx b/product_docs/docs/pgd/5/reference/functions.mdx index 0f11f729c99..38905db703f 100644 --- a/product_docs/docs/pgd/5/reference/functions.mdx +++ b/product_docs/docs/pgd/5/reference/functions.mdx @@ -529,7 +529,7 @@ with `bdr.ddl_replication = off`, to avoid replication issues when the same replicated DDL command is sent to multiple nodes. Be careful when using this function since you risk breaking replication -and causing inconsistencies between nodes. For global schema changes, use +and causing inconsistencies between nodes in the group. For global schema changes, use either transparent DDL replication or `bdr.replicate_ddl_command()` to replicate DDL. From 611b679ac3410a78ad178dc646039f0c8f57adfe Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 26 Sep 2023 09:45:59 -0400 Subject: [PATCH 167/255] Dates and formatting for PostGIS release notes --- product_docs/docs/postgis/3.2/01_release_notes/index.mdx | 2 +- .../docs/postgis/3.2/01_release_notes/rel_notes312.mdx | 6 +++++- .../docs/postgis/3.2/01_release_notes/rel_notes314.mdx | 6 +++++- .../docs/postgis/3.2/01_release_notes/rel_notes315.mdx | 6 +++++- .../docs/postgis/3.2/01_release_notes/rel_notes32.mdx | 6 +++++- .../docs/postgis/3.2/01_release_notes/rel_notes321.mdx | 2 +- 6 files changed, 22 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/postgis/3.2/01_release_notes/index.mdx b/product_docs/docs/postgis/3.2/01_release_notes/index.mdx index 769dc9c3e12..67803d2ae71 100644 --- a/product_docs/docs/postgis/3.2/01_release_notes/index.mdx +++ b/product_docs/docs/postgis/3.2/01_release_notes/index.mdx @@ -13,7 +13,7 @@ cover what was new in each release. | Version | Release date | | ------------------------ | ------------ | -| [3.2.1](rel_notes321) | 04 Aug 2022 | +| [3.2.1](rel_notes321) | 04 Aug 2023 | | [3.2.0](rel_notes32) | 01 Dec 2022 | | [3.1.5](rel_notes315) | 03 Aug 2022| | [3.1.4](rel_notes314) | 01 Dec 2021| diff --git a/product_docs/docs/postgis/3.2/01_release_notes/rel_notes312.mdx b/product_docs/docs/postgis/3.2/01_release_notes/rel_notes312.mdx index 361833672a8..14a45f99365 100644 --- a/product_docs/docs/postgis/3.2/01_release_notes/rel_notes312.mdx +++ b/product_docs/docs/postgis/3.2/01_release_notes/rel_notes312.mdx @@ -1,6 +1,10 @@ --- -title: "Version 3.1.2" +title: "PostGIS 3.1.2 release notes" +navTitle: Version 3.1.2 --- + +Released: 24 Jun 2021 + EDB PostGIS is a PostgreSQL extension that allows you to store geographic information systems (GIS) objects in an EDB Posgres Advanced Server database. New features, enhancements, bug fixes, and other changes in PostGIS 3.1.4 include: diff --git a/product_docs/docs/postgis/3.2/01_release_notes/rel_notes314.mdx b/product_docs/docs/postgis/3.2/01_release_notes/rel_notes314.mdx index c40846500e0..0e6b7430ca9 100644 --- a/product_docs/docs/postgis/3.2/01_release_notes/rel_notes314.mdx +++ b/product_docs/docs/postgis/3.2/01_release_notes/rel_notes314.mdx @@ -1,8 +1,12 @@ --- -title: "Version 3.1.4" +title: "PostGIS 3.1.4 release notes" +navTitle: Version 3.1.4 redirects: - /postgis/latest/01_release_notes/10_rel_notes314/ --- + +Released: 01 Dec 2021 + EDB PostGIS is a PostgreSQL extension that allows you to store geographic information systems (GIS) objects in an EDB Postgres Advanced Server database. New features, enhancements, bug fixes, and other changes in PostGIS 3.1.4 include: diff --git a/product_docs/docs/postgis/3.2/01_release_notes/rel_notes315.mdx b/product_docs/docs/postgis/3.2/01_release_notes/rel_notes315.mdx index b2003578cd9..17916c9dade 100644 --- a/product_docs/docs/postgis/3.2/01_release_notes/rel_notes315.mdx +++ b/product_docs/docs/postgis/3.2/01_release_notes/rel_notes315.mdx @@ -1,6 +1,10 @@ --- -title: "Version 3.1.5" +title: "PostGIS 3.1.5 release notes" +navTitle: Version 3.1.5 --- + +Released: 03 Aug 2022 + EDB PostGIS is a PostgreSQL extension that allows you to store geographic information systems (GIS) objects in an EDB Postgres Advanced Server database. New features, enhancements, bug fixes, and other changes in PostGIS 3.1.5 include: diff --git a/product_docs/docs/postgis/3.2/01_release_notes/rel_notes32.mdx b/product_docs/docs/postgis/3.2/01_release_notes/rel_notes32.mdx index 31315f37fe6..2b86af2cfbb 100644 --- a/product_docs/docs/postgis/3.2/01_release_notes/rel_notes32.mdx +++ b/product_docs/docs/postgis/3.2/01_release_notes/rel_notes32.mdx @@ -1,6 +1,10 @@ --- -title: "Version 3.2.0" +title: "PostGIS 3.2.0 release notes" +navTitle: Version 3.2.0 --- + +Released: 01 Dec 2022 + EDB PostGIS is a PostgreSQL extension that allows you to store geographic information systems (GIS) objects in an EDB Postgres Advanced Server database. New features, enhancements, bug fixes, and other changes in PostGIS 3.2.0 include: diff --git a/product_docs/docs/postgis/3.2/01_release_notes/rel_notes321.mdx b/product_docs/docs/postgis/3.2/01_release_notes/rel_notes321.mdx index f0f2d886288..95d2f33c39c 100644 --- a/product_docs/docs/postgis/3.2/01_release_notes/rel_notes321.mdx +++ b/product_docs/docs/postgis/3.2/01_release_notes/rel_notes321.mdx @@ -3,7 +3,7 @@ title: "PostGIS 3.2.1 release notes" navTitle: Version 3.2.1 --- -Released: 04 Aug 2022 +Released: 04 Aug 2023 EDB PostGIS is a PostgreSQL extension that allows you to store geographic information systems (GIS) objects in an EDB Postgres Advanced Server database. From 1974b8fde8893ad25684804baa789dbed771ee49 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 26 Sep 2023 11:20:12 -0400 Subject: [PATCH 168/255] new titles and dates for EPES and Postgres for Kubernetes --- product_docs/docs/pge/15/release_notes/rel_notes15.2.mdx | 4 +++- product_docs/docs/pge/15/release_notes/rel_notes15.3.mdx | 4 +++- .../postgres_for_kubernetes/1/rel_notes/1_0_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_10_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_11_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_12_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_13_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_14_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_15_1_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_15_2_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_15_3_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_15_4_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_15_5_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_15_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_16_1_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_16_2_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_16_3_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_16_4_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_16_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_17_1_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_17_2_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_17_3_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_17_4_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_17_5_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_17_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_18_0_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_18_1_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_18_2_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_18_3_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_18_4_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_18_5_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_18_6_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_19_0_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_19_1_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_19_2_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_19_3_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_19_4_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_1_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_20_0_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_20_1_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_2_1_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_2_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_3_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_4_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_5_1_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_5_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_6_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_7_1_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_7_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_8_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_9_1_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_9_2_rel_notes.mdx | 2 ++ .../postgres_for_kubernetes/1/rel_notes/1_9_rel_notes.mdx | 2 ++ 53 files changed, 108 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pge/15/release_notes/rel_notes15.2.mdx b/product_docs/docs/pge/15/release_notes/rel_notes15.2.mdx index 421b1ae8efa..98d443baac5 100644 --- a/product_docs/docs/pge/15/release_notes/rel_notes15.2.mdx +++ b/product_docs/docs/pge/15/release_notes/rel_notes15.2.mdx @@ -1,8 +1,10 @@ --- -title: "EDB Postgres Extended Server version 15.2" +title: "EDB Postgres Extended Server 15.2 release notes" navTitle: Version 15.2 --- +Released: 14 Feb 2023 + New features, enhancements, bug fixes, and other changes in EDB Postgres Extended Server 15.2 include: | Type | Description | diff --git a/product_docs/docs/pge/15/release_notes/rel_notes15.3.mdx b/product_docs/docs/pge/15/release_notes/rel_notes15.3.mdx index 5f3fa2dbc3d..a91c59b27c9 100644 --- a/product_docs/docs/pge/15/release_notes/rel_notes15.3.mdx +++ b/product_docs/docs/pge/15/release_notes/rel_notes15.3.mdx @@ -1,8 +1,10 @@ --- -title: "EDB Postgres Extended Server version 15.3" +title: "EDB Postgres Extended Server 15.3 release notes" navTitle: Version 15.3 --- +Released: 11 May 2023 + New features, enhancements, bug fixes, and other changes in EDB Postgres Extended Server 15.2 include: | Type | Description | Category | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_0_rel_notes.mdx index d3ba4879aea..7f9ae461bc6 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_0_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_0_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.0 release notes" navTitle: "Version 1.0" --- +Released: 04 Feb 2021 + The first major release implements Cluster, Backup and ScheduledBackup in the API group postgresql.k8s.enterprisedb.io/v1. It uses these resources to create and manage PostgreSQL clusters inside Kubernetes with the following main capabilities: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_10_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_10_rel_notes.mdx index 35e06d9c28a..5770db49ac2 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_10_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_10_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.10.0 release notes" navTitle: "Version 1.10.0" --- +Released: 11 Nov 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_11_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_11_rel_notes.mdx index fc1fcdc58c5..23a7ad26cc3 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_11_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_11_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.11.0 release notes" navTitle: "Version 1.11.0" --- +Released: 15 Dec 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_12_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_12_rel_notes.mdx index 2ff1c50972d..d920ab7dd96 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_12_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_12_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.12.0 release notes" navTitle: "Version 1.12.0" --- +Released: 11 Jan 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_13_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_13_rel_notes.mdx index e4b1237a337..d3dc3cbfbb7 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_13_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_13_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.13.0 release notes" navTitle: "Version 1.13.0" --- +Released: 17 Feb 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_14_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_14_rel_notes.mdx index 2028ecf3aa2..3c6145c86b9 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_14_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_14_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.14.0 release notes" navTitle: "Version 1.14.0" --- +Released: 25 Mar 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_1_rel_notes.mdx index 2361e7a152b..c889f1149e4 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_1_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_1_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.15.1 release notes" navTitle: "Version 1.15.1" --- +Released: 27 May 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_2_rel_notes.mdx index 1d0bf49bd00..c923f94e941 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_2_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_2_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.15.2 release notes" navTitle: "Version 1.15.2" --- +Released: 07 Jul 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_3_rel_notes.mdx index af95aff6e62..0c1b84eeb83 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_3_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_3_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.15.3 release notes" navTitle: "Version 1.15.3" --- +Released: 12 Aug 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_4_rel_notes.mdx index f8f625f7d7d..1aa4560cb6b 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_4_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_4_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.15.4 release notes" navTitle: "Version 1.15.4" --- +Released: 06 Sep 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_5_rel_notes.mdx index d939daf8b69..a950e86eb1f 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_5_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_5_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.15.5 release notes" navTitle: "Version 1.15.5" --- +Released: 07 Oct 2022 + !!!warning Version 1.15 has reached End-of-Life (EOL). Version 1.15.5 is the last release for the 1.15 minor version. diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_rel_notes.mdx index 67645ac5bff..739ba0ad241 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_15_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.15.2 release notes" navTitle: "Version 1.15.0" --- +Released: 21 Apr 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_1_rel_notes.mdx index 2d0564bcf0a..94218c8d937 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_1_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_1_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.16.1 release notes" navTitle: "Version 1.16.1" --- +Released: 12 Aug 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_2_rel_notes.mdx index aab481edbcc..076e0fde767 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_2_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_2_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.16.2 release notes" navTitle: "Version 1.16.2" --- +Released: 06 Sep 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_3_rel_notes.mdx index 3c78d2f2ff2..9b92821a500 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_3_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_3_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.16.3 release notes" navTitle: "Version 1.16.3" --- +Released: 07 Oct 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_4_rel_notes.mdx index 82dc5e450e0..908b1498fdd 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_4_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_4_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.16.4 release notes" navTitle: "Version 1.16.4" --- +Released: 14 Nov 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_rel_notes.mdx index f43e17cf10b..7de76f846d6 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.16.0 release notes" navTitle: "Version 1.16.0" --- +Released: 07 Jul 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_1_rel_notes.mdx index 6990f7ff12b..7f5ffa5bfbf 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_1_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_1_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.17.1 release notes" navTitle: "Version 1.17.1" --- +Released: 07 Oct 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_2_rel_notes.mdx index b387956a6e9..2fc745aebe4 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_2_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_2_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.17.2 release notes" navTitle: "Version 1.17.2" --- +Released: 14 Nov 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_3_rel_notes.mdx index e8dae2c112f..9494699de96 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_3_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_3_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.17.3 release notes" navTitle: "Version 1.17.3" --- +Released: 21 Dec 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_4_rel_notes.mdx index 87560d31132..3a32d4b9e1c 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_4_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_4_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.17.4 release notes" navTitle: "Version 1.17.4" --- +Released: 14 Feb 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_5_rel_notes.mdx index a3356d7d0b0..4b2652bdc1f 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_5_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_5_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.17.5 release notes" navTitle: "Version 1.17.5" --- +Released: 20 Mar 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_rel_notes.mdx index 4bf7bb2ea99..4d119356919 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_17_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.17.0 release notes" navTitle: "Version 1.17.0" --- +Released: 06 Sep 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_0_rel_notes.mdx index b8e50d0c140..251d69b2e56 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_0_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_0_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.18.0 release notes" navTitle: "Version 1.18.0" --- +Released: 14 Nov 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_1_rel_notes.mdx index bec42588bef..ac5583167eb 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_1_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_1_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.18.1 release notes" navTitle: "Version 1.18.1" --- +Released: 21 Dec 2022 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_2_rel_notes.mdx index fc7a1a2a47e..446d3b3124f 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_2_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_2_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.18.2 release notes" navTitle: "Version 1.18.2" --- +Released: 14 Feb 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_3_rel_notes.mdx index 8f40da9b6f1..e128f33796b 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_3_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_3_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.18.3 release notes" navTitle: "Version 1.18.3" --- +Released: 20 Mar 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_4_rel_notes.mdx index 57ef56b045e..c3ca9a0f07c 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_4_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_4_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.18.4 release notes" navTitle: "Version 1.18.4" --- +Released: 27 Apr 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_5_rel_notes.mdx index 3e5a909ee8d..691490a0e78 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_5_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_5_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.18.5 release notes" navTitle: "Version 1.18.5" --- +Released: 13 Jun 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_6_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_6_rel_notes.mdx index 7d5eb2ad2e3..1b6d558327c 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_6_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_18_6_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.18.6 release notes" navTitle: "Version 1.18.6" --- +Released: 27 Jul 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_0_rel_notes.mdx index ccd829de0bf..afc71bc35ca 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_0_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_0_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.19.0 release notes" navTitle: "Version 1.19.0" --- +Released: 14 Feb 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_1_rel_notes.mdx index ebaee203c3c..963acfd90fd 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_1_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_1_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.19.1 release notes" navTitle: "Version 1.19.1" --- +Released: 20 Mar 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_2_rel_notes.mdx index 94a2400bee2..6740de3bc86 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_2_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_2_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.19.2 release notes" navTitle: "Version 1.19.2" --- +Released: 27 Apr 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_3_rel_notes.mdx index 7a25b1f71af..0b3c922df74 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_3_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_3_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.19.3 release notes" navTitle: "Version 1.19.3" --- +Released: 13 Jun 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_4_rel_notes.mdx index 5cde55b56b8..d8a61148c42 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_4_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_19_4_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.19.4 release notes" navTitle: "Version 1.19.4" --- +Released: 27 Jul 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_1_rel_notes.mdx index 5d58066314e..002e64742bd 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_1_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_1_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.1 release notes" navTitle: "Version 1.1" --- +Released: 03 Mar 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_20_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_20_0_rel_notes.mdx index a3f0b83bcff..5bbd146676d 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_20_0_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_20_0_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.20.0 release notes" navTitle: "Version 1.20.0" --- +Released: 27 Apr 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_20_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_20_1_rel_notes.mdx index 55d9d5ac3ae..3e155c861b3 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_20_1_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_20_1_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.20.1 release notes" navTitle: "Version 1.20.1" --- +Released: 13 Jun 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_2_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_2_1_rel_notes.mdx index 33dd32f9f8d..73ad098f500 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_2_1_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_2_1_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.2.1 release notes" navTitle: "Version 1.2.1" --- +Released: 06 Apr 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_2_rel_notes.mdx index 5a91bd755aa..bebdd48aab3 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_2_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_2_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.2.0 release notes" navTitle: "Version 1.2.0" --- +Released: 31 Mar 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_3_rel_notes.mdx index e268234539f..9403bfb5be3 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_3_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_3_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.3.0 release notes" navTitle: "Version 1.3.0" --- +Released: 23 Apr 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_4_rel_notes.mdx index afe9fe65f0a..6ae34489cb3 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_4_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_4_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.4.0 release notes" navTitle: "Version 1.4.0" --- +Released: 18 May 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_5_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_5_1_rel_notes.mdx index 4eaf8fab220..c525f953fb8 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_5_1_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_5_1_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.5.1 release notes" navTitle: "Version 1.5.1" --- +Released: 11 Jun 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_5_rel_notes.mdx index 2d4dd5bdcd4..95d589a3337 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_5_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_5_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.5.0 release notes" navTitle: "Version 1.5.0" --- +Released: 17 Jun 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_6_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_6_rel_notes.mdx index 60ea9af3cc7..30790f70165 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_6_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_6_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.6.0 release notes" navTitle: "Version 1.6.0" --- +Released: 12 Jul 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_7_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_7_1_rel_notes.mdx index 28ac7bf87a0..fe6bd15f050 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_7_1_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_7_1_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.7.1 release notes" navTitle: "Version 1.7.1" --- +Released: 11 Aug 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_7_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_7_rel_notes.mdx index 225105817f3..72672f6f3ae 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_7_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_7_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.7.0 release notes" navTitle: "Version 1.7.0" --- +Released: 28 Jul 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_8_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_8_rel_notes.mdx index 4f31ca209b5..2f8b4020b6a 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_8_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_8_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.8.0 release notes" navTitle: "Version 1.8.0" --- +Released: 13 Sep 2023 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_9_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_9_1_rel_notes.mdx index cde4575ca4e..9d26a4aa094 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_9_1_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_9_1_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.9.1 release notes" navTitle: "Version 1.9.1" --- +Released: 30 Sep 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_9_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_9_2_rel_notes.mdx index 80592b98c67..31f9857c4b4 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_9_2_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_9_2_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.9.2 release notes" navTitle: "Version 1.9.2" --- +Released: 15 Oct 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_9_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_9_rel_notes.mdx index 07d3913fe2a..e7418d0abc4 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_9_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_9_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.9.0 release notes" navTitle: "Version 1.9.0" --- +Released: 28 Sep 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | From ef25e390cc270e39e3e33dd2e1372363a965ed57 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 26 Sep 2023 11:34:53 -0400 Subject: [PATCH 169/255] 1.15.5 was missing from index page for Postgres for Kubernetes --- .../postgres_for_kubernetes/1/rel_notes/1_16_5_rel_notes.mdx | 2 ++ product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx | 1 + 2 files changed, 3 insertions(+) diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_5_rel_notes.mdx index ea487c21746..e6305843135 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_5_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_5_rel_notes.mdx @@ -3,6 +3,8 @@ title: "EDB Postgres for Kubernetes 1.16.5 release notes" navTitle: "Version 1.16.5" --- +Released: 21 Dec 2021 + This release of EDB Postgres for Kubernetes includes the following: | Type | Description | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx index d490711144a..0dc85308acc 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx @@ -84,6 +84,7 @@ The EDB Postgres for Kubernetes documentation describes the major version of EDB | [1.17.2](1_17_2_rel_notes) | 14 Nov 2022 | Upstream [1.17.2](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | | [1.17.1](1_17_1_rel_notes) | 07 Oct 2022 | Upstream [1.17.1](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | | [1.17.0](1_17_rel_notes) | 06 Sep 2022 | Upstream [1.17.0](https://cloudnative-pg.io/documentation/1.17/release_notes/v1.17/) | +| [1.16.5](1_16_5_rel_notes) | 21 Dec 2022 | Upstream [1.16.4](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.4](1_16_4_rel_notes) | 14 Nov 2022 | Upstream [1.16.4](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.3](1_16_3_rel_notes) | 07 Oct 2022 | Upstream [1.16.3](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | | [1.16.2](1_16_2_rel_notes) | 06 Sep 2022 | Upstream [1.16.2](https://cloudnative-pg.io/documentation/1.16/release_notes/v1.16/) | From 98c7e6bb78c3e9d8cbc053ddef4e76d4227c1d78 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 26 Sep 2023 11:56:04 -0400 Subject: [PATCH 170/255] New titles and date for Postgres Distributed and Failover Manager --- .../docs/efm/4/efm_rel_notes/04_efm_46_rel_notes.mdx | 5 ++++- .../docs/efm/4/efm_rel_notes/05_efm_45_rel_notes.mdx | 5 ++++- .../docs/efm/4/efm_rel_notes/06_efm_44_rel_notes.mdx | 5 ++++- .../docs/efm/4/efm_rel_notes/07_efm_43_rel_notes.mdx | 5 ++++- .../docs/efm/4/efm_rel_notes/08_efm_42_rel_notes.mdx | 5 ++++- .../docs/efm/4/efm_rel_notes/09_efm_41_rel_notes.mdx | 5 ++++- .../docs/efm/4/efm_rel_notes/10_efm_40_rel_notes.mdx | 5 ++++- product_docs/docs/pgd/5/rel_notes/pgd_5.0.0_rel_notes.mdx | 4 +++- product_docs/docs/pgd/5/rel_notes/pgd_5.0.1_rel_notes.mdx | 4 +++- product_docs/docs/pgd/5/rel_notes/pgd_5.1.0_rel_notes.mdx | 4 +++- 10 files changed, 37 insertions(+), 10 deletions(-) diff --git a/product_docs/docs/efm/4/efm_rel_notes/04_efm_46_rel_notes.mdx b/product_docs/docs/efm/4/efm_rel_notes/04_efm_46_rel_notes.mdx index 302184b8e58..33d848505e1 100644 --- a/product_docs/docs/efm/4/efm_rel_notes/04_efm_46_rel_notes.mdx +++ b/product_docs/docs/efm/4/efm_rel_notes/04_efm_46_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 4.6" +title: "Failover Manager 4.6 release notes" +navTitle: Version 4.6 --- +Released: 14 Feb 2023 + Enhancements, bug fixes, and other changes in EFM 4.6 include: | Type | Description | diff --git a/product_docs/docs/efm/4/efm_rel_notes/05_efm_45_rel_notes.mdx b/product_docs/docs/efm/4/efm_rel_notes/05_efm_45_rel_notes.mdx index b77815942ed..04be692e59a 100644 --- a/product_docs/docs/efm/4/efm_rel_notes/05_efm_45_rel_notes.mdx +++ b/product_docs/docs/efm/4/efm_rel_notes/05_efm_45_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 4.5" +title: "Failover Manager 4.5 release notes" +navTitle: Version 4.5 --- +Released: 30 Aug 2022 + Enhancements, bug fixes, and other changes in EFM 4.5 include: | Type | Description | diff --git a/product_docs/docs/efm/4/efm_rel_notes/06_efm_44_rel_notes.mdx b/product_docs/docs/efm/4/efm_rel_notes/06_efm_44_rel_notes.mdx index ff4198a9b17..825e53a9092 100644 --- a/product_docs/docs/efm/4/efm_rel_notes/06_efm_44_rel_notes.mdx +++ b/product_docs/docs/efm/4/efm_rel_notes/06_efm_44_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 4.4" +title: "Failover Manager 4.4 release notes" +navTitle: Version 4.4 --- +Released: 05 Jan 2022 + Enhancements, bug fixes, and other changes in EFM 4.4 include: | Type | Description | diff --git a/product_docs/docs/efm/4/efm_rel_notes/07_efm_43_rel_notes.mdx b/product_docs/docs/efm/4/efm_rel_notes/07_efm_43_rel_notes.mdx index ecf004613f9..27955089c3b 100644 --- a/product_docs/docs/efm/4/efm_rel_notes/07_efm_43_rel_notes.mdx +++ b/product_docs/docs/efm/4/efm_rel_notes/07_efm_43_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 4.3" +title: "Failover Manager 4.3 release notes" +navTitle: Version 4.3 --- +Released: 18 Dec 2021 + Enhancements, bug fixes, and other changes in EFM 4.3 include: | Type | Description | diff --git a/product_docs/docs/efm/4/efm_rel_notes/08_efm_42_rel_notes.mdx b/product_docs/docs/efm/4/efm_rel_notes/08_efm_42_rel_notes.mdx index 43edf2bbdbf..a91949c4114 100644 --- a/product_docs/docs/efm/4/efm_rel_notes/08_efm_42_rel_notes.mdx +++ b/product_docs/docs/efm/4/efm_rel_notes/08_efm_42_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 4.2" +title: "Failover Manager 4.2 release notes" +navTitle: Version 4.2 --- +Released: 19 Apr 2021 + Enhancements, bug fixes, and other changes in EFM 4.2 include: | Type | Description | diff --git a/product_docs/docs/efm/4/efm_rel_notes/09_efm_41_rel_notes.mdx b/product_docs/docs/efm/4/efm_rel_notes/09_efm_41_rel_notes.mdx index 06307a3cf72..26c41d583ea 100644 --- a/product_docs/docs/efm/4/efm_rel_notes/09_efm_41_rel_notes.mdx +++ b/product_docs/docs/efm/4/efm_rel_notes/09_efm_41_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 4.1" +title: "Failover Manager 4.1 release notes" +navTitle: Version 4.1 --- +Released: 11 Dec 2021 + Enhancements, bug fixes, and other changes in EFM 4.1 include: | Type | Description | diff --git a/product_docs/docs/efm/4/efm_rel_notes/10_efm_40_rel_notes.mdx b/product_docs/docs/efm/4/efm_rel_notes/10_efm_40_rel_notes.mdx index 2f91b376bc7..21a607e6415 100644 --- a/product_docs/docs/efm/4/efm_rel_notes/10_efm_40_rel_notes.mdx +++ b/product_docs/docs/efm/4/efm_rel_notes/10_efm_40_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 4.0" +title: "Failover Manager 4.0 release notes" +navTitle: Version 4.0 --- +Released: 02 Sep 2021 + Enhancements, bug fixes, and other changes in EFM 4.0 include: | Type | Description | diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.0.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.0.0_rel_notes.mdx index 53e0ad7a376..8de3704586c 100644 --- a/product_docs/docs/pgd/5/rel_notes/pgd_5.0.0_rel_notes.mdx +++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.0.0_rel_notes.mdx @@ -1,8 +1,10 @@ --- -title: "Release notes for EDB Postgres Distributed version 5.0.0" +title: "EDB Postgres Distributed 5.0.0 release notes" navTitle: "Version 5.0.0" --- +Released: 21 Feb 2023 + EDB Postgres Distributed version 5.0.0 is a is a new major version of EDB Postgres Distributed. This version brings major new features and compatibility changes. diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.0.1_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.0.1_rel_notes.mdx index fe24f09ce94..4c2be1d67c7 100644 --- a/product_docs/docs/pgd/5/rel_notes/pgd_5.0.1_rel_notes.mdx +++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.0.1_rel_notes.mdx @@ -1,8 +1,10 @@ --- -title: "Release notes for EDB Postgres Distributed version 5.0.1" +title: "EDB Postgres Distributed 5.0.1 release notes" navTitle: "Version 5.0.1" --- +Released: 21 Mar 2023 + EDB Postgres Distributed version 5.0.1 is a patch version of EDB Postgres Distributed. This version addresses security vulnerabilities in dependencies for PGD-Proxy and PGD-CLI. diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.1.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.1.0_rel_notes.mdx index 62d8cbffd1e..ebadaa671bb 100644 --- a/product_docs/docs/pgd/5/rel_notes/pgd_5.1.0_rel_notes.mdx +++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.1.0_rel_notes.mdx @@ -1,8 +1,10 @@ --- -title: "Release notes for EDB Postgres Distributed version 5.1.0" +title: "EDB Postgres Distributed 5.1.0 release notes" navTitle: "Version 5.1.0" --- +Released: 16 May 2023 + EDB Postgres Distributed version 5.1.0 is a minor version of EDB Postgres Distributed. This version addresses security vulnerabilities in dependencies for PGD Proxy and PGD CLI. From 196345e42ff44d8ee4217f602b00b416cf405b57 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 27 Sep 2023 09:05:17 -0400 Subject: [PATCH 171/255] New titles and dates for PEM, Live Compare, EDBPlus, Trusted Architect --- .../edb_plus/41/02_release_notes/edbplus_41.0_rel_notes.mdx | 5 ++++- .../edb_plus/41/02_release_notes/edbplus_41.1_rel_notes.mdx | 4 ++++ product_docs/docs/livecompare/2/rel_notes/2.0_rel_notes.mdx | 5 ++++- product_docs/docs/livecompare/2/rel_notes/2.1_rel_notes.mdx | 5 ++++- product_docs/docs/livecompare/2/rel_notes/2.2_rel_notes.mdx | 5 ++++- product_docs/docs/livecompare/2/rel_notes/2.3_rel_notes.mdx | 5 ++++- product_docs/docs/livecompare/2/rel_notes/2.4_rel_notes.mdx | 5 ++++- product_docs/docs/pem/9/pem_rel_notes/900_rel_notes.mdx | 5 ++++- product_docs/docs/pem/9/pem_rel_notes/910_rel_notes.mdx | 5 ++++- product_docs/docs/pem/9/pem_rel_notes/911_rel_notes.mdx | 5 ++++- product_docs/docs/pem/9/pem_rel_notes/920_rel_notes.mdx | 5 ++++- product_docs/docs/pem/9/pem_rel_notes/921_rel_notes.mdx | 5 ++++- product_docs/docs/pem/9/pem_rel_notes/922_rel_notes.mdx | 5 ++++- product_docs/docs/tpa/23/rel_notes/tpa_23.12_rel_notes.mdx | 1 + product_docs/docs/tpa/23/rel_notes/tpa_23.13_rel_notes.mdx | 1 + product_docs/docs/tpa/23/rel_notes/tpa_23.14_rel_notes.mdx | 1 + product_docs/docs/tpa/23/rel_notes/tpa_23.15_rel_notes.mdx | 1 + product_docs/docs/tpa/23/rel_notes/tpa_23.16_rel_notes.mdx | 1 + product_docs/docs/tpa/23/rel_notes/tpa_23.17_rel_notes.mdx | 1 + product_docs/docs/tpa/23/rel_notes/tpa_23.18_rel_notes.mdx | 1 + product_docs/docs/tpa/23/rel_notes/tpa_23.19_rel_notes.mdx | 1 + product_docs/docs/tpa/23/rel_notes/tpa_23.20_rel_notes.mdx | 1 + product_docs/docs/tpa/23/rel_notes/tpa_23.23_rel_notes.mdx | 1 - 23 files changed, 61 insertions(+), 13 deletions(-) diff --git a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.0_rel_notes.mdx b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.0_rel_notes.mdx index 45858b30a37..810f88280c8 100644 --- a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.0_rel_notes.mdx +++ b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.0_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 41.0.0" +title: "EDB*Plus 41.0.0 release notes" +navTitle: Version 41.0.0 --- +Released: 14 Feb 2023 + New features, enhancements, bug fixes, and other changes in EDB*Plus 41.0.0 include: | Type | Description | diff --git a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.1_rel_notes.mdx b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.1_rel_notes.mdx index 69bc21a38e3..d2b83b6c781 100644 --- a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.1_rel_notes.mdx +++ b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.1_rel_notes.mdx @@ -1,7 +1,11 @@ --- title: "Version 41.1.0" +title: "EDB*Plus 41.1.0 release notes" +navTitle: Version 41.1.0 --- +Released: 20 Apr 2023 + New features, enhancements, bug fixes, and other changes in EDB*Plus 41.1.0 include: | Type | Description | diff --git a/product_docs/docs/livecompare/2/rel_notes/2.0_rel_notes.mdx b/product_docs/docs/livecompare/2/rel_notes/2.0_rel_notes.mdx index 9570893c606..bfa579daa21 100644 --- a/product_docs/docs/livecompare/2/rel_notes/2.0_rel_notes.mdx +++ b/product_docs/docs/livecompare/2/rel_notes/2.0_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 2.0" +title: "LiveCompare 2.0 release notes" +navTitle: Version 2.0 --- +Released: 15 Feb 2022 + LiveCompare 2.0 includes the following new features, enhancements, bug fixes, and other changes: | Type | Description | ID | diff --git a/product_docs/docs/livecompare/2/rel_notes/2.1_rel_notes.mdx b/product_docs/docs/livecompare/2/rel_notes/2.1_rel_notes.mdx index 13a671457f3..cbfe29ade96 100644 --- a/product_docs/docs/livecompare/2/rel_notes/2.1_rel_notes.mdx +++ b/product_docs/docs/livecompare/2/rel_notes/2.1_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 2.1" +title: "LiveCompare 2.1 release notes" +navTitle: Version 2.1 --- +Released: Mar 31 2022 + LiveCompare 2.1 includes the following new features, bug fixes, and other changes: | Type | Description | ID | diff --git a/product_docs/docs/livecompare/2/rel_notes/2.2_rel_notes.mdx b/product_docs/docs/livecompare/2/rel_notes/2.2_rel_notes.mdx index 79daab91e1c..09ce8e1ac60 100644 --- a/product_docs/docs/livecompare/2/rel_notes/2.2_rel_notes.mdx +++ b/product_docs/docs/livecompare/2/rel_notes/2.2_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 2.2" +title: "LiveCompare 2.2 release notes" +navTitle: Version 2.2 --- +Released: 14 Jun 2022 + LiveCompare 2.2 includes the following new features, enhancements, and bug fixes: | Type | Description | ID | diff --git a/product_docs/docs/livecompare/2/rel_notes/2.3_rel_notes.mdx b/product_docs/docs/livecompare/2/rel_notes/2.3_rel_notes.mdx index c79a2c72e29..d5349ff6d51 100644 --- a/product_docs/docs/livecompare/2/rel_notes/2.3_rel_notes.mdx +++ b/product_docs/docs/livecompare/2/rel_notes/2.3_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 2.3" +title: "LiveCompare 2.3 release notes" +navTitle: Version 2.3 --- +Released: 15 Aug 2022 + LiveCompare 2.3 includes the following new features, enhancements, bug fixes, and other changes: | Type | Description | ID | diff --git a/product_docs/docs/livecompare/2/rel_notes/2.4_rel_notes.mdx b/product_docs/docs/livecompare/2/rel_notes/2.4_rel_notes.mdx index 40883857bba..1514dc5f792 100644 --- a/product_docs/docs/livecompare/2/rel_notes/2.4_rel_notes.mdx +++ b/product_docs/docs/livecompare/2/rel_notes/2.4_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 2.4" +title: "LiveCompare 2.4 release notes" +navTitle: Version 2.4 --- +Released: 29 Nov 2022 + LiveCompare 2.4 includes the following new features, enhancements, bug fixes, and other changes: | Type | Description | diff --git a/product_docs/docs/pem/9/pem_rel_notes/900_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/900_rel_notes.mdx index 2b9445949dd..0b758229b6b 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/900_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/900_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 9.0.0" +title: "Postgres Enterprise Manager 9.0.0 release notes" +navTitle: Version 9.0.0 --- +Released: 09 Dec 2022 + New features, enhancements, bug fixes, and other changes in PEM 9.0.0 include: | Type | Description | ID | diff --git a/product_docs/docs/pem/9/pem_rel_notes/910_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/910_rel_notes.mdx index 6ea2c4e920e..7b2945fa4a1 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/910_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/910_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 9.1.0" +title: "Postgres Enterprise Manager 9.1.0 release notes" +navTitle: Version 9.1.0 --- +Released: 14 Feb 2023 + New features, enhancements, bug fixes, and other changes in PEM 9.1.0 include: | Type | Description | diff --git a/product_docs/docs/pem/9/pem_rel_notes/911_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/911_rel_notes.mdx index 97b941f9ea7..71b0718ceb5 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/911_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/911_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 9.1.1" +title: "Postgres Enterprise Manager 9.1.1 release notes" +navTitle: Version 9.1.1 --- +Released: 31 Mar 2023 + New features, enhancements, bug fixes, and other changes in PEM 9.1.0 include: | Type | Description | diff --git a/product_docs/docs/pem/9/pem_rel_notes/920_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/920_rel_notes.mdx index 3f76dbffb94..245905e56b1 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/920_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/920_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 9.2.0" +title: "Postgres Enterprise Manager 9.2.0 release notes" +navTitle: Version 9.2.0 --- +Released: 24 May 2023 + New features, enhancements, bug fixes, and other changes in PEM 9.2.0 include: | Type | Description | diff --git a/product_docs/docs/pem/9/pem_rel_notes/921_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/921_rel_notes.mdx index 9c1a6652f1f..3d2a9021222 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/921_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/921_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 9.2.1" +title: "Postgres Enterprise Manager 9.2.1 release notes" +navTitle: Version 9.2.1 --- +Released: 03 Jul 2023 + New features, enhancements, bug fixes, and other changes in PEM 9.2.1 include: | Type | Description | diff --git a/product_docs/docs/pem/9/pem_rel_notes/922_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/922_rel_notes.mdx index 91681265165..c327e2e483f 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/922_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/922_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 9.2.2" +title: "Postgres Enterprise Manager 9.2.2 release notes" +navTitle: Version 2.2 --- +Released: 14 Jul 2023 + New features, enhancements, bug fixes, and other changes in PEM 9.2.2 include: | Type | Description | diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.12_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.12_rel_notes.mdx index 0e1f58a8cd1..e8ce5ae934c 100644 --- a/product_docs/docs/tpa/23/rel_notes/tpa_23.12_rel_notes.mdx +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.12_rel_notes.mdx @@ -3,6 +3,7 @@ title: Trusted Postgres Architect 23.12 release notes navTitle: "Version 23.12" --- +Released: 21 Feb 2023 New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.12 include the following: diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.13_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.13_rel_notes.mdx index 841a1271a69..f139ee1e0d8 100644 --- a/product_docs/docs/tpa/23/rel_notes/tpa_23.13_rel_notes.mdx +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.13_rel_notes.mdx @@ -3,6 +3,7 @@ title: Trusted Postgres Architect 23.13 release notes navTitle: "Version 23.13" --- +Released: 22 Feb 2023 New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.13 include the following: diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.14_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.14_rel_notes.mdx index 8fb02fe20f1..62e728f6421 100644 --- a/product_docs/docs/tpa/23/rel_notes/tpa_23.14_rel_notes.mdx +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.14_rel_notes.mdx @@ -3,6 +3,7 @@ title: Trusted Postgres Architect 23.14 release notes navTitle: "Version 23.14" --- +Released: 23 Feb 2023 New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.14 include the following: diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.15_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.15_rel_notes.mdx index 9ae77171c25..95633190101 100644 --- a/product_docs/docs/tpa/23/rel_notes/tpa_23.15_rel_notes.mdx +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.15_rel_notes.mdx @@ -3,6 +3,7 @@ title: Trusted Postgres Architect 23.15 release notes navTitle: "Version 23.15" --- +Released: 15 Mar 2023 New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.15 include the following: diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.16_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.16_rel_notes.mdx index 5166745d16a..1eeedd621c3 100644 --- a/product_docs/docs/tpa/23/rel_notes/tpa_23.16_rel_notes.mdx +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.16_rel_notes.mdx @@ -3,6 +3,7 @@ title: Trusted Postgres Architect 23.16 release notes navTitle: "Version 23.16" --- +Released: 21 Mar 2023 New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.16 include the following: diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.17_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.17_rel_notes.mdx index fcd0588b04e..9f56cd96812 100644 --- a/product_docs/docs/tpa/23/rel_notes/tpa_23.17_rel_notes.mdx +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.17_rel_notes.mdx @@ -3,6 +3,7 @@ title: Trusted Postgres Architect 23.17 release notes navTitle: "Version 23.17" --- +Released: 10 May 2023 New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.17 include the following: diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.18_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.18_rel_notes.mdx index 839ace293bd..2fc577bb937 100644 --- a/product_docs/docs/tpa/23/rel_notes/tpa_23.18_rel_notes.mdx +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.18_rel_notes.mdx @@ -3,6 +3,7 @@ title: Trusted Postgres Architect 23.18 release notes navTitle: "Version 23.18" --- +Released: 23 May 2023 New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.18 include the following: diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.19_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.19_rel_notes.mdx index 432f345f4f2..d91de001247 100644 --- a/product_docs/docs/tpa/23/rel_notes/tpa_23.19_rel_notes.mdx +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.19_rel_notes.mdx @@ -3,6 +3,7 @@ title: Trusted Postgres Architect 23.19 release notes navTitle: "Version 23.19" --- +Released: 12 Jul 2023 New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.19 include the following: diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.20_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.20_rel_notes.mdx index bb0b433c0b8..820cf53bc0f 100644 --- a/product_docs/docs/tpa/23/rel_notes/tpa_23.20_rel_notes.mdx +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.20_rel_notes.mdx @@ -3,6 +3,7 @@ title: Trusted Postgres Architect 23.20 release notes navTitle: "Version 23.20" --- +Released: 01 Aug 2023 New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.20 include the following: diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.23_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.23_rel_notes.mdx index 14ea25356b6..99037059a7e 100644 --- a/product_docs/docs/tpa/23/rel_notes/tpa_23.23_rel_notes.mdx +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.23_rel_notes.mdx @@ -5,7 +5,6 @@ navTitle: "Version 23.23" Released: 21 Sep 2023 - New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.23 include the following: | Type | Description | From fde5aee98b9247370a4dd98a082dab0fa82cc11a Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 27 Sep 2023 09:30:45 -0400 Subject: [PATCH 172/255] New titles and dates for connector products --- .../01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx | 6 ++++-- .../01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx | 6 ++++-- .../01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx | 6 +++++- .../01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx | 7 +++++-- .../01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx | 7 ++++--- .../01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx | 6 ++++-- .../01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx | 6 ++++-- .../42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx | 6 ++++-- .../42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx | 6 ++++-- .../42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx | 6 ++++-- .../15/ocl_rel_notes/01_ocl_release_notes.mdx | 6 +++++- .../15/ocl_rel_notes/15.2.0.2_ocl_release_notes.mdx | 6 +++++- .../15/ocl_rel_notes/15.2.0.3_ocl_release_notes.mdx | 6 +++++- .../13/01_odbc_rel_notes/02_odbc_13.2.0.01_rel_notes.mdx | 5 ++++- .../13/01_odbc_rel_notes/03_odbc_13.1.0.02_rel_notes.mdx | 5 ++++- .../13/01_odbc_rel_notes/04_odbc_13.1.0.01_rel_notes.mdx | 6 ++++-- .../13/01_odbc_rel_notes/05_odbc_13.0.0.01_rel_notes.mdx | 5 ++++- 17 files changed, 73 insertions(+), 28 deletions(-) diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx index 8fa8baa1326..4a5f03be0fb 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx @@ -1,8 +1,10 @@ --- -title: "Version 42.3.3.1" - +title: "EDB JDBC Connector 42.3.3.1 release notes" +navTitle: Version 42.3.3.1 --- +Released: 20 Apr 2022 + The EDB JDBC connector provides connectivity between a Java application and an EDB Postgres Advanced Server database. New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.3.3.1 include: diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx index 69c511e90c7..ab5fb48f540 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx @@ -1,8 +1,10 @@ --- -title: "Version 42.3.2.1" - +title: "EDB JDBC Connector 42.3.2.1 release notes" +navTitle: Version 42.3.2.1 --- +Released: 15 Feb 2022 + The EDB JDBC connector provides connectivity between a Java application and an EDB Postgres Advanced Server database. New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.3.2.1 include: diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx index 854c3da8436..85917271d07 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx @@ -1,8 +1,12 @@ --- -title: "Version 42.2.24.1" +title: "EDB JDBC Connector 42.2.24.1 release notes" +navTitle: Version 42.2.24.1 redirects: - ../01_release_notes/ --- + +Released: 05 Nov 2021 + The EDB JDBC connector provides connectivity between a Java application and an Advanced Server database. New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.2.24.1 include: diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx index 36566fc5743..f95747e3d97 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 42.2.19.1" - +title: "EDB JDBC Connector 42.2.19.1 release notes" +navTitle: Version 42.2.19.1 --- + +Released: 15 Apr 2021 + The EDB JDBC connector provides connectivity between a Java application and an Advanced Server database. New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.2.19.1 include: diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx index 5e682c39e4c..9fa2960e777 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx @@ -1,12 +1,13 @@ --- -title: "Version 42.2.12.3" - +title: "EDB JDBC Connector 42.2.12.3 release notes" +navTitle: Version 42.2.12.3 legacyRedirects: - - "/edb-docs/d/jdbc-connector/user-guides/jdbc-guide/42.2.12.3/whats_new.html" - "/edb-docs/d/jdbc-connector/user-guides/jdbc-guide/42.2.12.1/whats_new.html" --- +Released: 22 Oct 2020 + The EDB JDBC connector provides connectivity between a Java application and an Advanced Server database. New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.2.12.3 include: diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx index 1dd79831650..5748249390c 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx @@ -1,8 +1,10 @@ --- -title: "Version 42.2.9.1" - +title: "EDB JDBC Connector 42.2.9.1 release notes" +navTitle: Version 42.2.9.1 --- +Released: 18 May 2020 + The EDB JDBC connector provides connectivity between a Java application and an Advanced Server database. New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.2.9.1 include: diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx index 82d7729d67a..63b2266768b 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx @@ -1,8 +1,10 @@ --- -title: "Version 42.2.8.1" - +title: "EDB JDBC Connector 42.2.8.1 release notes" +navTitle: Version 42.2.8.1 --- +Released: 21 Oct 2019 + The EDB JDBC connector provides connectivity between a Java application and an Advanced Server database. New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.2.8.1 include: diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx index cec7d145e20..c000a77a053 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx @@ -1,8 +1,10 @@ --- -title: "Version 42.5.0.1" - +title: "EDB JDBC Connector 42.5.0.1 release notes" +navTitle: Version 42.5.0.1 --- +Released: 01 Sep 2022 + The EDB JDBC connector provides connectivity between a Java application and an EDB Postgres Advanced Server database. New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.5.0.1 include: diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx index 91b965fde07..76dd70a8c0e 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx @@ -1,8 +1,10 @@ --- -title: "Version 42.5.1.1" - +title: "EDB JDBC Connector 42.5.1.1 release notes" +navTitle: Version 42.5.1.1 --- +Released: 09 Dec 2022 + The EDB JDBC connector provides connectivity between a Java application and an EDB Postgres Advanced Server database. New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.5.1.1 include: diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx index 17c739387ab..a51ed328a47 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx @@ -1,8 +1,10 @@ --- -title: "Version 42.5.1.2" - +title: "EDB JDBC Connector 42.5.1.2 release notes" +navTitle: Version 42.5.1.2 --- +Released: 14 Feb 2023 + The EDB JDBC connector provides connectivity between a Java application and an EDB Postgres Advanced Server database. New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.5.1.2 include: diff --git a/product_docs/docs/ocl_connector/15/ocl_rel_notes/01_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/15/ocl_rel_notes/01_ocl_release_notes.mdx index 09806e49d0a..60332c5be88 100644 --- a/product_docs/docs/ocl_connector/15/ocl_rel_notes/01_ocl_release_notes.mdx +++ b/product_docs/docs/ocl_connector/15/ocl_rel_notes/01_ocl_release_notes.mdx @@ -1,6 +1,10 @@ --- -title: "Version 15.2.0.1" +title: "EDB OCL Connector 15.2.0.1 release notes" +navTitle: Version 15.2.0.1 --- + +Released: 14 Feb 2023 + The EDB OCL Connector provides an API similar to the Oracle Call Interface. New features, enhancements, bug fixes, and other changes in the EDB OCL Connector 15.2.0.1 include: diff --git a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.2_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.2_ocl_release_notes.mdx index f9e48f1f124..2bb98625633 100644 --- a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.2_ocl_release_notes.mdx +++ b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.2_ocl_release_notes.mdx @@ -1,6 +1,10 @@ --- -title: "Version 15.2.0.2" +title: "EDB OCL Connector 15.2.0.2 release notes" +navTitle: Version 15.2.0.2 --- + +Released: 19 May 2023 + The EDB OCL Connector provides an API similar to the Oracle Call Interface. New features, enhancements, bug fixes, and other changes in the EDB OCL Connector 15.2.0.2 include: diff --git a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.3_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.3_ocl_release_notes.mdx index 3c6be87f6ea..a9a6b5c0b22 100644 --- a/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.3_ocl_release_notes.mdx +++ b/product_docs/docs/ocl_connector/15/ocl_rel_notes/15.2.0.3_ocl_release_notes.mdx @@ -1,6 +1,10 @@ --- -title: "Version 15.2.0.3" +title: "EDB OCL Connector 15.2.0.3 release notes" +navTitle: Version 15.2.0.3 --- + +Released: 20 Jun 2023 + The EDB OCL Connector provides an API similar to the Oracle Call Interface. New features, enhancements, bug fixes, and other changes in the EDB OCL Connector 15.2.0.3 include: diff --git a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/02_odbc_13.2.0.01_rel_notes.mdx b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/02_odbc_13.2.0.01_rel_notes.mdx index 9326446a475..f65bbcb2ccd 100644 --- a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/02_odbc_13.2.0.01_rel_notes.mdx +++ b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/02_odbc_13.2.0.01_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 13.02.0000.01" +title: "EDB ODBC Connector 13.02.0000.01 release notes" +navTitle: Version 13.02.0000.01 --- +Released: 17 May 2022 + EDB ODBC Connector 13.02.0000.01 includes the following enhancement: | Type | Description | diff --git a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/03_odbc_13.1.0.02_rel_notes.mdx b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/03_odbc_13.1.0.02_rel_notes.mdx index df7fba9ab4e..4582c51f493 100644 --- a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/03_odbc_13.1.0.02_rel_notes.mdx +++ b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/03_odbc_13.1.0.02_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 13.01.0000.02" +title: "EDB ODBC Connector 13.01.0000.02 release notes" +navTitle: Version 13.01.0000.02 --- +Released: 12 Dec 2021 + EDB ODBC Connector 13.01.0000.02 includes the following enhancement: | Type | Description | diff --git a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/04_odbc_13.1.0.01_rel_notes.mdx b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/04_odbc_13.1.0.01_rel_notes.mdx index 229c53b5728..c13b9b10a32 100644 --- a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/04_odbc_13.1.0.01_rel_notes.mdx +++ b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/04_odbc_13.1.0.01_rel_notes.mdx @@ -1,8 +1,10 @@ --- -title: "Version 13.01.0000.01" - +title: "EDB ODBC Connector 13.01.0000.01 release notes" +navTitle: Version 13.01.0000.01 --- +Released: 14 Sep 2021 + EDB ODBC Connector 13.01.0000.01 includes the following upstream merge: | Type | Description | diff --git a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/05_odbc_13.0.0.01_rel_notes.mdx b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/05_odbc_13.0.0.01_rel_notes.mdx index d4e6a91a005..658242035cc 100644 --- a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/05_odbc_13.0.0.01_rel_notes.mdx +++ b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/05_odbc_13.0.0.01_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 13.00.0000.01" +title: "EDB ODBC Connector 13.00.0000.01 release notes" +navTitle: Version 13.00.0000.01 --- +Released: 19 Nov 2020 + EDB ODBC Connector 13.00.0000.01 includes the following upstream merge: | Type | Description | From b5a2430a9762fd5e704c9dd9bc426bf48c2a829d Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 27 Sep 2023 10:24:40 -0400 Subject: [PATCH 173/255] New titles and dates for p-products --- .../pgbouncer/1/pgbouncer_rel_notes/07_11800_rel_notes.mdx | 5 ++++- .../pgbouncer/1/pgbouncer_rel_notes/08_11700_rel_notes.mdx | 5 ++++- .../pgbouncer/1/pgbouncer_rel_notes/09_11610_rel_notes.mdx | 5 ++++- .../pgbouncer/1/pgbouncer_rel_notes/10_11601_rel_notes.mdx | 5 ++++- .../docs/pgpool/4/pgpool_rel_notes/07_432_rel_notes.mdx | 4 +++- .../docs/pgpool/4/pgpool_rel_notes/08_430_rel_notes.mdx | 4 +++- .../docs/pgpool/4/pgpool_rel_notes/09_426_rel_notes.mdx | 4 +++- .../docs/pgpool/4/pgpool_rel_notes/10_425_rel_notes.mdx | 5 ++++- .../docs/pgpool/4/pgpool_rel_notes/3724_rel_notes.mdx | 4 +++- .../docs/pgpool/4/pgpool_rel_notes/4019_rel_notes.mdx | 4 +++- .../docs/pgpool/4/pgpool_rel_notes/4112_rel_notes.mdx | 4 +++- .../docs/pgpool/4/pgpool_rel_notes/429_rel_notes.mdx | 4 +++- 12 files changed, 41 insertions(+), 12 deletions(-) diff --git a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/07_11800_rel_notes.mdx b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/07_11800_rel_notes.mdx index c6b0c2411e8..e6f92fecd55 100644 --- a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/07_11800_rel_notes.mdx +++ b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/07_11800_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 1.18.0.0" +title: "EDB PgBouncer 1.18.0.0 release notes" +navTitle: Version 1.18.0.0 --- +Released: 14 Feb 2023 + EDB PgBouncer 1.18.0.0 includes the following upstream merge and security fix: | Type | Description | diff --git a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/08_11700_rel_notes.mdx b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/08_11700_rel_notes.mdx index 47e48beb292..329e68b7356 100644 --- a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/08_11700_rel_notes.mdx +++ b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/08_11700_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 1.17.0.0" +title: "EDB PgBouncer 1.17.0.0 release notes" +navTitle: Version 1.17.0.0 --- +Released: 04 Aug 2022 + EDB PgBouncer 1.17.0.0 includes the following upstream merge and security fix: | Type | Description | diff --git a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/09_11610_rel_notes.mdx b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/09_11610_rel_notes.mdx index 86f3be167c8..06340cff94e 100644 --- a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/09_11610_rel_notes.mdx +++ b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/09_11610_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 1.16.1.0" +title: "EDB PgBouncer 1.16.0.0 release notes" +navTitle: Version 1.16.0.0 --- +Released: 11 Dec 2021 + EDB PgBouncer 1.16.1.0 includes the following upstream merge and security fix: | Type | Description | diff --git a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/10_11601_rel_notes.mdx b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/10_11601_rel_notes.mdx index 9e84c38d49f..17c5d0f44e2 100644 --- a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/10_11601_rel_notes.mdx +++ b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/10_11601_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 1.16.0.1" +title: "EDB PgBouncer 1.16.0.1 release notes" +navTitle: Version 1.16.0.1 --- +Released: 10 Jun 2021 + New features, enhancements, bug fixes, and other changes in EDB PgBouncer 1.16.0.1 include the following: | Type | Description | diff --git a/product_docs/docs/pgpool/4/pgpool_rel_notes/07_432_rel_notes.mdx b/product_docs/docs/pgpool/4/pgpool_rel_notes/07_432_rel_notes.mdx index f76826b5c81..e8452b854e6 100644 --- a/product_docs/docs/pgpool/4/pgpool_rel_notes/07_432_rel_notes.mdx +++ b/product_docs/docs/pgpool/4/pgpool_rel_notes/07_432_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 4.3.2" +title: "EDB PgPool-II 4.3.2 release notes" +navTitle: Version 4.3.2 --- +Released: 05 Jul 2022 EDB Pgpool-II 4.3.2 includes the following upstream merge: diff --git a/product_docs/docs/pgpool/4/pgpool_rel_notes/08_430_rel_notes.mdx b/product_docs/docs/pgpool/4/pgpool_rel_notes/08_430_rel_notes.mdx index 133e1fc6c45..c2076c0dcd6 100644 --- a/product_docs/docs/pgpool/4/pgpool_rel_notes/08_430_rel_notes.mdx +++ b/product_docs/docs/pgpool/4/pgpool_rel_notes/08_430_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 4.3.0" +title: "EDB PgPool-II 4.3.0 release notes" +navTitle: Version 4.3.0 --- +Released: 01 Feb 2022 EDB Pgpool-II 4.3.0 includes the following upstream merge and updates: diff --git a/product_docs/docs/pgpool/4/pgpool_rel_notes/09_426_rel_notes.mdx b/product_docs/docs/pgpool/4/pgpool_rel_notes/09_426_rel_notes.mdx index 4dd52dba92d..1988a4ceedb 100644 --- a/product_docs/docs/pgpool/4/pgpool_rel_notes/09_426_rel_notes.mdx +++ b/product_docs/docs/pgpool/4/pgpool_rel_notes/09_426_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 4.2.6" +title: "EDB PgPool-II 4.2.6 release notes" +navTitle: Version 4.2.6 --- +Released: 01 Dec 2021 EDB Pgpool-II 4.2.6 includes the following upstream merge and security fix: diff --git a/product_docs/docs/pgpool/4/pgpool_rel_notes/10_425_rel_notes.mdx b/product_docs/docs/pgpool/4/pgpool_rel_notes/10_425_rel_notes.mdx index ff585958f27..6b6c1e9c67a 100644 --- a/product_docs/docs/pgpool/4/pgpool_rel_notes/10_425_rel_notes.mdx +++ b/product_docs/docs/pgpool/4/pgpool_rel_notes/10_425_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 4.2.5" +title: "EDB PgPool-II 4.2.5 release notes" +navTitle: Version 4.2.5 --- +Released: 10 Jun 2021 + EDB Pgpool-II 4.2.5 includes the following upstream merges and bug fixes: | Type | Description | diff --git a/product_docs/docs/pgpool/4/pgpool_rel_notes/3724_rel_notes.mdx b/product_docs/docs/pgpool/4/pgpool_rel_notes/3724_rel_notes.mdx index 10e1795a5d5..1ebbcdd59aa 100644 --- a/product_docs/docs/pgpool/4/pgpool_rel_notes/3724_rel_notes.mdx +++ b/product_docs/docs/pgpool/4/pgpool_rel_notes/3724_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 3.7.24" +title: "EDB PgPool-II 3.7.24 release notes" +navTitle: Version 3.7.24 --- +Released: 05 Jul 2022 EDB Pgpool-II 3.7.24 includes the following upstream merge: diff --git a/product_docs/docs/pgpool/4/pgpool_rel_notes/4019_rel_notes.mdx b/product_docs/docs/pgpool/4/pgpool_rel_notes/4019_rel_notes.mdx index 920627494b5..f3e51705924 100644 --- a/product_docs/docs/pgpool/4/pgpool_rel_notes/4019_rel_notes.mdx +++ b/product_docs/docs/pgpool/4/pgpool_rel_notes/4019_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 4.0.19" +title: "EDB PgPool-II 4.0.19 release notes" +navTitle: Version 4.0.19 --- +Released: 05 Jul 2022 EDB Pgpool-II 4.0.19 includes the following upstream merge: diff --git a/product_docs/docs/pgpool/4/pgpool_rel_notes/4112_rel_notes.mdx b/product_docs/docs/pgpool/4/pgpool_rel_notes/4112_rel_notes.mdx index 2431e41d280..4d816fca78c 100644 --- a/product_docs/docs/pgpool/4/pgpool_rel_notes/4112_rel_notes.mdx +++ b/product_docs/docs/pgpool/4/pgpool_rel_notes/4112_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 4.1.12" +title: "EDB PgPool-II 4.1.12 release notes" +navTitle: Version 4.1.12 --- +Released: 05 Jul 2022 EDB Pgpool-II 4.1.12 includes the following upstream merge: diff --git a/product_docs/docs/pgpool/4/pgpool_rel_notes/429_rel_notes.mdx b/product_docs/docs/pgpool/4/pgpool_rel_notes/429_rel_notes.mdx index 96cd3c23493..c5e53f0b0d5 100644 --- a/product_docs/docs/pgpool/4/pgpool_rel_notes/429_rel_notes.mdx +++ b/product_docs/docs/pgpool/4/pgpool_rel_notes/429_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 4.2.9" +title: "EDB PgPool-II 4.2.9 release notes" +navTitle: Version 4.2.9 --- +Released: 05 Jul 2022 EDB Pgpool-II 4.2.9 includes the following upstream merge: From e8bc6cf948e0766e66d5a30be652f504b6a26c17 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 27 Sep 2023 10:47:14 -0400 Subject: [PATCH 174/255] new titles and dates for FDW products --- .../2/hadoop_rel_notes/hadoop_rel_notes_2.0.4.mdx | 5 ++++- .../2/hadoop_rel_notes/hadoop_rel_notes_2.0.5.mdx | 5 ++++- .../2/hadoop_rel_notes/hadoop_rel_notes_2.0.7.mdx | 4 +++- .../2/hadoop_rel_notes/hadoop_rel_notes_2.0.8.mdx | 4 +++- .../2/hadoop_rel_notes/hadoop_rel_notes_2.1.0.mdx | 5 ++++- .../2/hadoop_rel_notes/hadoop_rel_notes_2.2.0.mdx | 5 ++++- .../2/hadoop_rel_notes/hadoop_rel_notes_2.3.0.mdx | 5 ++++- .../5/mongo_rel_notes/mongo5.2.3_rel_notes.mdx | 5 ++++- .../5/mongo_rel_notes/mongo5.2.6_rel_notes.mdx | 5 ++++- .../5/mongo_rel_notes/mongo5.2.8_rel_notes.mdx | 5 ++++- .../5/mongo_rel_notes/mongo5.2.9_rel_notes.mdx | 5 ++++- .../5/mongo_rel_notes/mongo5.3.0_rel_notes.mdx | 5 ++++- .../5/mongo_rel_notes/mongo5.4.0_rel_notes.mdx | 5 ++++- .../5/mongo_rel_notes/mongo5.5.0_rel_notes.mdx | 5 ++++- .../2/mysql_rel_notes/mysql2.5.1_rel_notes.mdx | 4 +++- .../2/mysql_rel_notes/mysql2.5.3_rel_notes.mdx | 4 +++- .../2/mysql_rel_notes/mysql2.5.5_rel_notes.mdx | 4 +++- .../2/mysql_rel_notes/mysql2.6.0_rel_notes.mdx | 4 +++- .../2/mysql_rel_notes/mysql2.7.0_rel_notes.mdx | 4 +++- .../2/mysql_rel_notes/mysql2.8.0_rel_notes.mdx | 4 +++- .../2/mysql_rel_notes/mysql2.9.0_rel_notes.mdx | 4 +++- 21 files changed, 75 insertions(+), 21 deletions(-) diff --git a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.4.mdx b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.4.mdx index f82b3072512..27cc51c8c7c 100644 --- a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.4.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.4.mdx @@ -1,7 +1,10 @@ --- -title: "Version 2.0.4" +title: "Hadoop Foreign Data Wrapper 2.0.4 release notes" +navTitle: Version 2.0.4 --- +Released: 28 Nov 2018 + Enhancements, bug fixes, and other changes in Hadoop Foreign Data Wrapper 2.0.4 include: | Type | Description | diff --git a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.5.mdx b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.5.mdx index 1d1c34c5db3..dff99f440f1 100644 --- a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.5.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.5.mdx @@ -1,7 +1,10 @@ --- -title: "Version 2.0.5" +title: "Hadoop Foreign Data Wrapper 2.0.5 release notes" +navTitle: Version 2.0.5 --- +Released: 10 Dec 2019 + Enhancements, bug fixes, and other changes in Hadoop Foreign Data Wrapper 2.0.5 include: | Type | Description | diff --git a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.7.mdx b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.7.mdx index 71142180a98..5af9ac1fa57 100644 --- a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.7.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.7.mdx @@ -1,7 +1,9 @@ --- -title: "Version 2.0.7" +title: "Hadoop Foreign Data Wrapper 2.0.7 release notes" +navTitle: Version 2.0.7 --- +Released: 23 Nov 2020 New features, enhancements, bug fixes, and other changes in Hadoop Foreign Data Wrapper 2.0.7 include the following: diff --git a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.8.mdx b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.8.mdx index 5b3c48a7617..dc4307f0744 100644 --- a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.8.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.0.8.mdx @@ -1,7 +1,9 @@ --- -title: "Version 2.0.8" +title: "Hadoop Foreign Data Wrapper 2.0.8 release notes" +navTitle: Version 2.0.8 --- +Released: 24 Jun 2021 New features, enhancements, bug fixes, and other changes in Hadoop Foreign Data Wrapper 2.0.8 include the following: diff --git a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.1.0.mdx b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.1.0.mdx index 996c8f4e589..37dd80a2096 100644 --- a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.1.0.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.1.0.mdx @@ -1,7 +1,10 @@ --- -title: "Version 2.1.0" +title: "Hadoop Foreign Data Wrapper 2.1.0 release notes" +navTitle: Version 2.1.0 --- +Released: 02 Dec 2021 + Enhancements, bug fixes, and other changes in Hadoop Foreign Data Wrapper 2.1.0 include: | Type | Description | diff --git a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.2.0.mdx b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.2.0.mdx index 87c40a5d243..daeabb74e86 100644 --- a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.2.0.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.2.0.mdx @@ -1,7 +1,10 @@ --- -title: "Version 2.2.0" +title: "Hadoop Foreign Data Wrapper 2.2.0 release notes" +navTitle: Version 2.2.0 --- +Released: 26 May 2022 + Enhancements, bug fixes, and other changes in Hadoop Foreign Data Wrapper 2.2 include: | Type | Description | diff --git a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.3.0.mdx b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.3.0.mdx index 3401bc99c37..93760451d6d 100644 --- a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.3.0.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.3.0.mdx @@ -1,7 +1,10 @@ --- -title: "Version 2.3.0" +title: "Hadoop Foreign Data Wrapper 2.3.0 release notes" +navTitle: Version 2.3.0 --- +Released: 06 Jan 2023 + Enhancements, bug fixes, and other changes in Hadoop Foreign Data Wrapper 2.3 include: | Type | Description | diff --git a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.3_rel_notes.mdx b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.3_rel_notes.mdx index 6cbdc8e7dc2..a3e53c7de91 100644 --- a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.3_rel_notes.mdx +++ b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.3_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 5.2.3" +title: "MongoDB Foreign Data Wrapper 5.2.3 release notes" +navTitle: Version 5.2.3 --- +Released: 01 Nov 2018 + Enhancements, bug fixes, and other changes in MongoDB Foreign Data Wrapper 5.2.3 include: diff --git a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.6_rel_notes.mdx b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.6_rel_notes.mdx index 356059c664b..1ecfe6a4437 100644 --- a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.6_rel_notes.mdx +++ b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.6_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 5.2.6" +title: "MongoDB Foreign Data Wrapper 5.2.6 release notes" +navTitle: Version 5.2.6 --- +Released: 27 Sep 2019 + Enhancements, bug fixes, and other changes in MongoDB Foreign Data Wrapper 5.2.6 include: diff --git a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.8_rel_notes.mdx b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.8_rel_notes.mdx index d8613fc8c8a..e3b15af520d 100644 --- a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.8_rel_notes.mdx +++ b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.8_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 5.2.8" +title: "MongoDB Foreign Data Wrapper 5.2.8 release notes" +navTitle: Version 5.2.8 --- +Released: 23 Nov 2020 + New features, enhancements, bug fixes, and other changes in Mongo Foreign Data Wrapper 5.2.8 include: | Type | Description | diff --git a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.9_rel_notes.mdx b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.9_rel_notes.mdx index 7b3baf98ec1..8bbfaac82d2 100644 --- a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.9_rel_notes.mdx +++ b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.2.9_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 5.2.9" +title: "MongoDB Foreign Data Wrapper 5.2.9 release notes" +navTitle: Version 5.2.9 --- +Released: 24 Jun 2021 + New features, enhancements, bug fixes, and other changes in Mongo Foreign Data Wrapper 5.2.9 include: | Type | Description | diff --git a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.3.0_rel_notes.mdx b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.3.0_rel_notes.mdx index 6ffa1b667b3..cc3c6bc0629 100644 --- a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.3.0_rel_notes.mdx +++ b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.3.0_rel_notes.mdx @@ -1,9 +1,12 @@ --- -title: "Version 5.3.0" +title: "MongoDB Foreign Data Wrapper 5.3.0 release notes" +navTitle: Version 5.3.0 redirects: - 01_5.3.0_rel_notes --- +Released: 02 Dec 2021 + Enhancements, bug fixes, and other changes in MongoDB Foreign Data Wrapper 5.3.0 include: diff --git a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.4.0_rel_notes.mdx b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.4.0_rel_notes.mdx index f980c2179d6..682b7768d3a 100644 --- a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.4.0_rel_notes.mdx +++ b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.4.0_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 5.4.0" +title: "MongoDB Foreign Data Wrapper 5.4.0 release notes" +navTitle: Version 5.4.0 --- +Released: 26 May 2022 + Enhancements, bug fixes, and other changes in MongoDB Foreign Data Wrapper 5.4.0 include: diff --git a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.5.0_rel_notes.mdx b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.5.0_rel_notes.mdx index b7d33fe1d96..c9f980cf571 100644 --- a/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.5.0_rel_notes.mdx +++ b/product_docs/docs/mongo_data_adapter/5/mongo_rel_notes/mongo5.5.0_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 5.5.0" +title: "MongoDB Foreign Data Wrapper 5.5.0 release notes" +navTitle: Version 5.5.0 --- +Released: 06 Jan 2023 + Enhancements, bug fixes, and other changes in MongoDB Foreign Data Wrapper 5.5.0 include: diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.1_rel_notes.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.1_rel_notes.mdx index f8d483f405a..924c537f03e 100644 --- a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.1_rel_notes.mdx +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.1_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 2.5.1" +title: "MySQL Foreign Data Wrapper 2.5.1 release notes" +navTitle: Version 2.5.1 --- +Released: 28 Nov 2018 Enhancements, bug fixes, and other changes in MySQL Foreign Data Wrapper 2.5.1 include: diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.3_rel_notes.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.3_rel_notes.mdx index cf0f35b9df9..be1cf82432e 100644 --- a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.3_rel_notes.mdx +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.3_rel_notes.mdx @@ -1,9 +1,11 @@ --- -title: "Version 2.5.3" +title: "MySQL Foreign Data Wrapper 2.5.3 release notes" +navTitle: Version 2.5.3 redirects: - 01_rel_notes --- +Released: 10 Dec 2019 Enhancements, bug fixes, and other changes in MySQL Foreign Data Wrapper 2.5.3 include: diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.5_rel_notes.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.5_rel_notes.mdx index 0d1c42b1772..d9cbd3ba844 100644 --- a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.5_rel_notes.mdx +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.5_rel_notes.mdx @@ -1,9 +1,11 @@ --- -title: "Version 2.5.5" +title: "MySQL Foreign Data Wrapper 2.5.5 release notes" +navTitle: Version 2.5.5 redirects: - 01_rel_notes --- +Released: 23 Nov 2020 Enhancements, bug fixes, and other changes in MySQL Foreign Data Wrapper 2.5.5 include: diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.6.0_rel_notes.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.6.0_rel_notes.mdx index 79f2d4cec51..23732590d4f 100644 --- a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.6.0_rel_notes.mdx +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.6.0_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 2.6.0" +title: "MySQL Foreign Data Wrapper 2.6.0 release notes" +navTitle: Version 2.6.0 --- +Released: 18 May 2021 Enhancements, bug fixes, and other changes in MySQL Foreign Data Wrapper 2.6.0 include: diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.7.0_rel_notes.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.7.0_rel_notes.mdx index ecf7c071c05..560c304de5f 100644 --- a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.7.0_rel_notes.mdx +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.7.0_rel_notes.mdx @@ -1,9 +1,11 @@ --- -title: "Version 2.7.0" +title: "MySQL Foreign Data Wrapper 2.7.0 release notes" +navTitle: Version 2.7.0 redirects: - 01_rel_notes --- +Released: 02 Dec 2021 Enhancements, bug fixes, and other changes in MySQL Foreign Data Wrapper 2.7.0 include: diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.8.0_rel_notes.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.8.0_rel_notes.mdx index 45c9027f753..4d912a07240 100644 --- a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.8.0_rel_notes.mdx +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.8.0_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 2.8.0" +title: "MySQL Foreign Data Wrapper 2.8.0 release notes" +navTitle: Version 2.8.0 --- +Released: 26 May 2022 Enhancements, bug fixes, and other changes in MySQL Foreign Data Wrapper 2.8.0 include: diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.9.0_rel_notes.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.9.0_rel_notes.mdx index 147c8a6f519..45b9ed0ba96 100644 --- a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.9.0_rel_notes.mdx +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.9.0_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 2.9.0" +title: "MySQL Foreign Data Wrapper 2.9.0 release notes" +navTitle: Version 2.9.0 --- +Released: 06 Jan 2023 Enhancements, bug fixes, and other changes in MySQL Foreign Data Wrapper 2.9.0 include: From 7b07a3685f1c4d465f0819896e951c3556142dc9 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 27 Sep 2023 11:38:47 -0400 Subject: [PATCH 175/255] New titles and dates for migration products --- .../docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx | 4 +++- .../docs/eprs/7/eprs_rel_notes/16_eprs_rel_notes_7.2.1.mdx | 4 +++- .../docs/eprs/7/eprs_rel_notes/17_eprs_rel_notes_7.2.0.mdx | 4 +++- .../docs/eprs/7/eprs_rel_notes/18_eprs_rel_notes_7.1.0.mdx | 4 +++- .../docs/eprs/7/eprs_rel_notes/19_eprs_rel_notes_7.0.1.mdx | 4 +++- .../docs/eprs/7/eprs_rel_notes/20_eprs_rel_notes_7.0.0.mdx | 5 ++++- .../docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.4.0.mdx | 4 +++- .../docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.5.0.mdx | 4 +++- .../docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.5.1.mdx | 4 +++- .../docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.6.0.mdx | 4 ++-- .../4/01_mp_release_notes/10_mp_4.0_rel_notes.mdx | 4 +++- .../4/01_mp_release_notes/mp_4.1_rel_notes.mdx | 4 +++- .../4/01_mp_release_notes/mp_4.2_rel_notes.mdx | 4 +++- .../4/01_mp_release_notes/mp_4.3_rel_notes.mdx | 4 +++- .../4/01_mp_release_notes/mp_4.4_rel_notes.mdx | 4 +++- .../4/01_mp_release_notes/mp_4.5.1_rel_notes.mdx | 1 - .../4/01_mp_release_notes/mp_4.5_rel_notes.mdx | 4 +++- .../55/mtk_rel_notes/05_mkt_5522_rel_notes.mdx | 5 ++++- .../55/mtk_rel_notes/06_mkt_5521_rel_notes.mdx | 5 ++++- .../55/mtk_rel_notes/07_mkt_552_rel_notes.mdx | 5 ++++- .../55/mtk_rel_notes/08_mkt_551_rel_notes.mdx | 5 ++++- .../55/mtk_rel_notes/09_mkt_55_rel_notes.mdx | 5 ++++- .../55/mtk_rel_notes/mtk_5523_rel_notes.mdx | 5 ++++- .../migration_toolkit/55/mtk_rel_notes/mtk_553_rel_notes.mdx | 5 ++++- .../migration_toolkit/55/mtk_rel_notes/mtk_554_rel_notes.mdx | 5 ++++- .../migration_toolkit/55/mtk_rel_notes/mtk_555_rel_notes.mdx | 5 ++++- .../migration_toolkit/55/mtk_rel_notes/mtk_556_rel_notes.mdx | 4 ++++ 27 files changed, 88 insertions(+), 27 deletions(-) diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx index c2704f54049..392fd913bc3 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx @@ -1,7 +1,9 @@ --- -title: "Version 7.3.0" +title: "Replication Server 7.3.0 release notes" +navTitle: Version 7.3.0 --- +Released: 15 Nov 2022 New features, enhancements, bug fixes, and other changes in Replication Server 7.3.0 include the following: diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/16_eprs_rel_notes_7.2.1.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/16_eprs_rel_notes_7.2.1.mdx index 109f22b36a8..c2c00b52340 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/16_eprs_rel_notes_7.2.1.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/16_eprs_rel_notes_7.2.1.mdx @@ -1,7 +1,9 @@ --- -title: "Version 7.2.1" +title: "Replication Server 7.2.1 release notes" +navTitle: Version 7.2.1 --- +Released: 25 Jul 2022 New features, enhancements, bug fixes, and other changes in Replication Server 7.2.1 include the following: diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/17_eprs_rel_notes_7.2.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/17_eprs_rel_notes_7.2.0.mdx index 60c14028791..0afa9b5c4ea 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/17_eprs_rel_notes_7.2.0.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/17_eprs_rel_notes_7.2.0.mdx @@ -1,7 +1,9 @@ --- -title: "Version 7.2.0" +title: "Replication Server 7.2.0 release notes" +navTitle: Version 7.2.0 --- +Released: 24 Jun 2022 New features, enhancements, bug fixes, and other changes in Replication Server 7.2.0 include the following: diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/18_eprs_rel_notes_7.1.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/18_eprs_rel_notes_7.1.0.mdx index a4c8b8e0b29..1834a3e5bd4 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/18_eprs_rel_notes_7.1.0.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/18_eprs_rel_notes_7.1.0.mdx @@ -1,7 +1,9 @@ --- -title: "Version 7.1.0" +title: "Replication Server 7.1.0 release notes" +navTitle: Version 7.1.0 --- +Released: 21 Mar 2022 New features, enhancements, bug fixes, and other changes in Replication Server 7.1.0 include the following: diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/19_eprs_rel_notes_7.0.1.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/19_eprs_rel_notes_7.0.1.mdx index da7e8161a19..a12ba0d9521 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/19_eprs_rel_notes_7.0.1.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/19_eprs_rel_notes_7.0.1.mdx @@ -1,7 +1,9 @@ --- -title: "Version 7.0.1" +title: "Replication Server 7.0.1 release notes" +navTitle: Version 7.0.1 --- +Released: 03 Mar 2022 New features, enhancements, bug fixes, and other changes in Replication Server 7.0.1 include the following: diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/20_eprs_rel_notes_7.0.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/20_eprs_rel_notes_7.0.0.mdx index 6ec2d689652..6908e1f19f3 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/20_eprs_rel_notes_7.0.0.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/20_eprs_rel_notes_7.0.0.mdx @@ -1,9 +1,12 @@ --- -title: "Version 7.0.0" +title: "Replication Server 7.0.0 release notes" +navTitle: Version 7.0.0 redirects: - ../01_whats_new/ --- +Released: 01 Dec 2021 + !!! Note The 7.0 version is backward compatible with 6.2.x and provides a non-breaking upgrade path for the existing cluster deployments. However, it is strongly recommended to verify it in a staging or nonproduction environment before applying the upgrade in a production environment. diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.4.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.4.0.mdx index c83d8fb32ae..5cf8be4d2c4 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.4.0.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.4.0.mdx @@ -1,7 +1,9 @@ --- -title: "Version 7.4.0" +title: "Replication Server 7.4.0 release notes" +navTitle: Version 7.4.0 --- +Released: 29 Nov 2022 New features, enhancements, bug fixes, and other changes in Replication Server 7.4.0 include the following: diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.5.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.5.0.mdx index 9f6d2ddec6e..695ed7c7eaf 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.5.0.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.5.0.mdx @@ -1,7 +1,9 @@ --- -title: "Version 7.5.0" +title: "Replication Server 7.5.0 release notes" +navTitle: Version 7.5.0 --- +Released: 14 Feb 2023 New features, enhancements, bug fixes, and other changes in Replication Server 7.5.0 include the following: diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.5.1.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.5.1.mdx index 43396d364f4..83190aa9675 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.5.1.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.5.1.mdx @@ -1,7 +1,9 @@ --- -title: "Version 7.5.1" +title: "Replication Server 7.5.1 release notes" +navTitle: Version 7.5.1 --- +Released: 26 May 2023 New features, enhancements, bug fixes, and other changes in Replication Server 7.5.1 include the following: 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 index 184dded1bb5..d5962c59151 100644 --- 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 @@ -1,6 +1,6 @@ --- -title: Replication Server 7.6.0 release notes -navTitle: "Version 7.6.0" +title: "Replication Server 7.6.0 release notes" +navTitle: Version 7.6.0 --- Released: 07 Sep 2023 diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/10_mp_4.0_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/10_mp_4.0_rel_notes.mdx index da7b858247b..f4650bb85b5 100644 --- a/product_docs/docs/migration_portal/4/01_mp_release_notes/10_mp_4.0_rel_notes.mdx +++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/10_mp_4.0_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 4.0" +title: "Migration Portal 4.0 release notes" +navTitle: Version 4.0 --- +Released: 22 Apr 2022 New features, enhancements, bug fixes, and other changes in Migration Portal 4.0 include the following: diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.1_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.1_rel_notes.mdx index 9e610bd5bda..8409fbc0f6d 100644 --- a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.1_rel_notes.mdx +++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.1_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 4.1" +title: "Migration Portal 4.1 release notes" +navTitle: Version 4.1 --- +Released: 04 Aug 2022 New features, enhancements, bug fixes, and other changes in Migration Portal 4.1 include the following: diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.2_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.2_rel_notes.mdx index 95d943b4eae..f405c77d0d6 100644 --- a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.2_rel_notes.mdx +++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.2_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 4.2" +title: "Migration Portal 4.2 release notes" +navTitle: Version 4.2 --- +Released: 04 Oct 2022 New features, enhancements, bug fixes, and other changes in Migration Portal 4.2 include the following: diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.3_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.3_rel_notes.mdx index f8353624670..ff626057a91 100644 --- a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.3_rel_notes.mdx +++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.3_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 4.3" +title: "Migration Portal 4.3 release notes" +navTitle: Version 4.3 --- +Released: 08 Dec 2022 New features, enhancements, bug fixes, and other changes in Migration Portal 4.3 include the following: diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.4_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.4_rel_notes.mdx index 15966e144ce..c614ff2ef13 100644 --- a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.4_rel_notes.mdx +++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.4_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 4.4" +title: "Migration Portal 4.4 release notes" +navTitle: Version 4.4 --- +Released: 14 Feb 2023 New features, enhancements, bug fixes, and other changes in Migration Portal 4.4 include the following: diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.1_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.1_rel_notes.mdx index 497cf44d406..24e8adc62a5 100644 --- a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.1_rel_notes.mdx +++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.1_rel_notes.mdx @@ -5,7 +5,6 @@ navTitle: Version 4.5.1 Released: 12 Jul 2023 - New features, enhancements, bug fixes, and other changes in Migration Portal 4.5.1 include the following: | Type | Description | diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5_rel_notes.mdx index 54c66219718..915539215d9 100644 --- a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5_rel_notes.mdx +++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5_rel_notes.mdx @@ -1,7 +1,9 @@ --- -title: "Version 4.5" +title: "Migration Portal 4.5 release notes" +navTitle: Version 4.5 --- +Released: 18 May 2023 New features, enhancements, bug fixes, and other changes in Migration Portal 4.5 include the following: diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/05_mkt_5522_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/05_mkt_5522_rel_notes.mdx index 9c73d70dbb7..c96982a1b2f 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/05_mkt_5522_rel_notes.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/05_mkt_5522_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 55.2.2" +title: "Migration Toolkit 55.2.2 release notes" +navTitle: Version 55.2.2 --- +Released: 10 Mar 2022 + New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.2.2 include: | Type | Description | diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/06_mkt_5521_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/06_mkt_5521_rel_notes.mdx index 665d8fedc97..1c5d149b8ea 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/06_mkt_5521_rel_notes.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/06_mkt_5521_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 55.2.1" +title: "Migration Toolkit 55.2.1 release notes" +navTitle: Version 55.2.1 --- +Released: 13 Jan 2022 + New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.2.1 include: | Type | Description | diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/07_mkt_552_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/07_mkt_552_rel_notes.mdx index 1a2ba6ff16d..6c65f240f41 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/07_mkt_552_rel_notes.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/07_mkt_552_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 55.2.0" +title: "Migration Toolkit 55.2.0 release notes" +navTitle: Version 55.2.0 --- +Released: 02 Dec 2021 + New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.2.0 include: | Type | Description | diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/08_mkt_551_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/08_mkt_551_rel_notes.mdx index a4eecc6282c..97fb72e466b 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/08_mkt_551_rel_notes.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/08_mkt_551_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 55.1.0" +title: "Migration Toolkit 55.1.0 release notes" +navTitle: Version 55.1.0 --- +Released: 20 Sep 2021 + New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.1.0 include: | Type | Description | diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/09_mkt_55_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/09_mkt_55_rel_notes.mdx index d846bd90297..dad64310a27 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/09_mkt_55_rel_notes.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/09_mkt_55_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 55.0.0" +title: "Migration Toolkit 55.0.0 release notes" +navTitle: Version 55.0.0 --- +Released: 19 Mar 2021 + New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.0.0 include: | Type | Description | diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_5523_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_5523_rel_notes.mdx index 40aee90c62c..27d87e634a5 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_5523_rel_notes.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_5523_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 55.2.3" +title: "Migration Toolkit 55.2.3 release notes" +navTitle: Version 55.2.3 --- +Released: 16 Jun 2022 + New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.2.3 include: | Type | Description | diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_553_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_553_rel_notes.mdx index a316d8b729d..201dacd59bc 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_553_rel_notes.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_553_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 55.3.0" +title: "Migration Toolkit 55.3.0 release notes" +navTitle: Version 55.3.0 --- +Released: 06 Oct 2022 + New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.3 include: | Type | Description | diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_554_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_554_rel_notes.mdx index 9a8262afb45..d4a10446651 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_554_rel_notes.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_554_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 55.4.0" +title: "Migration Toolkit 55.4.0 release notes" +navTitle: Version 55.4.0 --- +Released: 29 Nov 2022 + New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.4 include: | Type | Description | diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_555_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_555_rel_notes.mdx index 0e64e008244..10fd9776084 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_555_rel_notes.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_555_rel_notes.mdx @@ -1,7 +1,10 @@ --- -title: "Version 55.5.0" +title: "Migration Toolkit 55.5.0 release notes" +navTitle: Version 55.5.0 --- +Released: 14 Feb 2023 + New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.5 include: | Type | Description | diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_556_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_556_rel_notes.mdx index c1d357401ce..d757d45fc4b 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_556_rel_notes.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_556_rel_notes.mdx @@ -1,7 +1,11 @@ --- title: "Version 55.6.0" +title: "Migration Toolkit 55.6.0 release notes" +navTitle: Version 55.6.0 --- +Released: 25 May 2023 + New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.6 include: | Type | Description | From 31694c71aee146a9f0ca75faa61b0e63b854bbab Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Thu, 28 Sep 2023 10:09:36 +0100 Subject: [PATCH 176/255] Update edbplus_41.1_rel_notes.mdx Remove duplicate title. --- .../docs/edb_plus/41/02_release_notes/edbplus_41.1_rel_notes.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.1_rel_notes.mdx b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.1_rel_notes.mdx index d2b83b6c781..a17f6fc1e5d 100644 --- a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.1_rel_notes.mdx +++ b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.1_rel_notes.mdx @@ -1,5 +1,4 @@ --- -title: "Version 41.1.0" title: "EDB*Plus 41.1.0 release notes" navTitle: Version 41.1.0 --- From 26a731dccfdda9965ac0aa4299738d88d04aaea6 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Thu, 28 Sep 2023 10:12:45 +0100 Subject: [PATCH 177/255] Remove double title from mtk_556_rel_notes.mdx --- .../migration_toolkit/55/mtk_rel_notes/mtk_556_rel_notes.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_556_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_556_rel_notes.mdx index d757d45fc4b..a3adbb82789 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_556_rel_notes.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_556_rel_notes.mdx @@ -1,5 +1,4 @@ --- -title: "Version 55.6.0" title: "Migration Toolkit 55.6.0 release notes" navTitle: Version 55.6.0 --- From e602b3b67763e9685e78db969d629b679c50e3a9 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Thu, 28 Sep 2023 11:56:03 +0100 Subject: [PATCH 178/255] Close open note on admonition Open admonition! FENCE THEM PEOPLE! --- product_docs/docs/pgd/3.7/bdr/release-notes.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/3.7/bdr/release-notes.mdx b/product_docs/docs/pgd/3.7/bdr/release-notes.mdx index 6806efce768..ff46107a01b 100644 --- a/product_docs/docs/pgd/3.7/bdr/release-notes.mdx +++ b/product_docs/docs/pgd/3.7/bdr/release-notes.mdx @@ -108,7 +108,8 @@ Check also release notes for pglogical 3.7.20 for resolved issues that affect BDR as well. !!! Note - This version is required for EDB Postgres Advanced Server versions 12.14.18, 13.10.14, and later. +This version is required for EDB Postgres Advanced Server versions 12.14.18, 13.10.14, and later. +!!! ### Resolved issues From 65777ee5c9986c8267db5c5575c61dc19ba9ebf4 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Thu, 28 Sep 2023 09:00:40 -0400 Subject: [PATCH 179/255] valerio connecting from azure suggestion Co-authored-by: Valerio Del Sarto --- .../01_connecting_from_azure/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx index df19f823b59..3017ef0cfd5 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx @@ -33,7 +33,7 @@ When using BigAnimal's cloud account, when creating a cluster, you provide BigAn 1. After the cluster is created, go to the cluster details to see the corresponding endpoint service name. You need the service name while creating a private endpoint. -1. Create a private endpoint in the client's VPC. The steps for creating a private endpoint in the client's VPC are the same whether you're using BigAnimal's cloud or your own. See [Step 1: Create an Azure private endpoint](#step-1-create-an-azure-private-endpoint) and [Step 2: Create an Azure Private DNS Zone for the private endpoint](#step-2-create-an-azure-private-dns-zone-for-the-private-endpoint). +1. Create a private endpoint in the client's VNet. The steps for creating a private endpoint in the client's VNet are the same whether you're using BigAnimal's cloud or your own. See [Step 1: Create an Azure private endpoint](#step-1-create-an-azure-private-endpoint) and [Step 2: Create an Azure Private DNS Zone for the private endpoint](#step-2-create-an-azure-private-dns-zone-for-the-private-endpoint). 1. In your application's Azure account, select **Private Link Center**, and then select **Private endpoints**. Select the endpoint you created previously, and use the service name provided in the details section in BigAnimal to access your cluster. From f9022feb4331e15475a3c12cebeb2b7537fd206c Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 28 Sep 2023 10:20:45 -0400 Subject: [PATCH 180/255] Update 04-ConfiguringVeeamKasten.mdx --- .../partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx b/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx index 73fe4f893c4..c82440b2814 100644 --- a/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx +++ b/advocacy_docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten.mdx @@ -18,7 +18,7 @@ Implementing EDB Postgres for Kubernetes with Kasten by Veeam requires the follo !!! Note For this integration, use the `example.yaml` files provided for the appropriate Kasten configuration pieces, and change any environment variables per your specific needs. - [Add the backup decorator annotations to the cluster](#add-the-backup-decorator-annotations-to-the-cluster) is important for the Kasten add-on integration. + See [Add the backup decorator annotations to the cluster](#add-the-backup-decorator-annotations-to-the-cluster), which is important for the Kasten add-on integration. Refer to the [EDB Postgres for Kubernetes external backup adapter](/postgres_for_kubernetes/latest/addons/#external-backup-adapter) documentation for more detailed information on the EDB Postgres for Kubernetes backup adaptor add-on functionality and additional details on its configuraton parameters. From ebafcc17d1c97b7afd806dc6c42b4e355f6cd1e3 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 28 Sep 2023 14:47:41 -0400 Subject: [PATCH 181/255] Added regions per Jira ticket --- .../overview/03a_region_support/index.mdx | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx b/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx index cb1b41582ef..d13c7e96802 100644 --- a/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx +++ b/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx @@ -152,6 +152,30 @@ When using Google Cloud, you can create clusters in the following regions. ## BigAnimal's cloud account +### Azure regions + +When using Azure and BigAnimal's cloud account, you can create clusters in the following regions. + +#### North America (NA) + +| Cloud region | Short name | +| ------------------------ | -------------- | +| US East (Virginia) | eastus2 | +| Canada (Central) | canadacentral | + + +#### Asia and Pacific (APAC) + +| Cloud region | Short name | +| ------------------------ | -------------- | +| Asia Pacific (Mumbai) | india-west | + +#### Europe, Middle East, and Africa (EMEA) + +| Cloud region | Short name | +| ------------------ | ------------ | +| Europe (London) | uksouth | + ### AWS regions When using AWS and BigAnimal's cloud account, you can create clusters in the following regions. From 9ba5ce0a27b43ad6e5c28ad854b361682a113e86 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Fri, 29 Sep 2023 10:09:01 -0400 Subject: [PATCH 182/255] accessing Azure-BAH logs content changed section title changes to example --- .../monitoring_from_azure/index.mdx | 43 +++++++++++++++++++ 1 file changed, 43 insertions(+) diff --git a/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/monitoring_from_azure/index.mdx b/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/monitoring_from_azure/index.mdx index d47e765da01..4a1cf9800b0 100644 --- a/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/monitoring_from_azure/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/monitoring_from_azure/index.mdx @@ -53,6 +53,49 @@ PostgresAuditLogs_CL | project record_log_time_s, record_error_severity_s, record_message_s | sort by record_log_time_s desc ``` + +### Using BigAnimal's cloud account + +To access your Postgres cluster logs, when using BigAnimal's cloud account, generate a SAS token from BigAnimal and use it to download the logs. + +1. In the BigAnimal portal, select **Clusters**, select your cluster, and select the **Monitoring & Logging** tab. + +1. Select **Generate Token** and copy the SAS token. The SAS token is a sensitive value and shouldn't be made publicly available. The following is a sample SAS token: + + ``` + https://blobsamples.blob.core.windows.net/?sv=2022-11-02&ss=b&srt=sco&sp=rwlc&se=2023-05-24T09:51:36Z&st=2023-05-24T01:51:36Z&spr=https&sig= + ``` + +1. Enter the `azcopy` command to download the Postgres logs from BigAnimal. For example: + + ``` + azcopy copy '$TOKEN' . --recursive + INFO: Scanning... + INFO: Any empty folders will not be processed, because source and/or destination doesn't have full folder support + + Job aa4b74a0-bc92-be4e-551c-47aec1c1cfc3 has started + Log file is located at: /Users/sample_user/.azcopy/aa4b74a0-bc92-be4e-551c-47aec1c1cfc3.log + + 100.0 %, 5 Done, 0 Failed, 0 Pending, 0 Skipped, 5 Total, 2-sec Throughput (Mb/s): 0.5375 + + + Job aa4b74a0-bc92-be4e-551c-47aec1c1cfc3 summary + Elapsed Time (Minutes): 0.0333 + Number of File Transfers: 5 + Number of Folder Property Transfers: 0 + Number of Symlink Transfers: 0 + Total Number of Transfers: 5 + Number of File Transfers Completed: 5 + Number of Folder Transfers Completed: 0 + Number of File Transfers Failed: 0 + Number of Folder Transfers Failed: 0 + Number of File Transfers Skipped: 0 + Number of Folder Transfers Skipped: 0 + TotalBytesTransferred: 134416 + Final Job Status: Completed + $ tail p-a1b2c3d4d5/kubernetes-logs/p-a1b2c3d4d5/2023/09/26/13/19/azure_customer_postgresql_cluster.var.log.containers.p-a1b2c3d4d5-1_p-a1b2c3d4d5_postgres-c798aa19ea0481c8d9575f025405b3ad9212816ca7e928f997473055499a692c.log + {"@timestamp":"2023-09-26T13:19:19.572442Z","level":"info","ts":"2023-09-26T13:19:19Z","logger":"wal-archive","msg":"Archived WAL file","logging_pod":"p-a1b2c3d4d5-1","walName":"pg_wal/000000010000000000000006","startTime":"2023-09-26T13:19:18Z","endTime":"2023-09-26T13:19:19Z","elapsedWalTime":1.060413255,"stream":"stdout","logtag":"F","message":"{\"level\":\"info\",\"ts\":\"2023-09-26T13:19:19Z\",\"logger\":\"wal-archive\",\"msg\":\"Archived WAL + ``` ## Metrics From d18f3122efd6d1643ba04e853aff8c5b485f9b17 Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Thu, 21 Sep 2023 03:47:54 +0000 Subject: [PATCH 183/255] Update various dependencies. upgrade icons upgrade bootstrap upgrade husky --- .husky/_/husky.sh | 11 +- package-lock.json | 764 +++++++++++++++++++++++++----------------- package.json | 20 +- src/styles/_docs.scss | 2 +- 4 files changed, 473 insertions(+), 324 deletions(-) diff --git a/.husky/_/husky.sh b/.husky/_/husky.sh index 6809ccca285..cec959a6b9d 100644 --- a/.husky/_/husky.sh +++ b/.husky/_/husky.sh @@ -1,4 +1,4 @@ -#!/bin/sh +#!/usr/bin/env sh if [ -z "$husky_skip_init" ]; then debug () { if [ "$HUSKY_DEBUG" = "1" ]; then @@ -6,7 +6,7 @@ if [ -z "$husky_skip_init" ]; then fi } - readonly hook_name="$(basename "$0")" + readonly hook_name="$(basename -- "$0")" debug "starting $hook_name..." if [ "$HUSKY" = "0" ]; then @@ -19,7 +19,8 @@ if [ -z "$husky_skip_init" ]; then . ~/.huskyrc fi - export readonly husky_skip_init=1 + readonly husky_skip_init=1 + export husky_skip_init sh -e "$0" "$@" exitCode="$?" @@ -27,5 +28,9 @@ if [ -z "$husky_skip_init" ]; then echo "husky - $hook_name hook exited with code $exitCode (error)" fi + if [ $exitCode = 127 ]; then + echo "husky - command not found in PATH=$PATH" + fi + exit $exitCode fi diff --git a/package-lock.json b/package-lock.json index 4a19c22e27c..be52c71cb06 100644 --- a/package-lock.json +++ b/package-lock.json @@ -9,13 +9,13 @@ "version": "0.1.0", "license": "Apache-2.0", "dependencies": { - "@enterprisedb/icons": "^1.25.1", + "@enterprisedb/icons": "^1.26.1", "@mdx-js/mdx": "^1.6.22", "@mdx-js/react": "^1.6.22", - "algoliasearch": "^4.17.2", + "algoliasearch": "^4.20.0", "balance-text": "^3.3.1", "bl": "5.0.0", - "bootstrap": "^4.6.2", + "bootstrap": "^5.3.2", "gatsby": "^4.25.7", "gatsby-cli": "^4.25.0", "gatsby-plugin-algolia": "^0.26.0", @@ -43,26 +43,26 @@ "graceful-fs": "^4.2.11", "hast-util-to-string": "^1.0.4", "is-absolute-url": "^4.0.1", - "markdown-to-jsx": "^7.2.1", + "markdown-to-jsx": "^7.3.2", "mdast-util-to-string": "^2.0.0", "prismjs": "^1.29.0", "react": "^18.2.0", - "react-bootstrap": "^1.6.7", + "react-bootstrap": "^2.8.0", "react-dom": "^18.2.0", "react-helmet": "^6.1.0", - "react-instantsearch-dom": "^6.40.0", + "react-instantsearch": "^7.1.0", "rehype-parse": "^7.0.1", "remark-admonitions": "github:josh-heyer/remark-admonitions", - "sass": "^1.63.4", + "sass": "^1.68.0", "truncate-utf8-bytes": "^1.0.2", "unist-util-visit-parents": "^3.1.1" }, "devDependencies": { - "fast-glob": "^3.2.12", + "fast-glob": "^3.3.1", "hast-util-is-element": "^2.1.3", "hast-util-to-text": "^3.1.2", - "husky": "^7.0.4", - "prettier": "^2.8.8", + "husky": "^8.0.3", + "prettier": "^3.0.3", "pretty-quick": "^3.1.3", "react-refresh": "^0.14.0", "rehype-format": "^3.1.0", @@ -79,74 +79,74 @@ } }, "node_modules/@algolia/cache-browser-local-storage": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/@algolia/cache-browser-local-storage/-/cache-browser-local-storage-4.17.2.tgz", - "integrity": "sha512-ZkVN7K/JE+qMQbpR6h3gQOGR6yCJpmucSBCmH5YDxnrYbp2CbrVCu0Nr+FGVoWzMJNznj1waShkfQ9awERulLw==", + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@algolia/cache-browser-local-storage/-/cache-browser-local-storage-4.20.0.tgz", + "integrity": "sha512-uujahcBt4DxduBTvYdwO3sBfHuJvJokiC3BP1+O70fglmE1ShkH8lpXqZBac1rrU3FnNYSUs4pL9lBdTKeRPOQ==", "dependencies": { - "@algolia/cache-common": "4.17.2" + "@algolia/cache-common": "4.20.0" } }, "node_modules/@algolia/cache-common": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/@algolia/cache-common/-/cache-common-4.17.2.tgz", - "integrity": "sha512-fojbhYIS8ovfYs6hwZpy1O4mBfVRxNgAaZRqsdVQd54hU4MxYDYFCxagYX28lOBz7btcDHld6BMoWXvjzkx6iQ==" + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@algolia/cache-common/-/cache-common-4.20.0.tgz", + "integrity": "sha512-vCfxauaZutL3NImzB2G9LjLt36vKAckc6DhMp05An14kVo8F1Yofb6SIl6U3SaEz8pG2QOB9ptwM5c+zGevwIQ==" }, "node_modules/@algolia/cache-in-memory": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/@algolia/cache-in-memory/-/cache-in-memory-4.17.2.tgz", - "integrity": "sha512-UYQcMzPurNi+cPYkuPemTZkjKAjdgAS1hagC5irujKbrYnN4yscK4TkOI5tX+O8/KegtJt3kOK07OIrJ2QDAAw==", + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@algolia/cache-in-memory/-/cache-in-memory-4.20.0.tgz", + "integrity": "sha512-Wm9ak/IaacAZXS4mB3+qF/KCoVSBV6aLgIGFEtQtJwjv64g4ePMapORGmCyulCFwfePaRAtcaTbMcJF+voc/bg==", "dependencies": { - "@algolia/cache-common": "4.17.2" + "@algolia/cache-common": "4.20.0" } }, "node_modules/@algolia/client-account": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/@algolia/client-account/-/client-account-4.17.2.tgz", - "integrity": "sha512-doSk89pBPDpDyKJSHFADIGa2XSGrBCj3QwPvqtRJXDADpN+OjW+eTR8r4hEs/7X4GGfjfAOAES8JgDx+fZntYw==", + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@algolia/client-account/-/client-account-4.20.0.tgz", + "integrity": "sha512-GGToLQvrwo7am4zVkZTnKa72pheQeez/16sURDWm7Seyz+HUxKi3BM6fthVVPUEBhtJ0reyVtuK9ArmnaKl10Q==", "dependencies": { - "@algolia/client-common": "4.17.2", - "@algolia/client-search": "4.17.2", - "@algolia/transporter": "4.17.2" + "@algolia/client-common": "4.20.0", + "@algolia/client-search": "4.20.0", + "@algolia/transporter": "4.20.0" } }, "node_modules/@algolia/client-analytics": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/@algolia/client-analytics/-/client-analytics-4.17.2.tgz", - "integrity": "sha512-V+DcXbOtD/hKwAR3qGQrtlrJ3q2f9OKfx843q744o4m3xHv5ueCAvGXB1znPsdaUrVDNAImcgEgqwI9x7EJbDw==", + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@algolia/client-analytics/-/client-analytics-4.20.0.tgz", + "integrity": "sha512-EIr+PdFMOallRdBTHHdKI3CstslgLORQG7844Mq84ib5oVFRVASuuPmG4bXBgiDbcsMLUeOC6zRVJhv1KWI0ug==", "dependencies": { - "@algolia/client-common": "4.17.2", - "@algolia/client-search": "4.17.2", - "@algolia/requester-common": "4.17.2", - "@algolia/transporter": "4.17.2" + "@algolia/client-common": "4.20.0", + "@algolia/client-search": "4.20.0", + "@algolia/requester-common": "4.20.0", + "@algolia/transporter": "4.20.0" } }, "node_modules/@algolia/client-common": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/@algolia/client-common/-/client-common-4.17.2.tgz", - "integrity": "sha512-gKBUnjxi0ukJYIJxVREYGt1Dmj1B3RBYbfGWi0dIPp1BC1VvQm+BOuNwsIwmq/x3MPO+sGuK978eKiP3tZDvag==", + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@algolia/client-common/-/client-common-4.20.0.tgz", + "integrity": "sha512-P3WgMdEss915p+knMMSd/fwiHRHKvDu4DYRrCRaBrsfFw7EQHon+EbRSm4QisS9NYdxbS04kcvNoavVGthyfqQ==", "dependencies": { - "@algolia/requester-common": "4.17.2", - "@algolia/transporter": "4.17.2" + "@algolia/requester-common": "4.20.0", + "@algolia/transporter": "4.20.0" } }, "node_modules/@algolia/client-personalization": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/@algolia/client-personalization/-/client-personalization-4.17.2.tgz", - "integrity": "sha512-wc4UgOWxSYWz5wpuelNmlt895jA9twjZWM2ms17Ws8qCvBHF7OVGdMGgbysPB8790YnfvvDnSsWOv3CEj26Eow==", + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@algolia/client-personalization/-/client-personalization-4.20.0.tgz", + "integrity": "sha512-N9+zx0tWOQsLc3K4PVRDV8GUeOLAY0i445En79Pr3zWB+m67V+n/8w4Kw1C5LlbHDDJcyhMMIlqezh6BEk7xAQ==", "dependencies": { - "@algolia/client-common": "4.17.2", - "@algolia/requester-common": "4.17.2", - "@algolia/transporter": "4.17.2" + "@algolia/client-common": "4.20.0", + "@algolia/requester-common": "4.20.0", + "@algolia/transporter": "4.20.0" } }, "node_modules/@algolia/client-search": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/@algolia/client-search/-/client-search-4.17.2.tgz", - "integrity": "sha512-FUjIs+gRe0upJC++uVs4sdxMw15JxfkT86Gr/kqVwi9kcqaZhXntSbW/Fw959bIYXczjmeVQsilYvBWW4YvSZA==", + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@algolia/client-search/-/client-search-4.20.0.tgz", + "integrity": "sha512-zgwqnMvhWLdpzKTpd3sGmMlr4c+iS7eyyLGiaO51zDZWGMkpgoNVmltkzdBwxOVXz0RsFMznIxB9zuarUv4TZg==", "dependencies": { - "@algolia/client-common": "4.17.2", - "@algolia/requester-common": "4.17.2", - "@algolia/transporter": "4.17.2" + "@algolia/client-common": "4.20.0", + "@algolia/requester-common": "4.20.0", + "@algolia/transporter": "4.20.0" } }, "node_modules/@algolia/events": { @@ -155,49 +155,63 @@ "integrity": "sha512-FQzvOCgoFXAbf5Y6mYozw2aj5KCJoA3m4heImceldzPSMbdyS4atVjJzXKMsfX3wnZTFYwkkt8/z8UesLHlSBQ==" }, "node_modules/@algolia/logger-common": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/@algolia/logger-common/-/logger-common-4.17.2.tgz", - "integrity": "sha512-EfXuweUE+1HiSMsQidaDWA5Lv4NnStYIlh7PO5pLkI+sdhbMX0e5AO5nUAMIFM1VkEANes70RA8fzhP6OqCqQQ==" + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@algolia/logger-common/-/logger-common-4.20.0.tgz", + "integrity": "sha512-xouigCMB5WJYEwvoWW5XDv7Z9f0A8VoXJc3VKwlHJw/je+3p2RcDXfksLI4G4lIVncFUYMZx30tP/rsdlvvzHQ==" }, "node_modules/@algolia/logger-console": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/@algolia/logger-console/-/logger-console-4.17.2.tgz", - "integrity": "sha512-JuG8HGVlJ+l/UEDK4h2Y8q/IEmRjQz1J0aS9tf6GPNbGYiSvMr1DDdZ+hqV3bb1XE6wU8Ypex56HisWMSpnG0A==", + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@algolia/logger-console/-/logger-console-4.20.0.tgz", + "integrity": "sha512-THlIGG1g/FS63z0StQqDhT6bprUczBI8wnLT3JWvfAQDZX5P6fCg7dG+pIrUBpDIHGszgkqYEqECaKKsdNKOUA==", "dependencies": { - "@algolia/logger-common": "4.17.2" + "@algolia/logger-common": "4.20.0" } }, "node_modules/@algolia/requester-browser-xhr": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/@algolia/requester-browser-xhr/-/requester-browser-xhr-4.17.2.tgz", - "integrity": "sha512-FKI2lYWwksALfRt2OETFmGb5+P7WVc4py2Ai3H7k8FSfTLwVvs9WVVmtlx6oANQ8RFEK4B85h8DQJTJ29TDfmA==", + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@algolia/requester-browser-xhr/-/requester-browser-xhr-4.20.0.tgz", + "integrity": "sha512-HbzoSjcjuUmYOkcHECkVTwAelmvTlgs48N6Owt4FnTOQdwn0b8pdht9eMgishvk8+F8bal354nhx/xOoTfwiAw==", "dependencies": { - "@algolia/requester-common": "4.17.2" + "@algolia/requester-common": "4.20.0" } }, "node_modules/@algolia/requester-common": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/@algolia/requester-common/-/requester-common-4.17.2.tgz", - "integrity": "sha512-Rfim23ztAhYpE9qm+KCfCRo+YLJCjiiTG+IpDdzUjMpYPhUtirQT0A35YEd/gKn86YNyydxS9w8iRSjwKh+L0A==" + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@algolia/requester-common/-/requester-common-4.20.0.tgz", + "integrity": "sha512-9h6ye6RY/BkfmeJp7Z8gyyeMrmmWsMOCRBXQDs4mZKKsyVlfIVICpcSibbeYcuUdurLhIlrOUkH3rQEgZzonng==" }, "node_modules/@algolia/requester-node-http": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/@algolia/requester-node-http/-/requester-node-http-4.17.2.tgz", - "integrity": "sha512-E0b0kyCDMvUIhQmDNd/mH4fsKJdEEX6PkMKrYJjzm6moo+rP22tqpq4Rfe7DZD8OB6/LsDD3zs3Kvd+L+M5wwQ==", + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@algolia/requester-node-http/-/requester-node-http-4.20.0.tgz", + "integrity": "sha512-ocJ66L60ABSSTRFnCHIEZpNHv6qTxsBwJEPfYaSBsLQodm0F9ptvalFkHMpvj5DfE22oZrcrLbOYM2bdPJRHng==", "dependencies": { - "@algolia/requester-common": "4.17.2" + "@algolia/requester-common": "4.20.0" } }, "node_modules/@algolia/transporter": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/@algolia/transporter/-/transporter-4.17.2.tgz", - "integrity": "sha512-m8pXlz5OnNzjD1rcw+duCN4jG4yEzkJBsvKYMoN22Oq6rQwy1AY5muZ+IQUs4dL+A364CYkRMLRWhvXpCZ1x+g==", + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@algolia/transporter/-/transporter-4.20.0.tgz", + "integrity": "sha512-Lsii1pGWOAISbzeyuf+r/GPhvHMPHSPrTDWNcIzOE1SG1inlJHICaVe2ikuoRjcpgxZNU54Jl+if15SUCsaTUg==", "dependencies": { - "@algolia/cache-common": "4.17.2", - "@algolia/logger-common": "4.17.2", - "@algolia/requester-common": "4.17.2" + "@algolia/cache-common": "4.20.0", + "@algolia/logger-common": "4.20.0", + "@algolia/requester-common": "4.20.0" } }, + "node_modules/@algolia/ui-components-highlight-vdom": { + "version": "1.2.1", + "resolved": "https://registry.npmjs.org/@algolia/ui-components-highlight-vdom/-/ui-components-highlight-vdom-1.2.1.tgz", + "integrity": "sha512-IlYgIaCUEkz9ezNbwugwKv991oOHhveyq6nzL0F1jDzg1p3q5Yj/vO4KpNG910r2dwGCG3nEm5GtChcLnarhFA==", + "dependencies": { + "@algolia/ui-components-shared": "1.2.1", + "@babel/runtime": "^7.0.0" + } + }, + "node_modules/@algolia/ui-components-shared": { + "version": "1.2.1", + "resolved": "https://registry.npmjs.org/@algolia/ui-components-shared/-/ui-components-shared-1.2.1.tgz", + "integrity": "sha512-a7mYHf/GVQfhAx/HRiMveKkFvHspQv/REdG+C/FIOosiSmNZxX7QebDwJkrGSmDWdXO12D0Qv1xn3AytFcEDlQ==" + }, "node_modules/@ampproject/remapping": { "version": "2.2.1", "resolved": "https://registry.npmjs.org/@ampproject/remapping/-/remapping-2.2.1.tgz", @@ -353,9 +367,9 @@ } }, "node_modules/@babel/core/node_modules/semver": { - "version": "6.3.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", - "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "version": "6.3.1", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", + "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", "bin": { "semver": "bin/semver.js" } @@ -378,9 +392,9 @@ } }, "node_modules/@babel/eslint-parser/node_modules/semver": { - "version": "6.3.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", - "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "version": "6.3.1", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", + "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", "bin": { "semver": "bin/semver.js" } @@ -441,9 +455,9 @@ } }, "node_modules/@babel/helper-compilation-targets/node_modules/semver": { - "version": "6.3.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", - "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "version": "6.3.1", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", + "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", "bin": { "semver": "bin/semver.js" } @@ -501,9 +515,9 @@ } }, "node_modules/@babel/helper-define-polyfill-provider/node_modules/semver": { - "version": "6.3.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", - "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "version": "6.3.1", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", + "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", "bin": { "semver": "bin/semver.js" } @@ -1715,9 +1729,9 @@ } }, "node_modules/@babel/plugin-transform-runtime/node_modules/semver": { - "version": "6.3.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", - "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "version": "6.3.1", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", + "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", "bin": { "semver": "bin/semver.js" } @@ -1928,9 +1942,9 @@ } }, "node_modules/@babel/preset-env/node_modules/semver": { - "version": "6.3.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", - "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "version": "6.3.1", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", + "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", "bin": { "semver": "bin/semver.js" } @@ -2072,9 +2086,9 @@ } }, "node_modules/@enterprisedb/icons": { - "version": "1.26.0", - "resolved": "https://npm.pkg.github.com/download/@EnterpriseDB/icons/1.26.0/e1ee18031b4d20aead6c43e113fca038d06d663c", - "integrity": "sha512-k2NWaThUJ1S9NjFJoSLk5zVgabqiNnZSzzZwBLHpXQQP3iaLObYnNaLLgUkyxXRZGFL5dEc6gS54Wlr+gtDS4w==", + "version": "1.26.1", + "resolved": "https://npm.pkg.github.com/download/@EnterpriseDB/icons/1.26.1/3540e84bc496f091c9a17ae947ccaa9ba8c4d978", + "integrity": "sha512-thsiXkfmwDYRXAl72fpBWGKe2FffvIFdtxCsXW4vffDE2vNA0IWybDtdgC4/yQ4WD3Pn47CryQ1g+DWY8L2v8w==", "dependencies": { "prop-types": "^15.8.1" }, @@ -3934,33 +3948,75 @@ } }, "node_modules/@popperjs/core": { - "version": "2.11.7", - "resolved": "https://registry.npmjs.org/@popperjs/core/-/core-2.11.7.tgz", - "integrity": "sha512-Cr4OjIkipTtcXKjAsm8agyleBuDHvxzeBoa1v543lbv1YaIwQjESsVcmjiWiPEbC1FIeHOG/Op9kdCmAmiS3Kw==", + "version": "2.11.8", + "resolved": "https://registry.npmjs.org/@popperjs/core/-/core-2.11.8.tgz", + "integrity": "sha512-P1st0aksCrn9sGZhp8GMYwBnQsbvAWsZAX44oXNNvLHGqAOcoVxmjZiohstwQ7SqKnbR47akdNi+uleWD8+g6A==", "funding": { "type": "opencollective", "url": "https://opencollective.com/popperjs" } }, - "node_modules/@restart/context": { - "version": "2.1.4", - "resolved": "https://registry.npmjs.org/@restart/context/-/context-2.1.4.tgz", - "integrity": "sha512-INJYZQJP7g+IoDUh/475NlGiTeMfwTXUEr3tmRneckHIxNolGOW9CTq83S8cxq0CgJwwcMzMJFchxvlwe7Rk8Q==", + "node_modules/@react-aria/ssr": { + "version": "3.8.0", + "resolved": "https://registry.npmjs.org/@react-aria/ssr/-/ssr-3.8.0.tgz", + "integrity": "sha512-Y54xs483rglN5DxbwfCPHxnkvZ+gZ0LbSYmR72LyWPGft8hN/lrl1VRS1EW2SMjnkEWlj+Km2mwvA3kEHDUA0A==", + "dependencies": { + "@swc/helpers": "^0.5.0" + }, + "engines": { + "node": ">= 12" + }, "peerDependencies": { - "react": ">=16.3.2" + "react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0" + } + }, + "node_modules/@react-aria/ssr/node_modules/@swc/helpers": { + "version": "0.5.2", + "resolved": "https://registry.npmjs.org/@swc/helpers/-/helpers-0.5.2.tgz", + "integrity": "sha512-E4KcWTpoLHqwPHLxidpOqQbcrZVgi0rsmmZXUle1jXmJfuIf/UWpczUJ7MZZ5tlxytgJXyp0w4PGkkeLiuIdZw==", + "dependencies": { + "tslib": "^2.4.0" } }, "node_modules/@restart/hooks": { - "version": "0.4.9", - "resolved": "https://registry.npmjs.org/@restart/hooks/-/hooks-0.4.9.tgz", - "integrity": "sha512-3BekqcwB6Umeya+16XPooARn4qEPW6vNvwYnlofIYe6h9qG1/VeD7UvShCWx11eFz5ELYmwIEshz+MkPX3wjcQ==", + "version": "0.4.11", + "resolved": "https://registry.npmjs.org/@restart/hooks/-/hooks-0.4.11.tgz", + "integrity": "sha512-Ft/ncTULZN6ldGHiF/k5qt72O8JyRMOeg0tApvCni8LkoiEahO+z3TNxfXIVGy890YtWVDvJAl662dVJSJXvMw==", "dependencies": { - "dequal": "^2.0.2" + "dequal": "^2.0.3" }, "peerDependencies": { "react": ">=16.8.0" } }, + "node_modules/@restart/ui": { + "version": "1.6.6", + "resolved": "https://registry.npmjs.org/@restart/ui/-/ui-1.6.6.tgz", + "integrity": "sha512-eC3puKuWE1SRYbojWHXnvCNHGgf3uzHCb6JOhnF4OXPibOIPEkR1sqDSkL643ydigxwh+ruCa1CmYHlzk7ikKA==", + "dependencies": { + "@babel/runtime": "^7.21.0", + "@popperjs/core": "^2.11.6", + "@react-aria/ssr": "^3.5.0", + "@restart/hooks": "^0.4.9", + "@types/warning": "^3.0.0", + "dequal": "^2.0.3", + "dom-helpers": "^5.2.0", + "uncontrollable": "^8.0.1", + "warning": "^4.0.3" + }, + "peerDependencies": { + "react": ">=16.14.0", + "react-dom": ">=16.14.0" + } + }, + "node_modules/@restart/ui/node_modules/uncontrollable": { + "version": "8.0.4", + "resolved": "https://registry.npmjs.org/uncontrollable/-/uncontrollable-8.0.4.tgz", + "integrity": "sha512-ulRWYWHvscPFc0QQXvyJjY6LIXU56f0h8pQFvhxiKk5V1fcI8gp9Ht9leVAhrVjzqMw0BgjspBINx9r6oyJUvQ==", + "peerDependencies": { + "react": ">=16.14.0" + } + }, "node_modules/@sideway/address": { "version": "4.1.4", "resolved": "https://registry.npmjs.org/@sideway/address/-/address-4.1.4.tgz", @@ -4131,6 +4187,11 @@ "resolved": "https://registry.npmjs.org/@types/debug/-/debug-0.0.30.tgz", "integrity": "sha512-orGL5LXERPYsLov6CWs3Fh6203+dXzJkR7OnddIr2514Hsecwc8xRpzCapshBbKFImCsvS/mk6+FWiN5LyZJAQ==" }, + "node_modules/@types/dom-speech-recognition": { + "version": "0.0.1", + "resolved": "https://registry.npmjs.org/@types/dom-speech-recognition/-/dom-speech-recognition-0.0.1.tgz", + "integrity": "sha512-udCxb8DvjcDKfk1WTBzDsxFbLgYxmQGKrE/ricoMqHRNjSlSUCcamVTA5lIQqzY10mY5qCY0QDwBfFEwhfoDPw==" + }, "node_modules/@types/eslint": { "version": "7.29.0", "resolved": "https://registry.npmjs.org/@types/eslint/-/eslint-7.29.0.tgz", @@ -4168,6 +4229,11 @@ "@types/node": "*" } }, + "node_modules/@types/google.maps": { + "version": "3.54.1", + "resolved": "https://registry.npmjs.org/@types/google.maps/-/google.maps-3.54.1.tgz", + "integrity": "sha512-zh6333O/yPfcvRxpBTjnNFJjiHiujvy+tTAWwvNj3LMy90Y+VLTom8n9gvmgjXhOHgHvYpgO2Xyz31wYEYN27A==" + }, "node_modules/@types/hast": { "version": "2.3.4", "resolved": "https://registry.npmjs.org/@types/hast/-/hast-2.3.4.tgz", @@ -4176,6 +4242,11 @@ "@types/unist": "*" } }, + "node_modules/@types/hogan.js": { + "version": "3.0.2", + "resolved": "https://registry.npmjs.org/@types/hogan.js/-/hogan.js-3.0.2.tgz", + "integrity": "sha512-M6jOVsZEK31II8HV9QaYI5pg/w7fZb+3aqdCn3M3uofBswvrYBzbaQwSudB6z1UqF2IT3B8vt/3oBoa7XqugFw==" + }, "node_modules/@types/http-cache-semantics": { "version": "4.0.1", "resolved": "https://registry.npmjs.org/@types/http-cache-semantics/-/http-cache-semantics-4.0.1.tgz", @@ -4189,11 +4260,6 @@ "@types/node": "*" } }, - "node_modules/@types/invariant": { - "version": "2.2.35", - "resolved": "https://registry.npmjs.org/@types/invariant/-/invariant-2.2.35.tgz", - "integrity": "sha512-DxX1V9P8zdJPYQat1gHyY0xj3efl8gnMVjiM9iCY6y27lj+PoQWkgjt8jDqmovPqULkKVpKRg8J36iQiA+EtEg==" - }, "node_modules/@types/json-schema": { "version": "7.0.11", "resolved": "https://registry.npmjs.org/@types/json-schema/-/json-schema-7.0.11.tgz", @@ -4267,6 +4333,11 @@ "resolved": "https://registry.npmjs.org/@types/prop-types/-/prop-types-15.7.5.tgz", "integrity": "sha512-JCB8C6SnDoQf0cNycqd/35A7MjcnK+ZTqE7judS6o7utxUCg6imJg3QK2qzHKszlTjcj2cn+NwMB2i96ubpj7w==" }, + "node_modules/@types/qs": { + "version": "6.9.8", + "resolved": "https://registry.npmjs.org/@types/qs/-/qs-6.9.8.tgz", + "integrity": "sha512-u95svzDlTysU5xecFNTgfFG5RUWu1A9P0VzgpcIiGZA9iraHOdSzcxMxQ55DyeRaGCSxQi7LxXDI4rzq/MYfdg==" + }, "node_modules/@types/reach__router": { "version": "1.3.11", "resolved": "https://registry.npmjs.org/@types/reach__router/-/reach__router-1.3.11.tgz", @@ -4413,9 +4484,9 @@ } }, "node_modules/@typescript-eslint/eslint-plugin/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -4565,9 +4636,9 @@ } }, "node_modules/@typescript-eslint/typescript-estree/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -4756,6 +4827,11 @@ "resolved": "https://registry.npmjs.org/@xtuc/long/-/long-4.2.2.tgz", "integrity": "sha512-NuHqBY1PB/D8xU6s/thBgOAiAP7HOYDQ32+BFZILJ8ivkUkAHQnWfn6WhL79Owj1qmUnoN/YPhktdIoucipkAQ==" }, + "node_modules/abbrev": { + "version": "1.1.1", + "resolved": "https://registry.npmjs.org/abbrev/-/abbrev-1.1.1.tgz", + "integrity": "sha512-nne9/IiQ/hzIhY6pdDnbBtz7DjPTKrY00P/zvPSm5pOFkl6xuGrGnXn/VtTNNfNtAfZ9/1RtehkszU9qcTii0Q==" + }, "node_modules/abortcontroller-polyfill": { "version": "1.7.5", "resolved": "https://registry.npmjs.org/abortcontroller-polyfill/-/abortcontroller-polyfill-1.7.5.tgz", @@ -4863,35 +4939,24 @@ } }, "node_modules/algoliasearch": { - "version": "4.17.2", - "resolved": "https://registry.npmjs.org/algoliasearch/-/algoliasearch-4.17.2.tgz", - "integrity": "sha512-VFu43JJNYIW74awp7oeQcQsPcxOhd8psqBDTfyNO2Zt6L1NqnNMTVnaIdQ+8dtKqUDBqQZp0szPxECvX8CK2Fg==", - "dependencies": { - "@algolia/cache-browser-local-storage": "4.17.2", - "@algolia/cache-common": "4.17.2", - "@algolia/cache-in-memory": "4.17.2", - "@algolia/client-account": "4.17.2", - "@algolia/client-analytics": "4.17.2", - "@algolia/client-common": "4.17.2", - "@algolia/client-personalization": "4.17.2", - "@algolia/client-search": "4.17.2", - "@algolia/logger-common": "4.17.2", - "@algolia/logger-console": "4.17.2", - "@algolia/requester-browser-xhr": "4.17.2", - "@algolia/requester-common": "4.17.2", - "@algolia/requester-node-http": "4.17.2", - "@algolia/transporter": "4.17.2" - } - }, - "node_modules/algoliasearch-helper": { - "version": "3.13.2", - "resolved": "https://registry.npmjs.org/algoliasearch-helper/-/algoliasearch-helper-3.13.2.tgz", - "integrity": "sha512-1bZjtHuqCBYw7Eu3Qh0Jfq4s63UcbOs6VvLPdt7kxn5+zMgs46xiXgc65YhZBNM3hDGrudhAX9hDhE9OP+rKUw==", - "dependencies": { - "@algolia/events": "^4.0.1" - }, - "peerDependencies": { - "algoliasearch": ">= 3.1 < 6" + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/algoliasearch/-/algoliasearch-4.20.0.tgz", + "integrity": "sha512-y+UHEjnOItoNy0bYO+WWmLWBlPwDjKHW6mNHrPi0NkuhpQOOEbrkwQH/wgKFDLh7qlKjzoKeiRtlpewDPDG23g==", + "dependencies": { + "@algolia/cache-browser-local-storage": "4.20.0", + "@algolia/cache-common": "4.20.0", + "@algolia/cache-in-memory": "4.20.0", + "@algolia/client-account": "4.20.0", + "@algolia/client-analytics": "4.20.0", + "@algolia/client-common": "4.20.0", + "@algolia/client-personalization": "4.20.0", + "@algolia/client-search": "4.20.0", + "@algolia/logger-common": "4.20.0", + "@algolia/logger-console": "4.20.0", + "@algolia/requester-browser-xhr": "4.20.0", + "@algolia/requester-common": "4.20.0", + "@algolia/requester-node-http": "4.20.0", + "@algolia/transporter": "4.20.0" } }, "node_modules/anser": { @@ -5439,9 +5504,9 @@ } }, "node_modules/babel-plugin-polyfill-corejs2/node_modules/semver": { - "version": "6.3.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", - "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "version": "6.3.1", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", + "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", "bin": { "semver": "bin/semver.js" } @@ -5708,9 +5773,9 @@ "integrity": "sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww==" }, "node_modules/bootstrap": { - "version": "4.6.2", - "resolved": "https://registry.npmjs.org/bootstrap/-/bootstrap-4.6.2.tgz", - "integrity": "sha512-51Bbp/Uxr9aTuy6ca/8FbFloBUJZLHwnhTcnjIeRn2suQWsWzcuJhGjKDB5eppVte/8oCdOL3VuwxvZDUggwGQ==", + "version": "5.3.2", + "resolved": "https://registry.npmjs.org/bootstrap/-/bootstrap-5.3.2.tgz", + "integrity": "sha512-D32nmNWiQHo94BKHLmOrdjlL05q1c8oxbtBphQFb9Z5to6eGRDCm0QgeaZ4zFBHzfg2++rqa2JkqCcxDy0sH0g==", "funding": [ { "type": "github", @@ -5722,8 +5787,7 @@ } ], "peerDependencies": { - "jquery": "1.9.1 - 3", - "popper.js": "^1.16.1" + "@popperjs/core": "^2.11.8" } }, "node_modules/boxen": { @@ -6961,9 +7025,9 @@ } }, "node_modules/css-loader/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -8153,9 +8217,9 @@ } }, "node_modules/eslint-plugin-import/node_modules/semver": { - "version": "6.3.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", - "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "version": "6.3.1", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", + "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", "bin": { "semver": "bin/semver.js" } @@ -8190,9 +8254,9 @@ } }, "node_modules/eslint-plugin-jsx-a11y/node_modules/semver": { - "version": "6.3.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", - "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "version": "6.3.1", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", + "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", "bin": { "semver": "bin/semver.js" } @@ -8264,9 +8328,9 @@ } }, "node_modules/eslint-plugin-react/node_modules/semver": { - "version": "6.3.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", - "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "version": "6.3.1", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", + "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", "bin": { "semver": "bin/semver.js" } @@ -8503,9 +8567,9 @@ } }, "node_modules/eslint/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -8890,9 +8954,9 @@ "integrity": "sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==" }, "node_modules/fast-glob": { - "version": "3.3.0", - "resolved": "https://registry.npmjs.org/fast-glob/-/fast-glob-3.3.0.tgz", - "integrity": "sha512-ChDuvbOypPuNjO8yIDf36x7BlZX1smcUMTTcyoIjycexOxd6DFsKsg21qVBzEmr3G7fUKIRy2/psii+CIUt7FA==", + "version": "3.3.1", + "resolved": "https://registry.npmjs.org/fast-glob/-/fast-glob-3.3.1.tgz", + "integrity": "sha512-kNFPyjhh5cKjrUltxs+wFx+ZkbRaxxmZ+X0ZU31SOsxCEtP9VPgtq2teZw1DebupL5GmDaNQ6yKMMVcM41iqDg==", "dependencies": { "@nodelib/fs.stat": "^2.0.2", "@nodelib/fs.walk": "^1.2.3", @@ -9354,9 +9418,9 @@ } }, "node_modules/fork-ts-checker-webpack-plugin/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -9829,9 +9893,9 @@ } }, "node_modules/gatsby-cli/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -10068,9 +10132,9 @@ } }, "node_modules/gatsby-plugin-manifest/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -10561,9 +10625,9 @@ } }, "node_modules/gatsby-plugin-sharp/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -11206,9 +11270,9 @@ } }, "node_modules/gatsby-transformer-sharp/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -11328,9 +11392,9 @@ } }, "node_modules/gatsby/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -12161,6 +12225,27 @@ "tslib": "^2.0.3" } }, + "node_modules/hogan.js": { + "version": "3.0.2", + "resolved": "https://registry.npmjs.org/hogan.js/-/hogan.js-3.0.2.tgz", + "integrity": "sha512-RqGs4wavGYJWE07t35JQccByczmNUXQT0E12ZYV1VKYu5UiAU9lsos/yBAcf840+zrUQQxgVduCR5/B8nNtibg==", + "dependencies": { + "mkdirp": "0.3.0", + "nopt": "1.0.10" + }, + "bin": { + "hulk": "bin/hulk" + } + }, + "node_modules/hogan.js/node_modules/mkdirp": { + "version": "0.3.0", + "resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.0.tgz", + "integrity": "sha512-OHsdUcVAQ6pOtg5JYWpCBo9W/GySVuwvP9hueRMW7UqshC0tbfzLv8wjySTPm3tfUZ/21CE9E1pJagOA91Pxew==", + "deprecated": "Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)", + "engines": { + "node": "*" + } + }, "node_modules/hosted-git-info": { "version": "3.0.8", "resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-3.0.8.tgz", @@ -12188,6 +12273,11 @@ "resolved": "https://registry.npmjs.org/yallist/-/yallist-4.0.0.tgz", "integrity": "sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==" }, + "node_modules/htm": { + "version": "3.1.1", + "resolved": "https://registry.npmjs.org/htm/-/htm-3.1.1.tgz", + "integrity": "sha512-983Vyg8NwUE7JkZ6NmOqpCZ+sh1bKv2iYTlUkzlWmA5JD2acKoxd4KVxbMmxX/85mtfdnDmTFoNKcg5DGAvxNQ==" + }, "node_modules/html-entities": { "version": "2.3.3", "resolved": "https://registry.npmjs.org/html-entities/-/html-entities-2.3.3.tgz", @@ -12271,15 +12361,15 @@ } }, "node_modules/husky": { - "version": "7.0.4", - "resolved": "https://registry.npmjs.org/husky/-/husky-7.0.4.tgz", - "integrity": "sha512-vbaCKN2QLtP/vD4yvs6iz6hBEo6wkSzs8HpRah1Z6aGmF2KW5PdYuAd7uX5a+OyBZHBhd+TFLqgjUgytQr4RvQ==", + "version": "8.0.3", + "resolved": "https://registry.npmjs.org/husky/-/husky-8.0.3.tgz", + "integrity": "sha512-+dQSyqPh4x1hlO1swXBiNb2HzTDN1I2IGLQx1GrBuiqFJfoMrnZWwVmatvSiO+Iz8fBUnf+lekwNo4c2LlXItg==", "dev": true, "bin": { "husky": "lib/bin.js" }, "engines": { - "node": ">=12" + "node": ">=14" }, "funding": { "url": "https://github.com/sponsors/typicode" @@ -12537,6 +12627,51 @@ "url": "https://github.com/sponsors/sindresorhus" } }, + "node_modules/instantsearch.js": { + "version": "4.57.0", + "resolved": "https://registry.npmjs.org/instantsearch.js/-/instantsearch.js-4.57.0.tgz", + "integrity": "sha512-oaWmX4gUI4U8fcj77FmR3UPHfHOYpJoeHhek+9wM4bZ+VJ8uAQZOV/aBGka7Kmvln8NLZ7rqn+Hm84tDunIBog==", + "dependencies": { + "@algolia/events": "^4.0.1", + "@algolia/ui-components-highlight-vdom": "^1.2.1", + "@algolia/ui-components-shared": "^1.2.1", + "@types/dom-speech-recognition": "^0.0.1", + "@types/google.maps": "^3.45.3", + "@types/hogan.js": "^3.0.0", + "@types/qs": "^6.5.3", + "algoliasearch-helper": "3.14.2", + "hogan.js": "^3.0.2", + "htm": "^3.0.0", + "preact": "^10.10.0", + "qs": "^6.5.1 < 6.10", + "search-insights": "^2.6.0" + }, + "peerDependencies": { + "algoliasearch": ">= 3.1 < 6" + } + }, + "node_modules/instantsearch.js/node_modules/algoliasearch-helper": { + "version": "3.14.2", + "resolved": "https://registry.npmjs.org/algoliasearch-helper/-/algoliasearch-helper-3.14.2.tgz", + "integrity": "sha512-FjDSrjvQvJT/SKMW74nPgFpsoPUwZCzGbCqbp8HhBFfSk/OvNFxzCaCmuO0p7AWeLy1gD+muFwQEkBwcl5H4pg==", + "dependencies": { + "@algolia/events": "^4.0.1" + }, + "peerDependencies": { + "algoliasearch": ">= 3.1 < 6" + } + }, + "node_modules/instantsearch.js/node_modules/qs": { + "version": "6.9.7", + "resolved": "https://registry.npmjs.org/qs/-/qs-6.9.7.tgz", + "integrity": "sha512-IhMFgUmuNpyRfxA90umL7ByLlgRXu6tIfKPpF5TmcfRLlLCckfP/g3IQmju6jjpu+Hh8rA+2p6A27ZSPOOHdKw==", + "engines": { + "node": ">=0.6" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, "node_modules/internal-slot": { "version": "1.0.5", "resolved": "https://registry.npmjs.org/internal-slot/-/internal-slot-1.0.5.tgz", @@ -13290,12 +13425,6 @@ "@sideway/pinpoint": "^2.0.0" } }, - "node_modules/jquery": { - "version": "3.6.4", - "resolved": "https://registry.npmjs.org/jquery/-/jquery-3.6.4.tgz", - "integrity": "sha512-v28EW9DWDFpzcD9O5iyJXg3R3+q+mET5JhnjJzQUZMHOv67bpSIHq81GEYpPNZHG+XXHsfSme3nxp/hndKEcsQ==", - "peer": true - }, "node_modules/js-tokens": { "version": "4.0.0", "resolved": "https://registry.npmjs.org/js-tokens/-/js-tokens-4.0.0.tgz", @@ -13751,9 +13880,9 @@ } }, "node_modules/make-dir/node_modules/semver": { - "version": "6.3.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", - "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "version": "6.3.1", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", + "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", "bin": { "semver": "bin/semver.js" } @@ -13807,9 +13936,9 @@ } }, "node_modules/markdown-to-jsx": { - "version": "7.2.1", - "resolved": "https://registry.npmjs.org/markdown-to-jsx/-/markdown-to-jsx-7.2.1.tgz", - "integrity": "sha512-9HrdzBAo0+sFz9ZYAGT5fB8ilzTW+q6lPocRxrIesMO+aB40V9MgFfbfMXxlGjf22OpRy+IXlvVaQenicdpgbg==", + "version": "7.3.2", + "resolved": "https://registry.npmjs.org/markdown-to-jsx/-/markdown-to-jsx-7.3.2.tgz", + "integrity": "sha512-B+28F5ucp83aQm+OxNrPkS8z0tMKaeHiy0lHJs3LqCyDQFtWuenaIrkaVTgAm1pf1AU85LXltva86hlaT17i8Q==", "engines": { "node": ">= 10" }, @@ -14664,9 +14793,9 @@ } }, "node_modules/node-abi/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -14816,6 +14945,20 @@ "resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.10.tgz", "integrity": "sha512-5GFldHPXVG/YZmFzJvKK2zDSzPKhEp0+ZR5SVaoSag9fsL5YgHbUHDfnG5494ISANDcK4KwPXAx2xqVEydmd7w==" }, + "node_modules/nopt": { + "version": "1.0.10", + "resolved": "https://registry.npmjs.org/nopt/-/nopt-1.0.10.tgz", + "integrity": "sha512-NWmpvLSqUrgrAC9HCuxEvb+PSloHpqVu+FqcO4eeF2h5qYRhA7ev6KvelyQAKtegUbC6RypJnlEOhd8vloNKYg==", + "dependencies": { + "abbrev": "1" + }, + "bin": { + "nopt": "bin/nopt.js" + }, + "engines": { + "node": "*" + } + }, "node_modules/normalize-path": { "version": "3.0.0", "resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz", @@ -15352,9 +15495,9 @@ } }, "node_modules/package-json/node_modules/semver": { - "version": "6.3.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", - "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "version": "6.3.1", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", + "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", "bin": { "semver": "bin/semver.js" } @@ -15817,17 +15960,6 @@ "resolved": "https://registry.npmjs.org/platform/-/platform-1.3.6.tgz", "integrity": "sha512-fnWVljUchTro6RiCFvCXBbNhJc2NijN7oIQxbwsyL0buWJPG85v81ehlHI9fXrJsMNgTofEoWIQeClKpgxFLrg==" }, - "node_modules/popper.js": { - "version": "1.16.1", - "resolved": "https://registry.npmjs.org/popper.js/-/popper.js-1.16.1.tgz", - "integrity": "sha512-Wb4p1J4zyFTbM+u6WuO4XstYx4Ky9Cewe4DWrel7B0w6VVICvPwdOpotjzcf6eD8TsckVnIMNONQyPIUFOUbCQ==", - "deprecated": "You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1", - "peer": true, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/popperjs" - } - }, "node_modules/postcss": { "version": "8.4.21", "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.4.21.tgz", @@ -15980,9 +16112,9 @@ } }, "node_modules/postcss-loader/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -16360,6 +16492,15 @@ "resolved": "https://registry.npmjs.org/postcss-value-parser/-/postcss-value-parser-4.2.0.tgz", "integrity": "sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==" }, + "node_modules/preact": { + "version": "10.17.1", + "resolved": "https://registry.npmjs.org/preact/-/preact-10.17.1.tgz", + "integrity": "sha512-X9BODrvQ4Ekwv9GURm9AKAGaomqXmip7NQTZgY7gcNmr7XE83adOMJvd3N42id1tMFU7ojiynRsYnY6/BRFxLA==", + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/preact" + } + }, "node_modules/prebuild-install": { "version": "7.1.1", "resolved": "https://registry.npmjs.org/prebuild-install/-/prebuild-install-7.1.1.tgz", @@ -16410,15 +16551,15 @@ } }, "node_modules/prettier": { - "version": "2.8.8", - "resolved": "https://registry.npmjs.org/prettier/-/prettier-2.8.8.tgz", - "integrity": "sha512-tdN8qQGvNjw4CHbY+XXk0JgCXn9QiF21a55rBe5LJAU+kDyC4WQn4+awm2Xfk2lQMk5fKup9XgzTZtGkjBdP9Q==", + "version": "3.0.3", + "resolved": "https://registry.npmjs.org/prettier/-/prettier-3.0.3.tgz", + "integrity": "sha512-L/4pUDMxcNa8R/EthV08Zt42WBO4h1rarVtK0K+QJG0X187OLo7l699jWw0GKuwzkPQ//jMFA/8Xm6Fh3J/DAg==", "dev": true, "bin": { - "prettier": "bin-prettier.js" + "prettier": "bin/prettier.cjs" }, "engines": { - "node": ">=10.13.0" + "node": ">=14" }, "funding": { "url": "https://github.com/prettier/prettier?sponsor=1" @@ -16944,31 +17085,32 @@ } }, "node_modules/react-bootstrap": { - "version": "1.6.7", - "resolved": "https://registry.npmjs.org/react-bootstrap/-/react-bootstrap-1.6.7.tgz", - "integrity": "sha512-IzCYXuLSKDEjGFglbFWk0/iHmdhdcJzTmtS6lXxc0kaNFx2PFgrQf5jKnx5sarF2tiXh9Tgx3pSt3pdK7YwkMA==", - "dependencies": { - "@babel/runtime": "^7.14.0", - "@restart/context": "^2.1.4", - "@restart/hooks": "^0.4.7", - "@types/invariant": "^2.2.33", - "@types/prop-types": "^15.7.3", - "@types/react": ">=16.14.8", - "@types/react-transition-group": "^4.4.1", - "@types/warning": "^3.0.0", - "classnames": "^2.3.1", + "version": "2.8.0", + "resolved": "https://registry.npmjs.org/react-bootstrap/-/react-bootstrap-2.8.0.tgz", + "integrity": "sha512-e/aNtxl0Z2ozrIaR82jr6Zz7ss9GSoaXpQaxmvtDUsTZIq/XalkduR/ZXP6vbQHz2T4syvjA+4FbtwELxxmpww==", + "dependencies": { + "@babel/runtime": "^7.21.0", + "@restart/hooks": "^0.4.9", + "@restart/ui": "^1.6.3", + "@types/react-transition-group": "^4.4.5", + "classnames": "^2.3.2", "dom-helpers": "^5.2.1", "invariant": "^2.2.4", - "prop-types": "^15.7.2", + "prop-types": "^15.8.1", "prop-types-extra": "^1.1.0", - "react-overlays": "^5.1.2", - "react-transition-group": "^4.4.1", + "react-transition-group": "^4.4.5", "uncontrollable": "^7.2.1", "warning": "^4.0.3" }, "peerDependencies": { - "react": ">=16.8.0", - "react-dom": ">=16.8.0" + "@types/react": ">=16.14.8", + "react": ">=16.14.0", + "react-dom": ">=16.14.0" + }, + "peerDependenciesMeta": { + "@types/react": { + "optional": true + } } }, "node_modules/react-dev-utils": { @@ -17167,37 +17309,45 @@ "react": ">=16.3.0" } }, - "node_modules/react-instantsearch-core": { - "version": "6.40.0", - "resolved": "https://registry.npmjs.org/react-instantsearch-core/-/react-instantsearch-core-6.40.0.tgz", - "integrity": "sha512-YCLEtW5ar+h6fQbo03KYUJq/G2BFIuwvD482JqqZ3FhSDzQSgM0ShsfrPgU3AotfZvml4rePyBKyJw6U/O0MIQ==", + "node_modules/react-instantsearch": { + "version": "7.1.0", + "resolved": "https://registry.npmjs.org/react-instantsearch/-/react-instantsearch-7.1.0.tgz", + "integrity": "sha512-AdOP2+ubNVZCkODi45IXpWo9AklTjEGm9xqFQ227zt6CA6NLVhY5otFGkWPBrQwwbEnSKO5PH563pfNGnCMsRQ==", "dependencies": { "@babel/runtime": "^7.1.2", - "algoliasearch-helper": "^3.13.0", - "prop-types": "^15.6.2", - "react-fast-compare": "^3.0.0" + "instantsearch.js": "4.57.0", + "react-instantsearch-core": "7.1.0" }, "peerDependencies": { "algoliasearch": ">= 3.1 < 5", - "react": ">= 16.3.0 < 19" + "react": ">= 16.8.0 < 19", + "react-dom": ">= 16.8.0 < 19" + } + }, + "node_modules/react-instantsearch/node_modules/algoliasearch-helper": { + "version": "3.14.2", + "resolved": "https://registry.npmjs.org/algoliasearch-helper/-/algoliasearch-helper-3.14.2.tgz", + "integrity": "sha512-FjDSrjvQvJT/SKMW74nPgFpsoPUwZCzGbCqbp8HhBFfSk/OvNFxzCaCmuO0p7AWeLy1gD+muFwQEkBwcl5H4pg==", + "dependencies": { + "@algolia/events": "^4.0.1" + }, + "peerDependencies": { + "algoliasearch": ">= 3.1 < 6" } }, - "node_modules/react-instantsearch-dom": { - "version": "6.40.0", - "resolved": "https://registry.npmjs.org/react-instantsearch-dom/-/react-instantsearch-dom-6.40.0.tgz", - "integrity": "sha512-bD+xIi05DeQ47svD4bMgv7rKpl2eKoDOjBU2rcQNBz9N9ryE1IOe6NWAHaDZWBd99eWX9Opwa1JHr3KtNtv2yA==", + "node_modules/react-instantsearch/node_modules/react-instantsearch-core": { + "version": "7.1.0", + "resolved": "https://registry.npmjs.org/react-instantsearch-core/-/react-instantsearch-core-7.1.0.tgz", + "integrity": "sha512-f+QZqUhQ1my/c//kw23Tn8jO1LQVqGRh8ObCbHnDzSPyI9Kp5+ETvI0BbXby1I4iObIjE1ApLhugBkli77zsTQ==", "dependencies": { "@babel/runtime": "^7.1.2", - "algoliasearch-helper": "^3.13.0", - "classnames": "^2.2.5", - "prop-types": "^15.6.2", - "react-fast-compare": "^3.0.0", - "react-instantsearch-core": "6.40.0" + "algoliasearch-helper": "3.14.2", + "instantsearch.js": "4.57.0", + "use-sync-external-store": "^1.0.0" }, "peerDependencies": { "algoliasearch": ">= 3.1 < 5", - "react": ">= 16.3.0 < 19", - "react-dom": ">= 16.3.0 < 19" + "react": ">= 16.8.0 < 19" } }, "node_modules/react-is": { @@ -17210,25 +17360,6 @@ "resolved": "https://registry.npmjs.org/react-lifecycles-compat/-/react-lifecycles-compat-3.0.4.tgz", "integrity": "sha512-fBASbA6LnOU9dOU2eW7aQ8xmYBSXUIWr+UmF9b1efZBazGNO+rcXT/icdKnYm2pTwcRylVUYwW7H1PHfLekVzA==" }, - "node_modules/react-overlays": { - "version": "5.2.1", - "resolved": "https://registry.npmjs.org/react-overlays/-/react-overlays-5.2.1.tgz", - "integrity": "sha512-GLLSOLWr21CqtJn8geSwQfoJufdt3mfdsnIiQswouuQ2MMPns+ihZklxvsTDKD3cR2tF8ELbi5xUsvqVhR6WvA==", - "dependencies": { - "@babel/runtime": "^7.13.8", - "@popperjs/core": "^2.11.6", - "@restart/hooks": "^0.4.7", - "@types/warning": "^3.0.0", - "dom-helpers": "^5.2.0", - "prop-types": "^15.7.2", - "uncontrollable": "^7.2.1", - "warning": "^4.0.3" - }, - "peerDependencies": { - "react": ">=16.3.0", - "react-dom": ">=16.3.0" - } - }, "node_modules/react-refresh": { "version": "0.14.0", "resolved": "https://registry.npmjs.org/react-refresh/-/react-refresh-0.14.0.tgz", @@ -18557,9 +18688,9 @@ } }, "node_modules/sass": { - "version": "1.63.4", - "resolved": "https://registry.npmjs.org/sass/-/sass-1.63.4.tgz", - "integrity": "sha512-Sx/+weUmK+oiIlI+9sdD0wZHsqpbgQg8wSwSnGBjwb5GwqFhYNwwnI+UWZtLjKvKyFlKkatRK235qQ3mokyPoQ==", + "version": "1.68.0", + "resolved": "https://registry.npmjs.org/sass/-/sass-1.68.0.tgz", + "integrity": "sha512-Lmj9lM/fef0nQswm1J2HJcEsBUba4wgNx2fea6yJHODREoMFnwRpZydBnX/RjyXw2REIwdkbqE4hrTo4qfDBUA==", "dependencies": { "chokidar": ">=3.0.0 <4.0.0", "immutable": "^4.0.0", @@ -18620,9 +18751,9 @@ } }, "node_modules/sass-loader/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -18673,6 +18804,11 @@ "url": "https://opencollective.com/webpack" } }, + "node_modules/search-insights": { + "version": "2.8.2", + "resolved": "https://registry.npmjs.org/search-insights/-/search-insights-2.8.2.tgz", + "integrity": "sha512-PxA9M5Q2bpBelVvJ3oDZR8nuY00Z6qwOxL53wNpgzV28M/D6u9WUbImDckjLSILBF8F1hn/mgyuUaOPtjow4Qw==" + }, "node_modules/section-matter": { "version": "1.0.0", "resolved": "https://registry.npmjs.org/section-matter/-/section-matter-1.0.0.tgz", @@ -18686,9 +18822,9 @@ } }, "node_modules/semver": { - "version": "5.7.1", - "resolved": "https://registry.npmjs.org/semver/-/semver-5.7.1.tgz", - "integrity": "sha512-sauaDf/PZdVgrLTNYHRtpXa1iRiKcaebiKQ1BJdpQlWH2lCvexQdX55snPFyK7QzpudqbCI0qXFfOasHdyNDGQ==", + "version": "5.7.2", + "resolved": "https://registry.npmjs.org/semver/-/semver-5.7.2.tgz", + "integrity": "sha512-cBznnQ9KjJqU67B52RMC65CMarK2600WFnbkcaiwWq3xy/5haFJlshgnpjovMVJ+Hff49d8GEn0b87C5pDQ10g==", "bin": { "semver": "bin/semver" } @@ -18711,9 +18847,9 @@ } }, "node_modules/semver-diff/node_modules/semver": { - "version": "6.3.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", - "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "version": "6.3.1", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", + "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", "bin": { "semver": "bin/semver.js" } @@ -18880,9 +19016,9 @@ "integrity": "sha512-eh0GgfEkpnoWDq+VY8OyvYhFEzBk6jIYbRKdIlyTiAXIVJ8PyBaKb0rp7oDtoddbdoHWhq8wwr+XZ81F1rpNdA==" }, "node_modules/sharp/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -20856,9 +20992,9 @@ } }, "node_modules/update-notifier/node_modules/semver": { - "version": "7.4.0", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.4.0.tgz", - "integrity": "sha512-RgOxM8Mw+7Zus0+zcLEUn8+JfoLpj/huFTItQy2hsM4khuC1HYRDp0cU482Ewn/Fcy6bCjufD8vAj7voC66KQw==", + "version": "7.5.4", + "resolved": "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz", + "integrity": "sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA==", "dependencies": { "lru-cache": "^6.0.0" }, @@ -20966,6 +21102,14 @@ "resolved": "https://registry.npmjs.org/punycode/-/punycode-1.3.2.tgz", "integrity": "sha512-RofWgt/7fL5wP1Y7fxE7/EmTLzQVnB0ycyibJ0OOHIlJqTNzglYFxVwETOcIoJqJmpDXJ9xImDv+Fq34F/d4Dw==" }, + "node_modules/use-sync-external-store": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/use-sync-external-store/-/use-sync-external-store-1.2.0.tgz", + "integrity": "sha512-eEgnFxGQ1Ife9bzYs6VLi8/4X6CObHMw9Qr9tPY43iKwsPw8xE8+EFsf/2cFZ5S3esXgpWgtSCtLNS41F+sKPA==", + "peerDependencies": { + "react": "^16.8.0 || ^17.0.0 || ^18.0.0" + } + }, "node_modules/utf8-byte-length": { "version": "1.0.4", "resolved": "https://registry.npmjs.org/utf8-byte-length/-/utf8-byte-length-1.0.4.tgz", @@ -21408,9 +21552,9 @@ "integrity": "sha512-JcKqAHLPxcdb9KM49dufGXn2x3ssnfjbcaQdLlfZsL9rH9wgDQjUtDxbo8NE0F6SFvydeu1VhZe7hZuHsB2/pw==" }, "node_modules/word-wrap": { - "version": "1.2.3", - "resolved": "https://registry.npmjs.org/word-wrap/-/word-wrap-1.2.3.tgz", - "integrity": "sha512-Hz/mrNwitNRh/HUAtM/VT/5VH+ygD6DV7mYKZAtHOrbs8U7lvPS6xf7EJKMF0uW1KJCl0H701g3ZGus+muE5vQ==", + "version": "1.2.5", + "resolved": "https://registry.npmjs.org/word-wrap/-/word-wrap-1.2.5.tgz", + "integrity": "sha512-BN22B5eaMMI9UMtjrGd5g5eCYPpCPDUy0FJXbYsaT5zYxjFOckS53SQDE3pWkVoWpHXVb3BrYcEN4Twa55B5cA==", "engines": { "node": ">=0.10.0" } diff --git a/package.json b/package.json index 77a1457ee79..e4bd45221f6 100644 --- a/package.json +++ b/package.json @@ -35,13 +35,13 @@ "update-icons": "node scripts/createIconNames.js && prettier --write src/components/icon/iconNames.js" }, "dependencies": { - "@enterprisedb/icons": "^1.25.1", + "@enterprisedb/icons": "^1.26.1", "@mdx-js/mdx": "^1.6.22", "@mdx-js/react": "^1.6.22", - "algoliasearch": "^4.17.2", + "algoliasearch": "^4.20.0", "balance-text": "^3.3.1", "bl": "5.0.0", - "bootstrap": "^4.6.2", + "bootstrap": "^5.3.2", "gatsby": "^4.25.7", "gatsby-cli": "^4.25.0", "gatsby-plugin-algolia": "^0.26.0", @@ -69,26 +69,26 @@ "graceful-fs": "^4.2.11", "hast-util-to-string": "^1.0.4", "is-absolute-url": "^4.0.1", - "markdown-to-jsx": "^7.2.1", + "markdown-to-jsx": "^7.3.2", "mdast-util-to-string": "^2.0.0", "prismjs": "^1.29.0", "react": "^18.2.0", - "react-bootstrap": "^1.6.7", + "react-bootstrap": "^2.8.0", "react-dom": "^18.2.0", "react-helmet": "^6.1.0", - "react-instantsearch-dom": "^6.40.0", + "react-instantsearch": "^7.1.0", "rehype-parse": "^7.0.1", "remark-admonitions": "github:josh-heyer/remark-admonitions", - "sass": "^1.63.4", + "sass": "^1.68.0", "truncate-utf8-bytes": "^1.0.2", "unist-util-visit-parents": "^3.1.1" }, "devDependencies": { - "fast-glob": "^3.2.12", + "fast-glob": "^3.3.1", "hast-util-is-element": "^2.1.3", "hast-util-to-text": "^3.1.2", - "husky": "^7.0.4", - "prettier": "^2.8.8", + "husky": "^8.0.3", + "prettier": "^3.0.3", "pretty-quick": "^3.1.3", "react-refresh": "^0.14.0", "rehype-format": "^3.1.0", diff --git a/src/styles/_docs.scss b/src/styles/_docs.scss index 6b07d01a5d6..1df5336764c 100644 --- a/src/styles/_docs.scss +++ b/src/styles/_docs.scss @@ -29,7 +29,7 @@ label.link-label { text-decoration: $link-decoration; cursor: pointer; - @include hover() { + &:hover { color: $link-hover-color; text-decoration: $link-hover-decoration; } From 9bf8b953eba8a420f7cc31a5365dd911d69e23fd Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Wed, 27 Sep 2023 14:27:54 +0000 Subject: [PATCH 184/255] Fixes for Algolia and Bootstrap - switch to instantsearch 7 API - address breaking changes in boostrap 5 - fix: incorrect path parsing for 404 page search - fix: race condition in global search bar initialization - fix: product filter dropdown appears behind search results in global search - fix: honor system dark mode preference when no local preference is set Also replaced pretty-quick with lint-staged, as new prettier is unsupported by the former --- .husky/pre-commit | 2 +- gatsby-ssr.js | 3 +- package-lock.json | 1004 ++++++++++++----- package.json | 6 +- src/components/advanced-search/filtering.js | 182 ++- src/components/advanced-search/form.js | 139 +-- src/components/advanced-search/hitComps.js | 6 +- src/components/advanced-search/queryParams.js | 4 +- src/components/advanced-search/results.js | 191 ++-- src/components/back-button.js | 4 +- src/components/card-decks.js | 30 +- src/components/code-block.js | 2 +- src/components/dark-mode-toggle.js | 2 +- src/components/feedback-dropdown.js | 4 +- src/components/icon/iconList.js | 2 +- src/components/index-links.js | 6 +- src/components/index-sub-nav.js | 2 +- src/components/katacoda-page-link.js | 10 +- src/components/katacoda-panel.js | 16 +- src/components/layout.js | 12 +- src/components/left-nav.js | 8 +- src/components/main-content.js | 2 +- src/components/pdf-download.js | 2 +- src/components/prev-next.js | 4 +- src/components/search-navigation-links.js | 2 +- src/components/search-navigation.js | 6 +- src/components/search/formComps.js | 98 +- src/components/search/hitComps.js | 8 +- src/components/search/index.js | 54 +- src/components/side-navigation.js | 12 +- src/components/table-of-contents.js | 16 +- src/components/top-bar.js | 5 +- src/components/tree-node.js | 8 +- src/components/version-dropdown.js | 5 +- src/pages/404.js | 103 +- src/pages/index.js | 783 ++++++------- src/pages/search.js | 28 +- src/styles/_docs.scss | 10 +- src/styles/_theme.scss | 1 + src/templates/doc-stub.js | 4 +- src/templates/doc.js | 6 +- 41 files changed, 1612 insertions(+), 1180 deletions(-) diff --git a/.husky/pre-commit b/.husky/pre-commit index c2555fb8c2f..36af219892f 100755 --- a/.husky/pre-commit +++ b/.husky/pre-commit @@ -1,4 +1,4 @@ #!/bin/sh . "$(dirname "$0")/_/husky.sh" -npx pretty-quick --staged --pattern 'src/**/*.js' --pattern 'gatsby-*.js' +npx lint-staged diff --git a/gatsby-ssr.js b/gatsby-ssr.js index 1ebc105d39f..9078bd5ae98 100644 --- a/gatsby-ssr.js +++ b/gatsby-ssr.js @@ -8,8 +8,9 @@ exports.onRenderBody = ({ setPreBodyComponents }) => { __html: ` const storedDark = window.localStorage.getItem('dark'); const inferredDark = window.matchMedia('(prefers-color-scheme: dark)').matches; - if (storedDark === 'true' || (storedDark === null && inferredDark)) { + if (storedDark === 'true' || (storedDark !== false && inferredDark)) { document.documentElement.classList.add('dark'); + document.documentElement.dataset['bsTheme'] = 'dark'; } `, }, diff --git a/package-lock.json b/package-lock.json index be52c71cb06..a5520390a11 100644 --- a/package-lock.json +++ b/package-lock.json @@ -44,6 +44,7 @@ "hast-util-to-string": "^1.0.4", "is-absolute-url": "^4.0.1", "markdown-to-jsx": "^7.3.2", + "masonry-layout": "^4.2.2", "mdast-util-to-string": "^2.0.0", "prismjs": "^1.29.0", "react": "^18.2.0", @@ -62,8 +63,8 @@ "hast-util-is-element": "^2.1.3", "hast-util-to-text": "^3.1.2", "husky": "^8.0.3", + "lint-staged": "^14.0.1", "prettier": "^3.0.3", - "pretty-quick": "^3.1.3", "react-refresh": "^0.14.0", "rehype-format": "^3.1.0", "rehype-remark": "^8.1.1", @@ -5097,15 +5098,6 @@ "url": "https://github.com/sponsors/ljharb" } }, - "node_modules/array-differ": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/array-differ/-/array-differ-3.0.0.tgz", - "integrity": "sha512-THtfYS6KtME/yIAhKjZ2ul7XI96lQGHRputJQHO80LAWQnuGP4iCIN8vdMRboGbIEYBwU33q8Tch1os2+X0kMg==", - "dev": true, - "engines": { - "node": ">=8" - } - }, "node_modules/array-flatten": { "version": "1.1.1", "resolved": "https://registry.npmjs.org/array-flatten/-/array-flatten-1.1.1.tgz", @@ -6334,6 +6326,106 @@ "node": ">=8" } }, + "node_modules/cli-truncate": { + "version": "3.1.0", + "resolved": "https://registry.npmjs.org/cli-truncate/-/cli-truncate-3.1.0.tgz", + "integrity": "sha512-wfOBkjXteqSnI59oPcJkcPl/ZmwvMMOj340qUIY1SKZCv0B9Cf4D4fAucRkIKQmsIuYK3x1rrgU7MeGRruiuiA==", + "dev": true, + "dependencies": { + "slice-ansi": "^5.0.0", + "string-width": "^5.0.0" + }, + "engines": { + "node": "^12.20.0 || ^14.13.1 || >=16.0.0" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/cli-truncate/node_modules/ansi-regex": { + "version": "6.0.1", + "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-6.0.1.tgz", + "integrity": "sha512-n5M855fKb2SsfMIiFFoVrABHJC8QtHwVx+mHWP3QcEqBHYienj5dHSgjbxtC0WEZXYt4wcD6zrQElDPhFuZgfA==", + "dev": true, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/chalk/ansi-regex?sponsor=1" + } + }, + "node_modules/cli-truncate/node_modules/ansi-styles": { + "version": "6.2.1", + "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-6.2.1.tgz", + "integrity": "sha512-bN798gFfQX+viw3R7yrGWRqnrN2oRkEkUjjl4JNn4E8GxxbjtG3FbrEIIY3l8/hrwUwIeCZvi4QuOTP4MErVug==", + "dev": true, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/chalk/ansi-styles?sponsor=1" + } + }, + "node_modules/cli-truncate/node_modules/is-fullwidth-code-point": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-4.0.0.tgz", + "integrity": "sha512-O4L094N2/dZ7xqVdrXhh9r1KODPJpFms8B5sGdJLPy664AgvXsreZUyCQQNItZRDlYug4xStLjNp/sz3HvBowQ==", + "dev": true, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/cli-truncate/node_modules/slice-ansi": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/slice-ansi/-/slice-ansi-5.0.0.tgz", + "integrity": "sha512-FC+lgizVPfie0kkhqUScwRu1O/lF6NOgJmlCgK+/LYxDCTk8sGelYaHDhFcDN+Sn3Cv+3VSa4Byeo+IMCzpMgQ==", + "dev": true, + "dependencies": { + "ansi-styles": "^6.0.0", + "is-fullwidth-code-point": "^4.0.0" + }, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/chalk/slice-ansi?sponsor=1" + } + }, + "node_modules/cli-truncate/node_modules/string-width": { + "version": "5.1.2", + "resolved": "https://registry.npmjs.org/string-width/-/string-width-5.1.2.tgz", + "integrity": "sha512-HnLOCR3vjcY8beoNLtcjZ5/nxn2afmME6lhrDrebokqMap+XbeW8n9TXpPDOqdGK5qcI3oT0GKTW6wC7EMiVqA==", + "dev": true, + "dependencies": { + "eastasianwidth": "^0.2.0", + "emoji-regex": "^9.2.2", + "strip-ansi": "^7.0.1" + }, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/cli-truncate/node_modules/strip-ansi": { + "version": "7.1.0", + "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-7.1.0.tgz", + "integrity": "sha512-iq6eVVI64nQQTRYq2KtEg2d2uU7LElhTJwsH4YzIHZshxlgZms/wIc4VoDQTlG/IvVIrBKG06CrZnp0qv7hkcQ==", + "dev": true, + "dependencies": { + "ansi-regex": "^6.0.1" + }, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/chalk/strip-ansi?sponsor=1" + } + }, "node_modules/cli-width": { "version": "3.0.0", "resolved": "https://registry.npmjs.org/cli-width/-/cli-width-3.0.0.tgz", @@ -7427,6 +7519,11 @@ "node": ">=6" } }, + "node_modules/desandro-matches-selector": { + "version": "2.0.2", + "resolved": "https://registry.npmjs.org/desandro-matches-selector/-/desandro-matches-selector-2.0.2.tgz", + "integrity": "sha512-+1q0nXhdzg1IpIJdMKalUwvvskeKnYyEe3shPRwedNcWtnhEKT3ZxvFjzywHDeGcKViIxTCAoOYQWP1qD7VNyg==" + }, "node_modules/destroy": { "version": "1.2.0", "resolved": "https://registry.npmjs.org/destroy/-/destroy-1.2.0.tgz", @@ -7693,6 +7790,12 @@ "resolved": "https://registry.npmjs.org/duplexer3/-/duplexer3-0.1.5.tgz", "integrity": "sha512-1A8za6ws41LQgv9HrE/66jyC5yuSjQ3L/KOpFtoBilsAK2iA2wuS5rTt1OCzIvtS2V7nVmedsUU+DGRcjBmOYA==" }, + "node_modules/eastasianwidth": { + "version": "0.2.0", + "resolved": "https://registry.npmjs.org/eastasianwidth/-/eastasianwidth-0.2.0.tgz", + "integrity": "sha512-I88TYZWc9XiYHRQ4/3c5rjjfgkjhLyW2luGIheGERbNQ6OY7yTybanSpDXZa8y7VUP9YmDcYa+eyq4ca7iLqWA==", + "dev": true + }, "node_modules/ee-first": { "version": "1.1.1", "resolved": "https://registry.npmjs.org/ee-first/-/ee-first-1.1.1.tgz", @@ -8686,6 +8789,11 @@ "node": ">= 0.6" } }, + "node_modules/ev-emitter": { + "version": "1.1.1", + "resolved": "https://registry.npmjs.org/ev-emitter/-/ev-emitter-1.1.1.tgz", + "integrity": "sha512-ipiDYhdQSCZ4hSbX4rMW+XzNKMD1prg/sTvoVmSLkuQ1MVlwjJQQA+sW8tMYR3BLUr9KjodFV4pvzunvRhd33Q==" + }, "node_modules/eval": { "version": "0.1.8", "resolved": "https://registry.npmjs.org/eval/-/eval-0.1.8.tgz", @@ -9211,6 +9319,14 @@ "url": "https://github.com/sponsors/sindresorhus" } }, + "node_modules/fizzy-ui-utils": { + "version": "2.0.7", + "resolved": "https://registry.npmjs.org/fizzy-ui-utils/-/fizzy-ui-utils-2.0.7.tgz", + "integrity": "sha512-CZXDVXQ1If3/r8s0T+v+qVeMshhfcuq0rqIFgJnrtd+Bu8GmDmqMjntjUePypVtjHXKJ6V4sw9zeyox34n9aCg==", + "dependencies": { + "desandro-matches-selector": "^2.0.0" + } + }, "node_modules/flat-cache": { "version": "3.0.4", "resolved": "https://registry.npmjs.org/flat-cache/-/flat-cache-3.0.4.tgz", @@ -11466,6 +11582,11 @@ "node": ">=4" } }, + "node_modules/get-size": { + "version": "2.0.3", + "resolved": "https://registry.npmjs.org/get-size/-/get-size-2.0.3.tgz", + "integrity": "sha512-lXNzT/h/dTjTxRbm9BXb+SGxxzkm97h/PCIKtlN/CBCxxmkkIVV21udumMS93MuVTDX583gqc94v3RjuHmI+2Q==" + }, "node_modules/get-stream": { "version": "6.0.1", "resolved": "https://registry.npmjs.org/get-stream/-/get-stream-6.0.1.tgz", @@ -13601,106 +13722,383 @@ "resolved": "https://registry.npmjs.org/lines-and-columns/-/lines-and-columns-1.2.4.tgz", "integrity": "sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==" }, - "node_modules/lmdb": { - "version": "2.5.3", - "resolved": "https://registry.npmjs.org/lmdb/-/lmdb-2.5.3.tgz", - "integrity": "sha512-iBA0cb13CobBSoGJLfZgnrykLlfJipDAnvtf+YwIqqzBEsTeQYsXrHaSBkaHd5wCWeabwrNvhjZoFMUrlo+eLw==", - "hasInstallScript": true, + "node_modules/lint-staged": { + "version": "14.0.1", + "resolved": "https://registry.npmjs.org/lint-staged/-/lint-staged-14.0.1.tgz", + "integrity": "sha512-Mw0cL6HXnHN1ag0mN/Dg4g6sr8uf8sn98w2Oc1ECtFto9tvRF7nkXGJRbx8gPlHyoR0pLyBr2lQHbWwmUHe1Sw==", + "dev": true, "dependencies": { - "msgpackr": "^1.5.4", - "node-addon-api": "^4.3.0", - "node-gyp-build-optional-packages": "5.0.3", - "ordered-binary": "^1.2.4", - "weak-lru-cache": "^1.2.2" + "chalk": "5.3.0", + "commander": "11.0.0", + "debug": "4.3.4", + "execa": "7.2.0", + "lilconfig": "2.1.0", + "listr2": "6.6.1", + "micromatch": "4.0.5", + "pidtree": "0.6.0", + "string-argv": "0.3.2", + "yaml": "2.3.1" }, - "optionalDependencies": { - "@lmdb/lmdb-darwin-arm64": "2.5.3", - "@lmdb/lmdb-darwin-x64": "2.5.3", - "@lmdb/lmdb-linux-arm": "2.5.3", - "@lmdb/lmdb-linux-arm64": "2.5.3", - "@lmdb/lmdb-linux-x64": "2.5.3", - "@lmdb/lmdb-win32-x64": "2.5.3" + "bin": { + "lint-staged": "bin/lint-staged.js" + }, + "engines": { + "node": "^16.14.0 || >=18.0.0" + }, + "funding": { + "url": "https://opencollective.com/lint-staged" } }, - "node_modules/lmdb/node_modules/node-addon-api": { - "version": "4.3.0", - "resolved": "https://registry.npmjs.org/node-addon-api/-/node-addon-api-4.3.0.tgz", - "integrity": "sha512-73sE9+3UaLYYFmDsFZnqCInzPyh3MqIwZO9cw58yIqAZhONrrabrYyYe3TuIqtIiOuTXVhsGau8hcrhhwSsDIQ==" + "node_modules/lint-staged/node_modules/chalk": { + "version": "5.3.0", + "resolved": "https://registry.npmjs.org/chalk/-/chalk-5.3.0.tgz", + "integrity": "sha512-dLitG79d+GV1Nb/VYcCDFivJeK1hiukt9QjRNVOsUtTy1rR1YJsmpGGTZ3qJos+uw7WmWF4wUwBd9jxjocFC2w==", + "dev": true, + "engines": { + "node": "^12.17.0 || ^14.13 || >=16.0.0" + }, + "funding": { + "url": "https://github.com/chalk/chalk?sponsor=1" + } }, - "node_modules/loader-runner": { - "version": "4.3.0", - "resolved": "https://registry.npmjs.org/loader-runner/-/loader-runner-4.3.0.tgz", - "integrity": "sha512-3R/1M+yS3j5ou80Me59j7F9IMs4PXs3VqRrm0TU3AbKPxlmpoY1TNscJV/oGJXo8qCatFGTfDbY6W6ipGOYXfg==", + "node_modules/lint-staged/node_modules/commander": { + "version": "11.0.0", + "resolved": "https://registry.npmjs.org/commander/-/commander-11.0.0.tgz", + "integrity": "sha512-9HMlXtt/BNoYr8ooyjjNRdIilOTkVJXB+GhxMTtOKwk0R4j4lS4NpjuqmRxroBfnfTSHQIHQB7wryHhXarNjmQ==", + "dev": true, "engines": { - "node": ">=6.11.5" + "node": ">=16" } }, - "node_modules/loader-utils": { - "version": "2.0.4", - "resolved": "https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.4.tgz", - "integrity": "sha512-xXqpXoINfFhgua9xiqD8fPFHgkoq1mmmpE92WlDbm9rNRd/EbRb+Gqf908T2DMfuHjjJlksiK2RbHVOdD/MqSw==", + "node_modules/lint-staged/node_modules/execa": { + "version": "7.2.0", + "resolved": "https://registry.npmjs.org/execa/-/execa-7.2.0.tgz", + "integrity": "sha512-UduyVP7TLB5IcAQl+OzLyLcS/l32W/GLg+AhHJ+ow40FOk2U3SAllPwR44v4vmdFwIWqpdwxxpQbF1n5ta9seA==", + "dev": true, "dependencies": { - "big.js": "^5.2.2", - "emojis-list": "^3.0.0", - "json5": "^2.1.2" + "cross-spawn": "^7.0.3", + "get-stream": "^6.0.1", + "human-signals": "^4.3.0", + "is-stream": "^3.0.0", + "merge-stream": "^2.0.0", + "npm-run-path": "^5.1.0", + "onetime": "^6.0.0", + "signal-exit": "^3.0.7", + "strip-final-newline": "^3.0.0" }, "engines": { - "node": ">=8.9.0" + "node": "^14.18.0 || ^16.14.0 || >=18.0.0" + }, + "funding": { + "url": "https://github.com/sindresorhus/execa?sponsor=1" } }, - "node_modules/locate-path": { - "version": "6.0.0", - "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-6.0.0.tgz", - "integrity": "sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==", - "dependencies": { - "p-locate": "^5.0.0" + "node_modules/lint-staged/node_modules/human-signals": { + "version": "4.3.1", + "resolved": "https://registry.npmjs.org/human-signals/-/human-signals-4.3.1.tgz", + "integrity": "sha512-nZXjEF2nbo7lIw3mgYjItAfgQXog3OjJogSbKa2CQIIvSGWcKgeJnQlNXip6NglNzYH45nSRiEVimMvYL8DDqQ==", + "dev": true, + "engines": { + "node": ">=14.18.0" + } + }, + "node_modules/lint-staged/node_modules/is-stream": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/is-stream/-/is-stream-3.0.0.tgz", + "integrity": "sha512-LnQR4bZ9IADDRSkvpqMGvt/tEJWclzklNgSw48V5EAaAeDd6qGvN8ei6k5p0tvxSR171VmGyHuTiAOfxAbr8kA==", + "dev": true, + "engines": { + "node": "^12.20.0 || ^14.13.1 || >=16.0.0" }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/lint-staged/node_modules/mimic-fn": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/mimic-fn/-/mimic-fn-4.0.0.tgz", + "integrity": "sha512-vqiC06CuhBTUdZH+RYl8sFrL096vA45Ok5ISO6sE/Mr1jRbGH4Csnhi8f3wKVl7x8mO4Au7Ir9D3Oyv1VYMFJw==", + "dev": true, "engines": { - "node": ">=10" + "node": ">=12" }, "funding": { "url": "https://github.com/sponsors/sindresorhus" } }, - "node_modules/lock": { - "version": "1.1.0", - "resolved": "https://registry.npmjs.org/lock/-/lock-1.1.0.tgz", - "integrity": "sha512-NZQIJJL5Rb9lMJ0Yl1JoVr9GSdo4HTPsUEWsSFzB8dE8DSoiLCVavWZPi7Rnlv/o73u6I24S/XYc/NmG4l8EKA==" + "node_modules/lint-staged/node_modules/npm-run-path": { + "version": "5.1.0", + "resolved": "https://registry.npmjs.org/npm-run-path/-/npm-run-path-5.1.0.tgz", + "integrity": "sha512-sJOdmRGrY2sjNTRMbSvluQqg+8X7ZK61yvzBEIDhz4f8z1TZFYABsqjjCBd/0PUNE9M6QDgHJXQkGUEm7Q+l9Q==", + "dev": true, + "dependencies": { + "path-key": "^4.0.0" + }, + "engines": { + "node": "^12.20.0 || ^14.13.1 || >=16.0.0" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } }, - "node_modules/lockfile": { - "version": "1.0.4", - "resolved": "https://registry.npmjs.org/lockfile/-/lockfile-1.0.4.tgz", - "integrity": "sha512-cvbTwETRfsFh4nHsL1eGWapU1XFi5Ot9E85sWAwia7Y7EgB7vfqcZhTKZ+l7hCGxSPoushMv5GKhT5PdLv03WA==", + "node_modules/lint-staged/node_modules/onetime": { + "version": "6.0.0", + "resolved": "https://registry.npmjs.org/onetime/-/onetime-6.0.0.tgz", + "integrity": "sha512-1FlR+gjXK7X+AsAHso35MnyN5KqGwJRi/31ft6x0M194ht7S+rWAvd7PHss9xSKMzE0asv1pyIHaJYq+BbacAQ==", + "dev": true, "dependencies": { - "signal-exit": "^3.0.2" + "mimic-fn": "^4.0.0" + }, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" } }, - "node_modules/lodash": { - "version": "4.17.21", - "resolved": "https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz", - "integrity": "sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==" + "node_modules/lint-staged/node_modules/path-key": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/path-key/-/path-key-4.0.0.tgz", + "integrity": "sha512-haREypq7xkM7ErfgIyA0z+Bj4AGKlMSdlQE2jvJo6huWD1EdkKYV+G/T4nq0YEF2vgTT8kqMFKo1uHn950r4SQ==", + "dev": true, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } }, - "node_modules/lodash.assignin": { - "version": "4.2.0", - "resolved": "https://registry.npmjs.org/lodash.assignin/-/lodash.assignin-4.2.0.tgz", - "integrity": "sha512-yX/rx6d/UTVh7sSVWVSIMjfnz95evAgDFdb1ZozC35I9mSFCkmzptOzevxjgbQUsc78NR44LVHWjsoMQXy9FDg==" + "node_modules/lint-staged/node_modules/strip-final-newline": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/strip-final-newline/-/strip-final-newline-3.0.0.tgz", + "integrity": "sha512-dOESqjYr96iWYylGObzd39EuNTa5VJxyvVAEm5Jnh7KGo75V43Hk1odPQkNDyXNmUR6k+gEiDVXnjB8HJ3crXw==", + "dev": true, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } }, - "node_modules/lodash.bind": { - "version": "4.2.1", - "resolved": "https://registry.npmjs.org/lodash.bind/-/lodash.bind-4.2.1.tgz", - "integrity": "sha512-lxdsn7xxlCymgLYo1gGvVrfHmkjDiyqVv62FAeF2i5ta72BipE1SLxw8hPEPLhD4/247Ijw07UQH7Hq/chT5LA==" + "node_modules/lint-staged/node_modules/yaml": { + "version": "2.3.1", + "resolved": "https://registry.npmjs.org/yaml/-/yaml-2.3.1.tgz", + "integrity": "sha512-2eHWfjaoXgTBC2jNM1LRef62VQa0umtvRiDSk6HSzW7RvS5YtkabJrwYLLEKWBc8a5U2PTSCs+dJjUTJdlHsWQ==", + "dev": true, + "engines": { + "node": ">= 14" + } }, - "node_modules/lodash.chunk": { - "version": "4.2.0", - "resolved": "https://registry.npmjs.org/lodash.chunk/-/lodash.chunk-4.2.0.tgz", - "integrity": "sha512-ZzydJKfUHJwHa+hF5X66zLFCBrWn5GeF28OHEr4WVWtNDXlQ/IjWKPBiikqKo2ne0+v6JgCgJ0GzJp8k8bHC7w==" + "node_modules/listr2": { + "version": "6.6.1", + "resolved": "https://registry.npmjs.org/listr2/-/listr2-6.6.1.tgz", + "integrity": "sha512-+rAXGHh0fkEWdXBmX+L6mmfmXmXvDGEKzkjxO+8mP3+nI/r/CWznVBvsibXdxda9Zz0OW2e2ikphN3OwCT/jSg==", + "dev": true, + "dependencies": { + "cli-truncate": "^3.1.0", + "colorette": "^2.0.20", + "eventemitter3": "^5.0.1", + "log-update": "^5.0.1", + "rfdc": "^1.3.0", + "wrap-ansi": "^8.1.0" + }, + "engines": { + "node": ">=16.0.0" + }, + "peerDependencies": { + "enquirer": ">= 2.3.0 < 3" + }, + "peerDependenciesMeta": { + "enquirer": { + "optional": true + } + } }, - "node_modules/lodash.clonedeep": { - "version": "4.5.0", - "resolved": "https://registry.npmjs.org/lodash.clonedeep/-/lodash.clonedeep-4.5.0.tgz", - "integrity": "sha512-H5ZhCF25riFd9uB5UCkVKo61m3S/xZk1x4wA6yp/L3RFP6Z/eHH1ymQcGLo7J3GMPfm0V/7m1tryHuGVxpqEBQ==" + "node_modules/listr2/node_modules/ansi-regex": { + "version": "6.0.1", + "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-6.0.1.tgz", + "integrity": "sha512-n5M855fKb2SsfMIiFFoVrABHJC8QtHwVx+mHWP3QcEqBHYienj5dHSgjbxtC0WEZXYt4wcD6zrQElDPhFuZgfA==", + "dev": true, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/chalk/ansi-regex?sponsor=1" + } }, - "node_modules/lodash.debounce": { + "node_modules/listr2/node_modules/ansi-styles": { + "version": "6.2.1", + "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-6.2.1.tgz", + "integrity": "sha512-bN798gFfQX+viw3R7yrGWRqnrN2oRkEkUjjl4JNn4E8GxxbjtG3FbrEIIY3l8/hrwUwIeCZvi4QuOTP4MErVug==", + "dev": true, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/chalk/ansi-styles?sponsor=1" + } + }, + "node_modules/listr2/node_modules/colorette": { + "version": "2.0.20", + "resolved": "https://registry.npmjs.org/colorette/-/colorette-2.0.20.tgz", + "integrity": "sha512-IfEDxwoWIjkeXL1eXcDiow4UbKjhLdq6/EuSVR9GMN7KVH3r9gQ83e73hsz1Nd1T3ijd5xv1wcWRYO+D6kCI2w==", + "dev": true + }, + "node_modules/listr2/node_modules/eventemitter3": { + "version": "5.0.1", + "resolved": "https://registry.npmjs.org/eventemitter3/-/eventemitter3-5.0.1.tgz", + "integrity": "sha512-GWkBvjiSZK87ELrYOSESUYeVIc9mvLLf/nXalMOS5dYrgZq9o5OVkbZAVM06CVxYsCwH9BDZFPlQTlPA1j4ahA==", + "dev": true + }, + "node_modules/listr2/node_modules/string-width": { + "version": "5.1.2", + "resolved": "https://registry.npmjs.org/string-width/-/string-width-5.1.2.tgz", + "integrity": "sha512-HnLOCR3vjcY8beoNLtcjZ5/nxn2afmME6lhrDrebokqMap+XbeW8n9TXpPDOqdGK5qcI3oT0GKTW6wC7EMiVqA==", + "dev": true, + "dependencies": { + "eastasianwidth": "^0.2.0", + "emoji-regex": "^9.2.2", + "strip-ansi": "^7.0.1" + }, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/listr2/node_modules/strip-ansi": { + "version": "7.1.0", + "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-7.1.0.tgz", + "integrity": "sha512-iq6eVVI64nQQTRYq2KtEg2d2uU7LElhTJwsH4YzIHZshxlgZms/wIc4VoDQTlG/IvVIrBKG06CrZnp0qv7hkcQ==", + "dev": true, + "dependencies": { + "ansi-regex": "^6.0.1" + }, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/chalk/strip-ansi?sponsor=1" + } + }, + "node_modules/listr2/node_modules/wrap-ansi": { + "version": "8.1.0", + "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-8.1.0.tgz", + "integrity": "sha512-si7QWI6zUMq56bESFvagtmzMdGOtoxfR+Sez11Mobfc7tm+VkUckk9bW2UeffTGVUbOksxmSw0AA2gs8g71NCQ==", + "dev": true, + "dependencies": { + "ansi-styles": "^6.1.0", + "string-width": "^5.0.1", + "strip-ansi": "^7.0.1" + }, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/chalk/wrap-ansi?sponsor=1" + } + }, + "node_modules/lmdb": { + "version": "2.5.3", + "resolved": "https://registry.npmjs.org/lmdb/-/lmdb-2.5.3.tgz", + "integrity": "sha512-iBA0cb13CobBSoGJLfZgnrykLlfJipDAnvtf+YwIqqzBEsTeQYsXrHaSBkaHd5wCWeabwrNvhjZoFMUrlo+eLw==", + "hasInstallScript": true, + "dependencies": { + "msgpackr": "^1.5.4", + "node-addon-api": "^4.3.0", + "node-gyp-build-optional-packages": "5.0.3", + "ordered-binary": "^1.2.4", + "weak-lru-cache": "^1.2.2" + }, + "optionalDependencies": { + "@lmdb/lmdb-darwin-arm64": "2.5.3", + "@lmdb/lmdb-darwin-x64": "2.5.3", + "@lmdb/lmdb-linux-arm": "2.5.3", + "@lmdb/lmdb-linux-arm64": "2.5.3", + "@lmdb/lmdb-linux-x64": "2.5.3", + "@lmdb/lmdb-win32-x64": "2.5.3" + } + }, + "node_modules/lmdb/node_modules/node-addon-api": { + "version": "4.3.0", + "resolved": "https://registry.npmjs.org/node-addon-api/-/node-addon-api-4.3.0.tgz", + "integrity": "sha512-73sE9+3UaLYYFmDsFZnqCInzPyh3MqIwZO9cw58yIqAZhONrrabrYyYe3TuIqtIiOuTXVhsGau8hcrhhwSsDIQ==" + }, + "node_modules/loader-runner": { + "version": "4.3.0", + "resolved": "https://registry.npmjs.org/loader-runner/-/loader-runner-4.3.0.tgz", + "integrity": "sha512-3R/1M+yS3j5ou80Me59j7F9IMs4PXs3VqRrm0TU3AbKPxlmpoY1TNscJV/oGJXo8qCatFGTfDbY6W6ipGOYXfg==", + "engines": { + "node": ">=6.11.5" + } + }, + "node_modules/loader-utils": { + "version": "2.0.4", + "resolved": "https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.4.tgz", + "integrity": "sha512-xXqpXoINfFhgua9xiqD8fPFHgkoq1mmmpE92WlDbm9rNRd/EbRb+Gqf908T2DMfuHjjJlksiK2RbHVOdD/MqSw==", + "dependencies": { + "big.js": "^5.2.2", + "emojis-list": "^3.0.0", + "json5": "^2.1.2" + }, + "engines": { + "node": ">=8.9.0" + } + }, + "node_modules/locate-path": { + "version": "6.0.0", + "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-6.0.0.tgz", + "integrity": "sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==", + "dependencies": { + "p-locate": "^5.0.0" + }, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/lock": { + "version": "1.1.0", + "resolved": "https://registry.npmjs.org/lock/-/lock-1.1.0.tgz", + "integrity": "sha512-NZQIJJL5Rb9lMJ0Yl1JoVr9GSdo4HTPsUEWsSFzB8dE8DSoiLCVavWZPi7Rnlv/o73u6I24S/XYc/NmG4l8EKA==" + }, + "node_modules/lockfile": { + "version": "1.0.4", + "resolved": "https://registry.npmjs.org/lockfile/-/lockfile-1.0.4.tgz", + "integrity": "sha512-cvbTwETRfsFh4nHsL1eGWapU1XFi5Ot9E85sWAwia7Y7EgB7vfqcZhTKZ+l7hCGxSPoushMv5GKhT5PdLv03WA==", + "dependencies": { + "signal-exit": "^3.0.2" + } + }, + "node_modules/lodash": { + "version": "4.17.21", + "resolved": "https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz", + "integrity": "sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==" + }, + "node_modules/lodash.assignin": { + "version": "4.2.0", + "resolved": "https://registry.npmjs.org/lodash.assignin/-/lodash.assignin-4.2.0.tgz", + "integrity": "sha512-yX/rx6d/UTVh7sSVWVSIMjfnz95evAgDFdb1ZozC35I9mSFCkmzptOzevxjgbQUsc78NR44LVHWjsoMQXy9FDg==" + }, + "node_modules/lodash.bind": { + "version": "4.2.1", + "resolved": "https://registry.npmjs.org/lodash.bind/-/lodash.bind-4.2.1.tgz", + "integrity": "sha512-lxdsn7xxlCymgLYo1gGvVrfHmkjDiyqVv62FAeF2i5ta72BipE1SLxw8hPEPLhD4/247Ijw07UQH7Hq/chT5LA==" + }, + "node_modules/lodash.chunk": { + "version": "4.2.0", + "resolved": "https://registry.npmjs.org/lodash.chunk/-/lodash.chunk-4.2.0.tgz", + "integrity": "sha512-ZzydJKfUHJwHa+hF5X66zLFCBrWn5GeF28OHEr4WVWtNDXlQ/IjWKPBiikqKo2ne0+v6JgCgJ0GzJp8k8bHC7w==" + }, + "node_modules/lodash.clonedeep": { + "version": "4.5.0", + "resolved": "https://registry.npmjs.org/lodash.clonedeep/-/lodash.clonedeep-4.5.0.tgz", + "integrity": "sha512-H5ZhCF25riFd9uB5UCkVKo61m3S/xZk1x4wA6yp/L3RFP6Z/eHH1ymQcGLo7J3GMPfm0V/7m1tryHuGVxpqEBQ==" + }, + "node_modules/lodash.debounce": { "version": "4.0.8", "resolved": "https://registry.npmjs.org/lodash.debounce/-/lodash.debounce-4.0.8.tgz", "integrity": "sha512-FT1yDzDYEoYWhnSGnpE/4Kj1fLZkDFyqRb7fNt6FdYOSxlUWAtp42Eh6Wb0rGIv/m9Bgo7x4GhQbm5Ys4SG5ow==" @@ -13805,6 +14203,184 @@ "resolved": "https://registry.npmjs.org/lodash.uniq/-/lodash.uniq-4.5.0.tgz", "integrity": "sha512-xfBaXQd9ryd9dlSDvnvI0lvxfLJlYAZzXomUYzLKtUeOQvOP5piqAWuGtrhWeqaXK9hhoM/iyJc5AV+XfsX3HQ==" }, + "node_modules/log-update": { + "version": "5.0.1", + "resolved": "https://registry.npmjs.org/log-update/-/log-update-5.0.1.tgz", + "integrity": "sha512-5UtUDQ/6edw4ofyljDNcOVJQ4c7OjDro4h3y8e1GQL5iYElYclVHJ3zeWchylvMaKnDbDilC8irOVyexnA/Slw==", + "dev": true, + "dependencies": { + "ansi-escapes": "^5.0.0", + "cli-cursor": "^4.0.0", + "slice-ansi": "^5.0.0", + "strip-ansi": "^7.0.1", + "wrap-ansi": "^8.0.1" + }, + "engines": { + "node": "^12.20.0 || ^14.13.1 || >=16.0.0" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/log-update/node_modules/ansi-escapes": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/ansi-escapes/-/ansi-escapes-5.0.0.tgz", + "integrity": "sha512-5GFMVX8HqE/TB+FuBJGuO5XG0WrsA6ptUqoODaT/n9mmUaZFkqnBueB4leqGBCmrUHnCnC4PCZTCd0E7QQ83bA==", + "dev": true, + "dependencies": { + "type-fest": "^1.0.2" + }, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/log-update/node_modules/ansi-regex": { + "version": "6.0.1", + "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-6.0.1.tgz", + "integrity": "sha512-n5M855fKb2SsfMIiFFoVrABHJC8QtHwVx+mHWP3QcEqBHYienj5dHSgjbxtC0WEZXYt4wcD6zrQElDPhFuZgfA==", + "dev": true, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/chalk/ansi-regex?sponsor=1" + } + }, + "node_modules/log-update/node_modules/ansi-styles": { + "version": "6.2.1", + "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-6.2.1.tgz", + "integrity": "sha512-bN798gFfQX+viw3R7yrGWRqnrN2oRkEkUjjl4JNn4E8GxxbjtG3FbrEIIY3l8/hrwUwIeCZvi4QuOTP4MErVug==", + "dev": true, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/chalk/ansi-styles?sponsor=1" + } + }, + "node_modules/log-update/node_modules/cli-cursor": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/cli-cursor/-/cli-cursor-4.0.0.tgz", + "integrity": "sha512-VGtlMu3x/4DOtIUwEkRezxUZ2lBacNJCHash0N0WeZDBS+7Ux1dm3XWAgWYxLJFMMdOeXMHXorshEFhbMSGelg==", + "dev": true, + "dependencies": { + "restore-cursor": "^4.0.0" + }, + "engines": { + "node": "^12.20.0 || ^14.13.1 || >=16.0.0" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/log-update/node_modules/is-fullwidth-code-point": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-4.0.0.tgz", + "integrity": "sha512-O4L094N2/dZ7xqVdrXhh9r1KODPJpFms8B5sGdJLPy664AgvXsreZUyCQQNItZRDlYug4xStLjNp/sz3HvBowQ==", + "dev": true, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/log-update/node_modules/restore-cursor": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/restore-cursor/-/restore-cursor-4.0.0.tgz", + "integrity": "sha512-I9fPXU9geO9bHOt9pHHOhOkYerIMsmVaWB0rA2AI9ERh/+x/i7MV5HKBNrg+ljO5eoPVgCcnFuRjJ9uH6I/3eg==", + "dev": true, + "dependencies": { + "onetime": "^5.1.0", + "signal-exit": "^3.0.2" + }, + "engines": { + "node": "^12.20.0 || ^14.13.1 || >=16.0.0" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/log-update/node_modules/slice-ansi": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/slice-ansi/-/slice-ansi-5.0.0.tgz", + "integrity": "sha512-FC+lgizVPfie0kkhqUScwRu1O/lF6NOgJmlCgK+/LYxDCTk8sGelYaHDhFcDN+Sn3Cv+3VSa4Byeo+IMCzpMgQ==", + "dev": true, + "dependencies": { + "ansi-styles": "^6.0.0", + "is-fullwidth-code-point": "^4.0.0" + }, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/chalk/slice-ansi?sponsor=1" + } + }, + "node_modules/log-update/node_modules/string-width": { + "version": "5.1.2", + "resolved": "https://registry.npmjs.org/string-width/-/string-width-5.1.2.tgz", + "integrity": "sha512-HnLOCR3vjcY8beoNLtcjZ5/nxn2afmME6lhrDrebokqMap+XbeW8n9TXpPDOqdGK5qcI3oT0GKTW6wC7EMiVqA==", + "dev": true, + "dependencies": { + "eastasianwidth": "^0.2.0", + "emoji-regex": "^9.2.2", + "strip-ansi": "^7.0.1" + }, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/log-update/node_modules/strip-ansi": { + "version": "7.1.0", + "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-7.1.0.tgz", + "integrity": "sha512-iq6eVVI64nQQTRYq2KtEg2d2uU7LElhTJwsH4YzIHZshxlgZms/wIc4VoDQTlG/IvVIrBKG06CrZnp0qv7hkcQ==", + "dev": true, + "dependencies": { + "ansi-regex": "^6.0.1" + }, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/chalk/strip-ansi?sponsor=1" + } + }, + "node_modules/log-update/node_modules/type-fest": { + "version": "1.4.0", + "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-1.4.0.tgz", + "integrity": "sha512-yGSza74xk0UG8k+pLh5oeoYirvIiWo5t0/o3zHHAO2tRDiZcxWP7fywNlXhqb6/r6sWvwi+RsyQMWhVLe4BVuA==", + "dev": true, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/log-update/node_modules/wrap-ansi": { + "version": "8.1.0", + "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-8.1.0.tgz", + "integrity": "sha512-si7QWI6zUMq56bESFvagtmzMdGOtoxfR+Sez11Mobfc7tm+VkUckk9bW2UeffTGVUbOksxmSw0AA2gs8g71NCQ==", + "dev": true, + "dependencies": { + "ansi-styles": "^6.1.0", + "string-width": "^5.0.1", + "strip-ansi": "^7.0.1" + }, + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://github.com/chalk/wrap-ansi?sponsor=1" + } + }, "node_modules/longest-streak": { "version": "2.0.4", "resolved": "https://registry.npmjs.org/longest-streak/-/longest-streak-2.0.4.tgz", @@ -13946,6 +14522,15 @@ "react": ">= 0.14.0" } }, + "node_modules/masonry-layout": { + "version": "4.2.2", + "resolved": "https://registry.npmjs.org/masonry-layout/-/masonry-layout-4.2.2.tgz", + "integrity": "sha512-iGtAlrpHNyxaR19CvKC3npnEcAwszXoyJiI8ARV2ePi7fmYhIud25MHK8Zx4P0LCC4d3TNO9+rFa1KoK1OEOaA==", + "dependencies": { + "get-size": "^2.0.2", + "outlayer": "^2.1.0" + } + }, "node_modules/md5-file": { "version": "5.0.0", "resolved": "https://registry.npmjs.org/md5-file/-/md5-file-5.0.0.tgz", @@ -14580,15 +15165,6 @@ "node": "*" } }, - "node_modules/mri": { - "version": "1.2.0", - "resolved": "https://registry.npmjs.org/mri/-/mri-1.2.0.tgz", - "integrity": "sha512-tzzskb3bG8LvYGFF/mDTpq3jpI6Q9wc3LEmBaghu+DdCssd1FakN7Bc0hVNmEyGq1bq3RgfkCb3cmQLpNPOroA==", - "dev": true, - "engines": { - "node": ">=4" - } - }, "node_modules/ms": { "version": "2.1.2", "resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz", @@ -14651,28 +15227,6 @@ "node": ">= 6.0.0" } }, - "node_modules/multimatch": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/multimatch/-/multimatch-4.0.0.tgz", - "integrity": "sha512-lDmx79y1z6i7RNx0ZGCPq1bzJ6ZoDDKbvh7jxr9SJcWLkShMzXrHbYVpTdnhNM5MXpDUxCQ4DgqVttVXlBgiBQ==", - "dev": true, - "dependencies": { - "@types/minimatch": "^3.0.3", - "array-differ": "^3.0.0", - "array-union": "^2.1.0", - "arrify": "^2.0.1", - "minimatch": "^3.0.4" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/multimatch/node_modules/@types/minimatch": { - "version": "3.0.5", - "resolved": "https://registry.npmjs.org/@types/minimatch/-/minimatch-3.0.5.tgz", - "integrity": "sha512-Klz949h02Gz2uZCMGwDUSDS1YBlTdDDgbWHi+81l29tQALUtvz4rAYi5uoVhE5Lagoq6DeqAUlbrHvW/mXDgdQ==", - "dev": true - }, "node_modules/mute-stream": { "version": "0.0.8", "resolved": "https://registry.npmjs.org/mute-stream/-/mute-stream-0.0.8.tgz", @@ -15243,6 +15797,16 @@ "node": ">=0.10.0" } }, + "node_modules/outlayer": { + "version": "2.1.1", + "resolved": "https://registry.npmjs.org/outlayer/-/outlayer-2.1.1.tgz", + "integrity": "sha512-+GplXsCQ3VrbGujAeHEzP9SXsBmJxzn/YdDSQZL0xqBmAWBmortu2Y9Gwdp9J0bgDQ8/YNIPMoBM13nTwZfAhw==", + "dependencies": { + "ev-emitter": "^1.0.0", + "fizzy-ui-utils": "^2.0.0", + "get-size": "^2.0.2" + } + }, "node_modules/p-cancelable": { "version": "2.1.1", "resolved": "https://registry.npmjs.org/p-cancelable/-/p-cancelable-2.1.1.tgz", @@ -15829,6 +16393,18 @@ "url": "https://github.com/sponsors/jonschlinkert" } }, + "node_modules/pidtree": { + "version": "0.6.0", + "resolved": "https://registry.npmjs.org/pidtree/-/pidtree-0.6.0.tgz", + "integrity": "sha512-eG2dWTVw5bzqGRztnHExczNxt5VGsE6OwTeCG3fdUf9KBsZzO3R5OIIIzWR+iZA0NtZ+RDVdaoE2dK1cn6jH4g==", + "dev": true, + "bin": { + "pidtree": "bin/pidtree.js" + }, + "engines": { + "node": ">=0.10" + } + }, "node_modules/pkg-dir": { "version": "4.2.0", "resolved": "https://registry.npmjs.org/pkg-dir/-/pkg-dir-4.2.0.tgz", @@ -16585,195 +17161,6 @@ "renderkid": "^2.0.4" } }, - "node_modules/pretty-quick": { - "version": "3.1.3", - "resolved": "https://registry.npmjs.org/pretty-quick/-/pretty-quick-3.1.3.tgz", - "integrity": "sha512-kOCi2FJabvuh1as9enxYmrnBC6tVMoVOenMaBqRfsvBHB0cbpYHjdQEpSglpASDFEXVwplpcGR4CLEaisYAFcA==", - "dev": true, - "dependencies": { - "chalk": "^3.0.0", - "execa": "^4.0.0", - "find-up": "^4.1.0", - "ignore": "^5.1.4", - "mri": "^1.1.5", - "multimatch": "^4.0.0" - }, - "bin": { - "pretty-quick": "bin/pretty-quick.js" - }, - "engines": { - "node": ">=10.13" - }, - "peerDependencies": { - "prettier": ">=2.0.0" - } - }, - "node_modules/pretty-quick/node_modules/ansi-styles": { - "version": "4.3.0", - "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz", - "integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==", - "dev": true, - "dependencies": { - "color-convert": "^2.0.1" - }, - "engines": { - "node": ">=8" - }, - "funding": { - "url": "https://github.com/chalk/ansi-styles?sponsor=1" - } - }, - "node_modules/pretty-quick/node_modules/chalk": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/chalk/-/chalk-3.0.0.tgz", - "integrity": "sha512-4D3B6Wf41KOYRFdszmDqMCGq5VV/uMAB273JILmO+3jAlh8X4qDtdtgCR3fxtbLEMzSx22QdhnDcJvu2u1fVwg==", - "dev": true, - "dependencies": { - "ansi-styles": "^4.1.0", - "supports-color": "^7.1.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/pretty-quick/node_modules/color-convert": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz", - "integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==", - "dev": true, - "dependencies": { - "color-name": "~1.1.4" - }, - "engines": { - "node": ">=7.0.0" - } - }, - "node_modules/pretty-quick/node_modules/color-name": { - "version": "1.1.4", - "resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz", - "integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==", - "dev": true - }, - "node_modules/pretty-quick/node_modules/execa": { - "version": "4.1.0", - "resolved": "https://registry.npmjs.org/execa/-/execa-4.1.0.tgz", - "integrity": "sha512-j5W0//W7f8UxAn8hXVnwG8tLwdiUy4FJLcSupCg6maBYZDpyBvTApK7KyuI4bKj8KOh1r2YH+6ucuYtJv1bTZA==", - "dev": true, - "dependencies": { - "cross-spawn": "^7.0.0", - "get-stream": "^5.0.0", - "human-signals": "^1.1.1", - "is-stream": "^2.0.0", - "merge-stream": "^2.0.0", - "npm-run-path": "^4.0.0", - "onetime": "^5.1.0", - "signal-exit": "^3.0.2", - "strip-final-newline": "^2.0.0" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sindresorhus/execa?sponsor=1" - } - }, - "node_modules/pretty-quick/node_modules/find-up": { - "version": "4.1.0", - "resolved": "https://registry.npmjs.org/find-up/-/find-up-4.1.0.tgz", - "integrity": "sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==", - "dev": true, - "dependencies": { - "locate-path": "^5.0.0", - "path-exists": "^4.0.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/pretty-quick/node_modules/get-stream": { - "version": "5.2.0", - "resolved": "https://registry.npmjs.org/get-stream/-/get-stream-5.2.0.tgz", - "integrity": "sha512-nBF+F1rAZVCu/p7rjzgA+Yb4lfYXrpl7a6VmJrU8wF9I1CKvP/QwPNZHnOlwbTkY6dvtFIzFMSyQXbLoTQPRpA==", - "dev": true, - "dependencies": { - "pump": "^3.0.0" - }, - "engines": { - "node": ">=8" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/pretty-quick/node_modules/has-flag": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz", - "integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==", - "dev": true, - "engines": { - "node": ">=8" - } - }, - "node_modules/pretty-quick/node_modules/human-signals": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/human-signals/-/human-signals-1.1.1.tgz", - "integrity": "sha512-SEQu7vl8KjNL2eoGBLF3+wAjpsNfA9XMlXAYj/3EdaNfAlxKthD1xjEQfGOUhllCGGJVNY34bRr6lPINhNjyZw==", - "dev": true, - "engines": { - "node": ">=8.12.0" - } - }, - "node_modules/pretty-quick/node_modules/locate-path": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-5.0.0.tgz", - "integrity": "sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==", - "dev": true, - "dependencies": { - "p-locate": "^4.1.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/pretty-quick/node_modules/p-limit": { - "version": "2.3.0", - "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-2.3.0.tgz", - "integrity": "sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==", - "dev": true, - "dependencies": { - "p-try": "^2.0.0" - }, - "engines": { - "node": ">=6" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/pretty-quick/node_modules/p-locate": { - "version": "4.1.0", - "resolved": "https://registry.npmjs.org/p-locate/-/p-locate-4.1.0.tgz", - "integrity": "sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==", - "dev": true, - "dependencies": { - "p-limit": "^2.2.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/pretty-quick/node_modules/supports-color": { - "version": "7.2.0", - "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-7.2.0.tgz", - "integrity": "sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==", - "dev": true, - "dependencies": { - "has-flag": "^4.0.0" - }, - "engines": { - "node": ">=8" - } - }, "node_modules/prismjs": { "version": "1.29.0", "resolved": "https://registry.npmjs.org/prismjs/-/prismjs-1.29.0.tgz", @@ -18469,6 +18856,12 @@ "resolved": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-0.3.5.tgz", "integrity": "sha512-+4nRk0k3oEpwUB7/CalD7xE2z4VmtEnnq0GO2IPTkrooTrAhEsWvuLF5iWP1dXrwluki/azwXV1ve7gtYuPldg==" }, + "node_modules/rfdc": { + "version": "1.3.0", + "resolved": "https://registry.npmjs.org/rfdc/-/rfdc-1.3.0.tgz", + "integrity": "sha512-V2hovdzFbOi77/WajaSMXk2OLm+xNIeQdMMuB7icj7bk6zi2F8GGAxigcnDFpJHbNyNcgyJDiP+8nOrY5cZGrA==", + "dev": true + }, "node_modules/rimraf": { "version": "2.7.1", "resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.7.1.tgz", @@ -19639,6 +20032,15 @@ "safe-buffer": "~5.2.0" } }, + "node_modules/string-argv": { + "version": "0.3.2", + "resolved": "https://registry.npmjs.org/string-argv/-/string-argv-0.3.2.tgz", + "integrity": "sha512-aqD2Q0144Z+/RqG52NeHEkZauTAUWJO8c6yTftGJKO3Tja5tUgIfmIl6kExvhtxSDP7fXB6DvzkfMpCd/F3G+Q==", + "dev": true, + "engines": { + "node": ">=0.6.19" + } + }, "node_modules/string-natural-compare": { "version": "3.0.1", "resolved": "https://registry.npmjs.org/string-natural-compare/-/string-natural-compare-3.0.1.tgz", diff --git a/package.json b/package.json index e4bd45221f6..7e83f88a581 100644 --- a/package.json +++ b/package.json @@ -70,6 +70,7 @@ "hast-util-to-string": "^1.0.4", "is-absolute-url": "^4.0.1", "markdown-to-jsx": "^7.3.2", + "masonry-layout": "^4.2.2", "mdast-util-to-string": "^2.0.0", "prismjs": "^1.29.0", "react": "^18.2.0", @@ -88,8 +89,8 @@ "hast-util-is-element": "^2.1.3", "hast-util-to-text": "^3.1.2", "husky": "^8.0.3", + "lint-staged": "^14.0.1", "prettier": "^3.0.3", - "pretty-quick": "^3.1.3", "react-refresh": "^0.14.0", "rehype-format": "^3.1.0", "rehype-remark": "^8.1.1", @@ -108,6 +109,9 @@ "loader-utils": ">=1.4.1", "nth-check": ">=2.0.1" }, + "lint-staged": { + "*.js": "prettier --write" + }, "repository": { "type": "git", "url": "https://github.com/EnterpriseDB/docs" diff --git a/src/components/advanced-search/filtering.js b/src/components/advanced-search/filtering.js index 1404b8ce579..04d1047ff22 100644 --- a/src/components/advanced-search/filtering.js +++ b/src/components/advanced-search/filtering.js @@ -1,17 +1,14 @@ -import React, { useEffect } from "react"; +import React from "react"; import { Badge } from "react-bootstrap"; import { - connectMenu, - connectCurrentRefinements, - connectRefinementList, -} from "react-instantsearch-dom"; + useClearRefinements, + useCurrentRefinements, + useRefinementList, + useInstantSearch, +} from "react-instantsearch"; import { products } from "../../constants/products"; import { capitalize } from "../../constants/utils"; - -const typeToContentType = { - doc: { name: "Documentation" }, - guide: { name: "Guides" }, -}; +import useSiteMetadata from "../../hooks/use-sitemetadata"; const labelForItem = (item, translation) => { return translation[item.label] @@ -20,7 +17,7 @@ const labelForItem = (item, translation) => { }; const versionSort = (a, b) => { - return b.label.localeCompare(a.label, undefined, { numeric: true }); + return b.name.localeCompare(a.name, undefined, { numeric: true }); }; const RadioInput = ({ @@ -46,7 +43,7 @@ const RadioInput = ({ {labelText} {showBadge && badgeNumber} @@ -58,8 +55,8 @@ const RadioRefinement = ({ attribute, heading, items, - queryActive, refine, + showBadge, show, sortFunction, translation = {}, @@ -79,9 +76,17 @@ const RadioRefinement = ({ }), ); + const radioRefine = (refinement) => { + // toggle all current refinements, add new one + for (let item of items) { + if (item !== refinement && item.isRefined) refine(item.label); + } + if (refinement) refine(refinement.label); + }; + return ( -
-
+
+
{heading || capitalize(attribute)}
total + item.count, 0)} - showBadge={queryActive} - onChange={() => refine("")} + showBadge={showBadge} + onChange={() => radioRefine()} checked={!refinedItem} /> {sortedItems.map((item) => ( @@ -100,8 +105,8 @@ const RadioRefinement = ({ name={radioName} labelText={labelForItem(item, translation)} badgeNumber={item.count} - showBadge={queryActive} - onChange={() => refine(item.label)} + showBadge={showBadge} + onChange={() => radioRefine(item)} checked={refinedItem === item} /> ))} @@ -109,54 +114,41 @@ const RadioRefinement = ({ ); }; -/* eslint-disable no-unused-vars */ -const ContentTypeRefinement = connectMenu( - /* eslint-enable */ - ({ items, currentRefinement, refine, queryActive }) => ( +const SingleFacetRefinement = ({ + attribute, + limit, + show, + hideIfEmpty = false, + sortBy, +}) => { + const { items, refine } = useRefinementList({ attribute, limit, sortBy }); + const empty = !items || items.length === 0; + const { algoliaIndex } = useSiteMetadata(); + + const { uiState } = useInstantSearch(); + const query = uiState[algoliaIndex].query; + + return ( - ), -); - -const SingleFacetRefinement = connectRefinementList( - ({ - items, - refine, - queryActive, - show, - attribute, - sortFunction, - hideIfEmpty = false, - }) => { - const empty = !items || items.length === 0; - - return ( - - ); - }, -); + ); +}; -const ClearRefinements = connectCurrentRefinements(({ items, refine }) => { +const ClearRefinements = () => { + const { canRefine, refine } = useClearRefinements(); const clear = (e) => { - refine(items); + refine(); e.preventDefault(); }; - if (items.length > 0) { + if (canRefine) { return ( Clear Filters @@ -164,51 +156,37 @@ const ClearRefinements = connectCurrentRefinements(({ items, refine }) => { ); } return null; -}); +}; -export const AdvancedSearchFiltering = connectCurrentRefinements( - ({ items, queryActive, refine }) => { - const showProductVersionFilters = !items.find((item) => { - return item.attribute === "type" && item.currentRefinement === "guide"; - }); +export const AdvancedSearchFiltering = () => { + const { items } = useCurrentRefinements(); - const productFilterApplied = items.some( - (item) => item.attribute === "product", - ); - const versionFilterApplied = items.some( - (item) => item.attribute === "version", - ); + const productFilterApplied = items.some( + (item) => item.attribute === "product", + ); + const versionFilterApplied = items.some( + (item) => item.attribute === "version", + ); - // if we don't have a product filter applied, wipe any version filters - useEffect(() => { - if (versionFilterApplied && !productFilterApplied) { - const versionFilter = items.find( - (item) => item.attribute === "version", - ); - if (versionFilter.items[0]) { - refine(versionFilter.items[0].value); - } - } - }); + // if we don't have a product filter applied, wipe any version filters + if (versionFilterApplied && !productFilterApplied) { + const versionFilter = items.find((item) => item.attribute === "version"); + for (let refinement of versionFilter.refinements) { + versionFilter.refine(refinement); + } + } - return ( - <> - - - - - ); - }, -); + return ( + <> + + + + + ); +}; diff --git a/src/components/advanced-search/form.js b/src/components/advanced-search/form.js index 21bf8e98b9e..6f2da399341 100644 --- a/src/components/advanced-search/form.js +++ b/src/components/advanced-search/form.js @@ -1,73 +1,84 @@ -import React, { useEffect, useCallback, createRef } from "react"; -import { connectSearchBox } from "react-instantsearch-dom"; +import React, { useLayoutEffect, useCallback, useRef, useState } from "react"; +import { useSearchBox } from "react-instantsearch"; import Icon, { iconNames } from "../icon"; import { SlashIndicator, ClearButton } from "../search/formComps"; -export const AdvancedSearchForm = connectSearchBox( - ({ currentRefinement, refine, query }) => { - const queryLength = (query || "").length; +export const AdvancedSearchForm = () => { + const { clear, refine, query } = useSearchBox(); + const inputRef = useRef(null); + const [inputValue, setInputValue] = useState(query); + const queryLength = (inputValue || "").length; - const inputRef = createRef(); - const searchKeyboardShortcuts = useCallback( - (e) => { - const inputFocused = inputRef.current.id === document.activeElement.id; + const onInputChange = useCallback( + (e) => { + let newValue = e.currentTarget.value; + setInputValue(newValue); + refine(newValue); + }, + [refine], + ); - if (e.key === "/" && !inputFocused) { - inputRef.current.focus(); - e.preventDefault(); - } - if (e.key === "Escape" && inputFocused) { - inputRef.current.blur(); - e.preventDefault(); - } - }, - [inputRef], - ); + const onClearSearch = useCallback( + (e) => { + clear(); + }, + [clear], + ); - useEffect(() => { - document.addEventListener("keydown", searchKeyboardShortcuts); - return () => { - document.removeEventListener("keydown", searchKeyboardShortcuts); - }; - }, [searchKeyboardShortcuts]); + const searchKeyboardShortcuts = useCallback((e) => { + const inputFocused = inputRef.current.id === document.activeElement?.id; - useEffect(() => { + if (e.key === "/" && !inputFocused) { inputRef.current.focus(); - }, []); // eslint-disable-line react-hooks/exhaustive-deps + e.preventDefault(); + } + if (e.key === "Escape" && inputFocused) { + inputRef.current.blur(); + e.preventDefault(); + } + }, []); - return ( -
e.preventDefault()} - > - - refine(e.currentTarget.value)} - ref={inputRef} - /> - { - refine(""); - }} - className={`${queryLength === 0 && "d-none"}`} - /> - - - ); - }, -); + useLayoutEffect(() => { + document.addEventListener("keydown", searchKeyboardShortcuts); + return () => { + document.removeEventListener("keydown", searchKeyboardShortcuts); + }; + }, [searchKeyboardShortcuts]); + + useLayoutEffect(() => { + inputRef.current.focus(); + }, []); // eslint-disable-line react-hooks/exhaustive-deps + + return ( +
e.preventDefault()} + > + + + + + + ); +}; diff --git a/src/components/advanced-search/hitComps.js b/src/components/advanced-search/hitComps.js index 0a152ed078c..bb94d5e12f7 100644 --- a/src/components/advanced-search/hitComps.js +++ b/src/components/advanced-search/hitComps.js @@ -1,16 +1,16 @@ import React from "react"; -import { Highlight, Snippet } from "react-instantsearch-dom"; +import { Highlight, Snippet } from "react-instantsearch"; import { Link } from "../"; export const AdvancedPageHit = ({ hit }) => ( <> - +
{hit.path}
diff --git a/src/components/advanced-search/queryParams.js b/src/components/advanced-search/queryParams.js index adc7d5ebf22..08d42ffbe9a 100644 --- a/src/components/advanced-search/queryParams.js +++ b/src/components/advanced-search/queryParams.js @@ -8,13 +8,13 @@ export const queryParamsToState = (query) => { if (params.get("product")) { searchState.refinementList = { ...searchState.refinementList, - product: params.get("product"), + product: [params.get("product")], }; } if (params.get("version")) { searchState.refinementList = { ...searchState.refinementList, - version: params.get("version"), + version: [params.get("version")], }; } if (params.get("page")) { diff --git a/src/components/advanced-search/results.js b/src/components/advanced-search/results.js index 318122f0df2..d9bd860c2cf 100644 --- a/src/components/advanced-search/results.js +++ b/src/components/advanced-search/results.js @@ -1,123 +1,122 @@ import React from "react"; import { Hits, - connectStateResults, - connectPagination, - connectCurrentRefinements, -} from "react-instantsearch-dom"; + usePagination, + useCurrentRefinements, + useInstantSearch, +} from "react-instantsearch"; import { AdvancedPageHit } from "./index"; import { products } from "../../constants/products"; import { capitalize } from "../../constants/utils"; +import useSiteMetadata from "../../hooks/use-sitemetadata"; const prettyProductName = (product) => { return products[product] ? products[product].name : capitalize(product); }; -const ResultsSummary = connectCurrentRefinements( - connectStateResults(({ searchResults: res, items }) => { - const resultCount = res && res.nbHits; - const query = res && res.query; +const ResultsSummary = () => { + const { results: res } = useInstantSearch(); + const { items } = useCurrentRefinements(); - const productRefinement = items.find( - (item) => item.attribute === "product", - ); - const versionRefinement = items.find( - (item) => item.attribute === "version", - ); + const resultCount = res && res.nbHits; + const query = res && res.query; - const productName = productRefinement - ? prettyProductName(productRefinement.currentRefinement[0]) - : null; - const version = versionRefinement - ? versionRefinement.currentRefinement[0] - : null; + const productRefinement = items.find((item) => item.attribute === "product"); + const versionRefinement = items.find((item) => item.attribute === "version"); - return ( -

- {resultCount} result{resultCount !== 1 && "s"} for "{query}" - {productName && " in "} - {productName && {productName}} - {version && " and "} - {version && Version {version}} -

- ); - }), -); + const productName = productRefinement + ? prettyProductName(productRefinement.refinements[0].value) + : null; + const version = versionRefinement + ? versionRefinement.refinements[0].value + : null; + + return ( +

+ {resultCount} result{resultCount !== 1 && "s"} for "{query}" + {productName && " in "} + {productName && {productName}} + {version && " and "} + {version && Version {version}} +

+ ); +}; -const Pagination = connectPagination( - ({ currentRefinement, nbPages, refine }) => { - const previousEnabled = currentRefinement > 1; - const nextEnabled = currentRefinement < nbPages; - const goPrevious = (e) => { - refine(currentRefinement - 1); - e.preventDefault(); - }; - const goNext = (e) => { - refine(currentRefinement + 1); - e.preventDefault(); - }; +const Pagination = () => { + const { currentRefinement, nbPages, refine } = usePagination(); + const previousEnabled = currentRefinement > 0; + const nextEnabled = currentRefinement < nbPages - 1; + const goPrevious = (e) => { + refine(currentRefinement - 1); + e.preventDefault(); + }; + const goNext = (e) => { + refine(currentRefinement + 1); + e.preventDefault(); + }; - if (previousEnabled || nextEnabled) { - return ( -
-
-
- -
- {currentRefinement} / {nbPages} -
- + if (previousEnabled || nextEnabled) { + return ( +
+
+
+ +
+ {currentRefinement + 1} / {nbPages} +
+
- ); - } - return null; - }, -); +
+ ); + } + return null; +}; const ResultsContent = ({ children }) => (
{children}
); -export const AdvancedSearchResults = connectStateResults( - ({ searchResults, query }) => { - const queryLength = (query || "").length; - const showPagination = searchResults && searchResults.nbPages > 1; +export const AdvancedSearchResults = () => { + const { algoliaIndex } = useSiteMetadata(); - if (queryLength === 0) { - return ( -

Enter a search query to begin.

- ); - } + const { results: searchResults, uiState } = useInstantSearch(); + const query = uiState[algoliaIndex].query; + const queryLength = (query || "").length; + const showPagination = searchResults && searchResults.nbPages > 1; + if (queryLength === 0) { return ( - - - - {showPagination && } - +

Enter a search query to begin.

); - }, -); + } + + return ( + + + + {showPagination && } + + ); +}; diff --git a/src/components/back-button.js b/src/components/back-button.js index f7c6b806905..c0d6ffddfef 100644 --- a/src/components/back-button.js +++ b/src/components/back-button.js @@ -3,11 +3,11 @@ import { Link } from "./"; import Icon, { iconNames } from "./icon/"; const BackButton = () => ( -
  • +
  • diff --git a/src/components/card-decks.js b/src/components/card-decks.js index cc1870480a4..6aa048f39d7 100644 --- a/src/components/card-decks.js +++ b/src/components/card-decks.js @@ -14,13 +14,13 @@ const FullCard = ({ card }) => { const iconName = card.frontmatter.iconName || iconNames.DOTTED_BOX; return ( -
    +
    @@ -34,23 +34,25 @@ const FullCard = ({ card }) => {

    {card.frontmatter.description}

    - {card.children.map((child) => ( - - {child.frontmatter.navTitle || child.frontmatter.title} - {showInteractiveBadge(child.frontmatter) && } - - ))} +
    + {card.children.map((child) => ( + + {child.frontmatter.navTitle || child.frontmatter.title} + {showInteractiveBadge(child.frontmatter) && } + + ))} +
    ); }; const SimpleCard = ({ card }) => ( -
    +

    @@ -68,7 +70,7 @@ const CardDecks = ({ cards, cardType = "simple", deckTitle = "" }) => { return ( <> {deckTitle &&

    {deckTitle}

    } -
    +
    {cards.map((card) => { return ( { const OutputPre = ({ content }) => (
    -
    Output
    +
    Output
    {content}
    ); diff --git a/src/components/dark-mode-toggle.js b/src/components/dark-mode-toggle.js index 710bdec9157..4b8a1fba7c9 100644 --- a/src/components/dark-mode-toggle.js +++ b/src/components/dark-mode-toggle.js @@ -10,7 +10,7 @@ const DarkModeToggle = ({ className = "" }) => ( className={`dark-mode-toggle d-flex ${className}`} title="Toggle Color Theme" > -