Merge pull request #1473 from EnterpriseDB/release/2021-06-15

Release: 2021-06-15 Former-commit-id: d5d5e03
EnterpriseDB · Jun 15, 2021 · 436c2b7 · 436c2b7
2 parents 31f3a88 + b5d31f6
commit 436c2b7
Show file tree

Hide file tree

Showing 31 changed files with 85 additions and 62 deletions.
diff --git a/build-sources.json b/build-sources.json
@@ -1,6 +1,7 @@
 {
   "ark": false,
   "bdr": true,
+  "harp": true,
   "bart": true,
   "efm": true,
   "epas": true,

diff --git a/gatsby-config.js b/gatsby-config.js
@@ -19,6 +19,7 @@ const sourceToPluginConfig = {
   ark: { name: 'ark', path: 'product_docs/docs/ark' },
   bart: { name: 'bart', path: 'product_docs/docs/bart' },
   bdr: { name: 'bdr', path: 'product_docs/docs/bdr' },
+  harp: { name: 'harp', path: 'product_docs/docs/harp' },
   efm: { name: 'efm', path: 'product_docs/docs/efm' },
   epas: { name: 'epas', path: 'product_docs/docs/epas' },
   eprs: { name: 'eprs', path: 'product_docs/docs/eprs' },

diff --git a/product_docs/docs/efm/4.0/efm_user/05_using_efm.mdx b/product_docs/docs/efm/4.0/efm_user/05_using_efm.mdx
@@ -98,7 +98,7 @@ For example, if the properties file on node `10.0.1.10` includes a setting of `p
 efm set-priority acctg 10.0.1.10 1
 ```
 
-In the event of a failover, Failover Manager will first retrieve information from Postgres streaming replication to confirm which Standby node has the most recent data, and promote the node with the least chance of data loss. If two Standby nodes contain equally up-to-date data, the node with a higher user-specified priority value will be promoted to Primary unless [use.replay.tiebreaker](04_configuring_efm/01_cluster_properties/#use_replay_tiebreaker) is set to `false` . To check the priority value of your Standby nodes, use the command:
+In the event of a failover, Failover Manager will first retrieve information from Postgres streaming replication to confirm which Standby node has the most recent data, and promote the node with the least chance of data loss. If two Standby nodes contain equally up-to-date data, the node with a higher user-specified priority value will be promoted to Primary unless [use.replay.tiebreaker](04_configuring_efm/01_cluster_properties/#use_replay_tiebreaker) is set to `true` . To check the priority value of your Standby nodes, use the command:
 
 ```text
 efm cluster-status <cluster_name>

diff --git a/product_docs/docs/efm/4.1/efm_user/05_using_efm.mdx b/product_docs/docs/efm/4.1/efm_user/05_using_efm.mdx
@@ -98,7 +98,7 @@ For example, if the properties file on node `10.0.1.10` includes a setting of `p
 efm set-priority acctg 10.0.1.10 1
 ```
 
-In the event of a failover, Failover Manager will first retrieve information from Postgres streaming replication to confirm which Standby node has the most recent data, and promote the node with the least chance of data loss. If two Standby nodes contain equally up-to-date data, the node with a higher user-specified priority value will be promoted to Primary unless [use.replay.tiebreaker](04_configuring_efm/01_cluster_properties/#use_replay_tiebreaker) is set to `false` . To check the priority value of your Standby nodes, use the command:
+In the event of a failover, Failover Manager will first retrieve information from Postgres streaming replication to confirm which Standby node has the most recent data, and promote the node with the least chance of data loss. If two Standby nodes contain equally up-to-date data, the node with a higher user-specified priority value will be promoted to Primary unless [use.replay.tiebreaker](04_configuring_efm/01_cluster_properties/#use_replay_tiebreaker) is set to `true` . To check the priority value of your Standby nodes, use the command:
 
 ```text
 efm cluster-status <cluster_name>

diff --git a/product_docs/docs/efm/4.2/efm_user/05_using_efm.mdx b/product_docs/docs/efm/4.2/efm_user/05_using_efm.mdx
@@ -94,7 +94,7 @@ For example, if the properties file on node `10.0.1.10` includes a setting of `p
 efm set-priority acctg 10.0.1.10 1
 ```
 
-In the event of a failover, Failover Manager will first retrieve information from Postgres streaming replication to confirm which Standby node has the most recent data, and promote the node with the least chance of data loss. If two Standby nodes contain equally up-to-date data, the node with a higher user-specified priority value will be promoted to Primary unless [use.replay.tiebreaker](04_configuring_efm/01_cluster_properties/#use_replay_tiebreaker) is set to `false` . To check the priority value of your Standby nodes, use the command:
+In the event of a failover, Failover Manager will first retrieve information from Postgres streaming replication to confirm which Standby node has the most recent data, and promote the node with the least chance of data loss. If two Standby nodes contain equally up-to-date data, the node with a higher user-specified priority value will be promoted to Primary unless [use.replay.tiebreaker](04_configuring_efm/01_cluster_properties/#use_replay_tiebreaker) is set to `true` . To check the priority value of your Standby nodes, use the command:
 
 ```text
 efm cluster-status <cluster_name>

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
@@ -22,9 +22,7 @@ EDB\*Loader features include:
 These features are explained in detail in the following sections.
 
 !!! Note
-    The following are important version compatibility restrictions between the EDB\*Loader client and the database server.
-
-When you invoke the EDB\*Loader program (called `edbldr`), you pass in parameters and directive information to the database server. **We strongly recommend that the version 12 EDB\*Loader client (the edbldr program supplied with Advanced Server 12) be used to load data only into version 12 of the database server. In general, the EDB\*Loader client and database server should be the same version.**
+    When you invoke the EDB\*Loader program (called `edbldr`), you pass in parameters and directive information to the database server. **We strongly recommend that the version 12 EDB\*Loader client (the edbldr program supplied with Advanced Server 12) be used to load data only into version 12 of the database server. In general, the EDB\*Loader client and database server should be the same version.**
 
 <div id="data_loading_methods" class="registered_link"></div>
 

diff --git a/.../epas/13/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx b/.../epas/13/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx
@@ -8,7 +8,7 @@ legacyRedirectsGenerated:
 
 <div id="edb_redwood_raw_names" class="registered_link"></div>
 
-When `edb_redwood_raw_names` is set to its default value of `FALSE`, database object names such as table names, column names, trigger names, program names, user names, etc. appear in uppercase letters when viewed from Oracle catalogs (for a complete list of supported catalog views, see the *Database Compatibility for Oracle Catalog Views Guide*). In addition, quotation marks enclose names that were created with enclosing quotation marks.
+When `edb_redwood_raw_names` is set to its default value of `FALSE`, database object names such as table names, column names, trigger names, program names, user names, etc. appear in uppercase letters when viewed from Oracle catalogs (for a complete list of supported catalog views, see the *Database Compatibility for Oracle Developers Catalog Views Guide*). In addition, quotation marks enclose names that were created with enclosing quotation marks.
 
 When `edb_redwood_raw_names` is set to `TRUE`, the database object names are displayed exactly as they are stored in the PostgreSQL system catalogs when viewed from the Oracle catalogs. Thus, names created without enclosing quotation marks appear in lowercase as expected in PostgreSQL. Names created with enclosing quotation marks appear exactly as they were created, but without the quotation marks.
 

diff --git a/.../docs/epas/13/epas_compat_ora_dev_guide/02_sql_tutorial/09_the_sql_language.mdx b/.../docs/epas/13/epas_compat_ora_dev_guide/02_sql_tutorial/09_the_sql_language.mdx
@@ -10,7 +10,7 @@ legacyRedirectsGenerated:
 
 Advanced Server supports SQL language that is compatible with Oracle syntax as well as syntax and commands for extended functionality (functionality that does not provide database compatibility for Oracle or support Oracle-styled applications).
 
-The *Database Compatibility for Oracle Developer's SQL Guide* provides detailed information about:
+The *Database Compatibility for Oracle Developers SQL Guide* provides detailed information about:
 
 -   Compatible SQL syntax and language elements
 -   Data types

diff --git a/product_docs/docs/epas/13/epas_compat_ora_dev_guide/07_open_client_library.mdx b/product_docs/docs/epas/13/epas_compat_ora_dev_guide/07_open_client_library.mdx
@@ -14,7 +14,7 @@ The following diagram compares the Open Client Library and Oracle Call Interface
 
 ![Open Client Library](images/open_client_library.png)
 
-For detailed usage information about the Open Client Library and the supported functions, see the EDB Postgres Advanced Server OCL Connector Guide:
+For detailed usage information about the Open Client Library and the supported functions, see the *EDB Postgres Advanced Server OCL Connector Guide*:
 
 <https://www.enterprisedb.com/docs/ocl_connector/latest/>
 

diff --git a/product_docs/docs/epas/13/epas_compat_ora_dev_guide/08_oracle_catalog_views.mdx b/product_docs/docs/epas/13/epas_compat_ora_dev_guide/08_oracle_catalog_views.mdx
@@ -8,6 +8,6 @@ legacyRedirectsGenerated:
 
 <div id="oracle_catalog_views" class="registered_link"></div>
 
-The Oracle Catalog Views provide information about database objects in a manner compatible with the Oracle data dictionary views. Information about the supported views is now available in the *Database Compatibility for Oracle Developer’s Catalog Views Guide*, available at:
+The Oracle Catalog Views provide information about database objects in a manner compatible with the Oracle data dictionary views. Information about the supported views is now available in the *Database Compatibility for Oracle Developers Catalog Views Guide*, available at:
 
 <https://www.enterprisedb.com/docs/epas/latest/epas_compat_cat_views/>
diff --git a/product_docs/docs/epas/13/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx b/product_docs/docs/epas/13/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx
@@ -15,6 +15,6 @@ Compatible tools and utility programs can allow a developer to work with Advance
 -   EDB\*Wrap
 -   The Dynamic Runtime Instrumentation Tools Architecture (DRITA)
 
-For detailed information about the functionality supported by Advanced Server, see the *Database Compatibility for Oracle Developer’s Tools and Utilities Guide*, available at:
+For detailed information about the functionality supported by Advanced Server, see the *Database Compatibility for Oracle Developers Tools and Utilities Guide*, available at:
 
 <https://www.enterprisedb.com/docs/epas/latest/epas_compat_tools_guide/>
diff --git a/product_docs/docs/epas/13/epas_compat_ora_dev_guide/11_system_catalog_tables.mdx b/product_docs/docs/epas/13/epas_compat_ora_dev_guide/11_system_catalog_tables.mdx
@@ -10,6 +10,6 @@ legacyRedirectsGenerated:
 
 The system catalog tables contain definitions of database objects that are available to Advanced Server; the layout of the system tables is subject to change. If you are writing an application that depends on information stored in the system tables, it would be prudent to use an existing catalog view, or create a catalog view to isolate the application from changes to the system table.
 
-For detailed information about the system catalog tables, see the *Database Compatibility for Oracle Developer’s Catalog Views Guide*, available at:
+For detailed information about the system catalog tables, see the *Database Compatibility for Oracle Developers Catalog Views Guide*, available at:
 
 <https://www.enterprisedb.com/docs/epas/latest/epas_compat_cat_views/>
diff --git a/product_docs/docs/epas/13/epas_compat_ora_dev_guide/index.mdx b/product_docs/docs/epas/13/epas_compat_ora_dev_guide/index.mdx
@@ -21,9 +21,9 @@ Database Compatibility for Oracle means that an application runs in an Oracle en
 
 For detailed information about the compatible SQL syntax, data types, and views, see the *Database Compatibility for Oracle Developers SQL Guide*.
 
-The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in the *Database Compatibility for Oracle Developers Built-in Packages Guide.*
+The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in the *Database Compatibility for Oracle Developers Built-in Package Guide*.
 
-For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an Advanced Server installation, see the *Database Compatibility for Oracle Developers Tools and Utilities Guide.*
+For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an Advanced Server installation, see the *Database Compatibility for Oracle Developers Tools and Utilities Guide*.
 
 For applications written using the Oracle Call Interface (OCI), EDB’s Open Client Library (OCL) provides interoperability with these applications. For detailed information about using the Open Client Library, see the *EDB Postgres Advanced Server OCL Connector Guide*.
 

diff --git a/product_docs/docs/epas/13/epas_compat_reference/index.mdx b/product_docs/docs/epas/13/epas_compat_reference/index.mdx
@@ -16,7 +16,7 @@ Database Compatibility for Oracle means that an application runs in an Oracle en
 This guide provides reference material about the compatible data types supported by Advanced Server. Reference information about:
 
 -   Compatible SQL Language syntax is provided in the *Database Compatibility for Oracle Developers SQL Guide*.
--   Compatible Catalog Views is provided in the *Database Compatibility for Oracle Developers Catalog View Guide*.
+-   Compatible Catalog Views is provided in the *Database Compatibility for Oracle Developers Catalog Views Guide*.
 
 Developing an application that is compatible with Oracle databases in the Advanced Server requires special attention to which features are used in the construction of the application. For example, developing a compatible application means selecting:
 

diff --git a/...ms/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx b/...ms/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx
@@ -35,7 +35,7 @@ However, certain data types have alternative names referred to as *aliases*, whi
 
 For example, there are fixed length character data types that can be specified as `CHAR` or `CHARACTER`. There are variable length character data types that can be specified as `CHAR VARYING, CHARACTER VARYING, VARCHAR,` or `VARCHAR2`. For integers, there are `BINARY_INTEGER, PLS_INTEGER,` and `INTEGER` data types. For numbers, there are `NUMBER, NUMERIC, DEC,` and `DECIMAL` data types.
 
-For detailed information about the data types supported by Advanced Server, see the Database Compatibility for Oracle Developers Reference Guide, available from EDB at:
+For detailed information about the data types supported by Advanced Server, see the *Database Compatibility for Oracle Developers Reference Guide*, available from EDB at:
 
 [https://www.enterprisedb.com/docs](/epas/latest/epas_compat_reference/)
 

diff --git a/product_docs/docs/epas/13/epas_compat_spl/10_collections/02_nested_tables.mdx b/product_docs/docs/epas/13/epas_compat_spl/10_collections/02_nested_tables.mdx
@@ -26,7 +26,7 @@ TYPE <tbltype> IS TABLE OF { <datatype> | <rectype> | <objtype> };
 `tbltype` is an identifier assigned to the nested table type. `datatype` is a scalar data type such as `VARCHAR2` or `NUMBER`. `rectype` is a previously defined record type. `objtype` is a previously defined object type.
 
 !!! Note
-    You can use the `CREATE TYPE` command to define a nested table type that is available to all SPL programs in the database. See the Database Compatibility for Oracle Developers Reference Guide for more information about the `CREATE TYPE` command.
+    You can use the `CREATE TYPE` command to define a nested table type that is available to all SPL programs in the database. See the *Database Compatibility for Oracle Developers Reference Guide* for more information about the `CREATE TYPE` command.
 
 In order to make use of the table, a *variable* must be declared of that nested table type. The following is the syntax for declaring a table variable.
 

diff --git a/product_docs/docs/epas/13/epas_compat_sql/21_create_public_database_link.mdx b/product_docs/docs/epas/13/epas_compat_sql/21_create_public_database_link.mdx
@@ -166,7 +166,7 @@ systemctl restart edb-as-13
 
 The particular script file that needs to be modified to include the `LD_LIBRARY_PATH` setting depends upon the Advanced Server version, the Linux system on which it was installed, and whether it was installed with the graphical installer or an RPM package.
 
-See the appropriate version of the `EDB Postgres Advanced Server Installation Guide` to determine the service script that affects the startup environment. The installation guides can be found at the following location:
+See the appropriate version of the *EDB Postgres Advanced Server Installation Guide* to determine the service script that affects the startup environment. The installation guides can be found at the following location:
 
 [https://www.enterprisedb.com/docs](/epas/latest/)
 

diff --git a/..._table_set_subpartition_template/01_example_setting_a_subpartition_template.mdx b/..._table_set_subpartition_template/01_example_setting_a_subpartition_template.mdx
@@ -83,7 +83,7 @@ ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' and partition_name =
 
 ## Example - Resetting a SUBPARTITION TEMPLATE
 
-The following example creates a list-partitioned table `sales` that is list partitioned by `country` and has subpartitioned by `part_no`. Use the following command to create the `sales` table:
+The following example creates a list-partitioned table `sales` that is list partitioned by `country` and hash subpartitioned by `part_no`. Use the following command to create the `sales` table:
 
 ```text
 CREATE TABLE sales
@@ -102,7 +102,7 @@ PARTITION BY LIST (country) SUBPARTITION BY HASH (part_no) SUBPARTITIONS 3
 );
 ```
 
-The table contains three partitions (`AMERICAS`, `ASIA`, and `EUROPE`), each partition consists of three subpartitions with system-generated names.
+The table contains three partitions (`americas`, `asia`, and `europe`), each partition consists of three subpartitions with system-generated names.
 
 ```text
 edb=# SELECT table_name, partition_name, subpartition_name FROM

diff --git a/product_docs/docs/epas/13/epas_compat_tools_guide/02_edb_loader.mdx b/product_docs/docs/epas/13/epas_compat_tools_guide/02_edb_loader.mdx
@@ -23,16 +23,15 @@ These features are explained in detail in the following sections.
 
 !!! Note
     The following are important version compatibility restrictions between the EDB\*Loader client and the database server.
-
--   When you invoke the EDB\*Loader program (called `edbldr`), you pass in parameters and directive information to the database server. **We strongly recommend that the version 13 EDB\*Loader client (the edbldr program supplied with Advanced Server 13) be used to load data only into version 13 of the database server. In general, the EDB\*Loader client and database server should be the same version.**
-
--   Using EDB\*Loader in conjunction with connection poolers such as PgPool-II and PgBouncer is not supported. EDB\*Loader must connect directly to Advanced Server version 13. Alternatively, the following commands are some of the options that can be used for loading data through connection poolers:
-
-    ```
-    psql \copy
-    jdbc copyIn
-    psycopg2 copy_from
-    ```
+
+    -   When you invoke the EDB\*Loader program (called `edbldr`), you pass in parameters and directive information to the database server. **We strongly recommend that the version 13 EDB\*Loader client (the edbldr program supplied with Advanced Server 13) be used to load data only into version 13 of the database server. In general, the EDB\*Loader client and database server should be the same version.**
+    -   Using EDB\*Loader in conjunction with connection poolers such as PgPool-II and PgBouncer is not supported. EDB\*Loader must connect directly to Advanced Server version 13. Alternatively, the following commands are some of the options that can be used for loading data through connection poolers:
+
+        ```
+        psql \copy
+        jdbc copyIn
+        psycopg2 copy_from
+       ```
 
 <div id="data_loading_methods" class="registered_link"></div>