diff --git a/build-sources.json b/build-sources.json index 59d7e261d15..cff13cf9084 100644 --- 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 index b3245b1838b..f2b28f045c1 100644 --- 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 index 25fb74d736d..fc2d9b15eed 100644 --- 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 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 index 65af68937c9..46d5089384c 100644 --- 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 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 index c1167b70b96..0c3fa8008cf 100644 --- 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 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 d47d62c7dd1..0b05a510c7b 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 @@ -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.** diff --git a/product_docs/docs/epas/13/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx b/product_docs/docs/epas/13/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx index d1f7ac8b78f..4b64ad531fd 100644 --- a/product_docs/docs/epas/13/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx +++ b/product_docs/docs/epas/13/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx @@ -8,7 +8,7 @@ legacyRedirectsGenerated: -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/product_docs/docs/epas/13/epas_compat_ora_dev_guide/02_sql_tutorial/09_the_sql_language.mdx b/product_docs/docs/epas/13/epas_compat_ora_dev_guide/02_sql_tutorial/09_the_sql_language.mdx index 5f9f487b938..63a4774aa24 100644 --- a/product_docs/docs/epas/13/epas_compat_ora_dev_guide/02_sql_tutorial/09_the_sql_language.mdx +++ b/product_docs/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 index ea15398f48b..b036ae75a4a 100644 --- 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*: 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 index 1f5d1d3e323..e8c7285ba5e 100644 --- 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: -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: 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 index 1213ed88c24..28be7e65062 100644 --- 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: 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 index 8999980afa7..21a4d82ab8b 100644 --- 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: 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 index 0911a75f66c..bd175c0b873 100644 --- 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 index 06337fd8ef6..7758fe6dff6 100644 --- 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/product_docs/docs/epas/13/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx b/product_docs/docs/epas/13/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx index 74ed997a62a..50e1b1bec12 100644 --- a/product_docs/docs/epas/13/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx +++ b/product_docs/docs/epas/13/epas_compat_spl/02_spl_programs/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 index ad997717d11..cb9d41fea1d 100644 --- 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 IS TABLE OF { | | }; `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 index 6a11f8b4aa8..6b568696b33 100644 --- 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/product_docs/docs/epas/13/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/01_example_setting_a_subpartition_template.mdx b/product_docs/docs/epas/13/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/01_example_setting_a_subpartition_template.mdx index 1b83e07fc43..4858bc556d5 100644 --- a/product_docs/docs/epas/13/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/01_example_setting_a_subpartition_template.mdx +++ b/product_docs/docs/epas/13/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/11_alter_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 index 31b6f3cfc58..f6218e312ea 100644 --- 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 + ``` diff --git a/product_docs/docs/epas/13/epas_guide/01_introduction/index.mdx b/product_docs/docs/epas/13/epas_guide/01_introduction/index.mdx index 83f8aca53e1..82bd16e9035 100644 --- a/product_docs/docs/epas/13/epas_guide/01_introduction/index.mdx +++ b/product_docs/docs/epas/13/epas_guide/01_introduction/index.mdx @@ -8,29 +8,29 @@ legacyRedirectsGenerated: The following features have been changed in EDB Postgres Advanced Server 12 to create Advanced Server 13: -- Advanced Server now supports the `PARALLEL` | `NOPARALLEL` clause in the `CREATE TABLE, ALTER TABLE, CREATE INDEX`, and `ALTER INDEX` commands to enable or disable parallelism on an index or a table. For information, see the *Database Compatibility for Oracle Developer's SQL Guide*. -- Advanced Server now supports `USING INDEX ... create_index_statement` clause in the `CREATE TABLE`, and `ALTER TABLE` commands to explicitly create an index on a table. For information, see the *Database Compatibility for Oracle Developer's SQL Guide*. +- Advanced Server now supports the `PARALLEL` | `NOPARALLEL` clause in the `CREATE TABLE, ALTER TABLE, CREATE INDEX`, and `ALTER INDEX` commands to enable or disable parallelism on an index or a table. For information, see the *Database Compatibility for Oracle Developers SQL Guide*. +- Advanced Server now supports `USING INDEX ... create_index_statement` clause in the `CREATE TABLE`, and `ALTER TABLE` commands to explicitly create an index on a table. For information, see the *Database Compatibility for Oracle Developers SQL Guide*. - Advanced Server introduces `AUTOMATIC LIST PARTITIONING`, which allows a database to automatically create a new partition if the partitioning key value does not correspond to an existing partition. For information, see the *Database Compatibility Table Partitioning Guide*. -- Advanced Server has added the `STATS_MODE` function that takes an argument a set of values to return the most frequent input value. For information, see the *Database Compatibility for Oracle Developer's Reference Guide*. -- Advanced Server has added the `SYSDATE` fuction that returns the timestamp without time zone. For information, see the *Database Compatibility for Oracle Developer's Reference Guide*. -- Advanced Server has added `smallint, init, bigint` and `numeric` variants to the `MEDIAN` function. For information, see the *Database Compatibility for Oracle Developer's Reference Guide*. -- Advanced Server has added support for the `FM` format in the `TO_NUMBER` function. For information, see the *Database Compatibility for Oracle Developer's Reference Guide*. +- Advanced Server has added the `STATS_MODE` function that takes an argument a set of values to return the most frequent input value. For information, see the *Database Compatibility for Oracle Developers Reference Guide*. +- Advanced Server has added the `SYSDATE` fuction that returns the timestamp without time zone. For information, see the *Database Compatibility for Oracle Developers Reference Guide*. +- Advanced Server has added `smallint, init, bigint` and `numeric` variants to the `MEDIAN` function. For information, see the *Database Compatibility for Oracle Developers Reference Guide*. +- Advanced Server has added support for the `FM` format in the `TO_NUMBER` function. For information, see the *Database Compatibility for Oracle Developers Reference Guide*. - Advanced Server now supports statement logging and records the number of rows processed during bulk execution. For information, see `edb_log_every_bulk_value` under [Reporting and Logging / What to Log](../03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/06_reporting_and_logging_what_to_log/#reporting_and_logging_what_to_log). -- Advanced Server has added a new GUC to support Oracle-style display output by setting `dbms_output.serveroutput` to `FALSE` in the `DBMS_OUTPUT` package. For information, see the *Database Compatibility for Oracle Developer's Built-in Package Guide*. -- EDB\*Loader now supports `HANDLE_CONFLICTS` parameter to move duplicate records to the `BAD` file. For information, see the *Database Compatibility for Oracle Developer's Tools and Utilities Guide*. -- Advanced Server has added `ALTER DIRECTORY ...OWNER TO` command to change the owner of a directory. For information, see the *Database Compatibility for Oracle Developer's SQL Guide*. -- Advanced Server has added `ALTER TRIGGER ...ON AUTHORIZATION` command to change an owner of the trigger's implicit objects. For information, see the *Database Compatibility for Oracle Developer's SQL Guide*. -- EDB\*Loader now supports `-c CONNECTION STRING` or `connstr=CONNECTION_STRING` parameter, which allows you to specify the SSL parameters and the connection parameters supported by libpq. For information, see the *Database Compatibility for Oracle Developer's Tools and Utilities Guide*. -- Advanced Server has added the `TO_TIMESTAMP_TZ` function that converts a timestamp formatted string to a `TIMESTAMPTZ` datatype. For information, see the *Database Compatibility for Oracle Developer's Reference Guide*. +- Advanced Server has added a new GUC to support Oracle-style display output by setting `dbms_output.serveroutput` to `FALSE` in the `DBMS_OUTPUT` package. For information, see the *Database Compatibility for Oracle Developers Built-in Package Guide*. +- EDB\*Loader now supports `HANDLE_CONFLICTS` parameter to move duplicate records to the `BAD` file. For information, see the *Database Compatibility for Oracle Developers Tools and Utilities Guide*. +- Advanced Server has added `ALTER DIRECTORY ...OWNER TO` command to change the owner of a directory. For information, see the *Database Compatibility for Oracle Developers SQL Guide*. +- Advanced Server has added `ALTER TRIGGER ...ON AUTHORIZATION` command to change an owner of the trigger's implicit objects. For information, see the *Database Compatibility for Oracle Developers SQL Guide*. +- EDB\*Loader now supports `-c CONNECTION STRING` or `connstr=CONNECTION_STRING` parameter, which allows you to specify the SSL parameters and the connection parameters supported by libpq. For information, see the *Database Compatibility for Oracle Developers Tools and Utilities Guide*. +- Advanced Server has added the `TO_TIMESTAMP_TZ` function that converts a timestamp formatted string to a `TIMESTAMPTZ` datatype. For information, see the *Database Compatibility for Oracle Developers Reference Guide*. - Advanced Server has added additional fields to make logs consistent across both CSV and XML audit logs. For information, see [EDB Audit Logging](../03_database_administration/05_edb_audit_logging/#edb_audit_logging). -- Advanced Server has added a new GUC `edb_dblink_oci.rescan` to control the scan type for the remote statement. For information, see the *Database Compatibility for Oracle Developer's SQL Guide*. -- Advanced Server has added support for `utl_http.end_of_body` exception in the `UTL_HTTP` package to handle error from `read_line, read_text`, and `read_raw` package procedures when no data is present in the response body. For information, see the *Database Compatibility for Oracle Developer's Built-in Package Guide*. -- Advanced Server now supports the `forward declaration` of function or procedure inside a package body. For information, see the *Database Compatibility for Oracle Developer's SQL Guide*. +- Advanced Server has added a new GUC `edb_dblink_oci.rescan` to control the scan type for the remote statement. For information, see the *Database Compatibility for Oracle Developers SQL Guide*. +- Advanced Server has added support for `utl_http.end_of_body` exception in the `UTL_HTTP` package to handle error from `read_line, read_text`, and `read_raw` package procedures when no data is present in the response body. For information, see the *Database Compatibility for Oracle Developers Built-in Package Guide*. +- Advanced Server now supports the `forward declaration` of function or procedure inside a package body. For information, see the *Database Compatibility for Oracle Developers SQL Guide*. - Advanced Server introduces `PARTITIONS, SUBPARTITIONS` number to create automatic hash partitions at subpartition level and `STORE IN` clause to specify the tablespaces to store the autogenerated partitions or subpartitions. For information, see the *Database Compatibility Table Partitioning Guide*. -- Advanced Server has added support for `AES192` and `AES256` in the `DBMS_CRYPTO` package for encrypting and decrypting data types. For information, see the *Database Compatibility for Oracle Developer's Built-in Package Guide*. +- Advanced Server has added support for `AES192` and `AES256` in the `DBMS_CRYPTO` package for encrypting and decrypting data types. For information, see the *Database Compatibility for Oracle Developers Built-in Package Guide*. - Advanced Server now supports `pg_hba.conf` entry upon successful authentication with the server. For information, see [Modifying the pg_hba.conf File](../03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying_the_pg_hba_conf_file). -- Advanced Server has implemented `WHEN` condition inside `COMPOUND TRIGGER` to execute a trigger when specified conditions occur. For information, see the *Database Compatibility for Oracle Developer's SQL Guide* or *Database Compatibility Stored Procedural Language Guide*. -- Advanced Server has added support for `column_value_long`, `define_column_long`, and `last_error_position` in the `DBMS_SQL` package to define and return a part of the `LONG` column. For information, see the *Database Compatibility for Oracle Developer's Built-in Package Guide*. +- Advanced Server has implemented `WHEN` condition inside `COMPOUND TRIGGER` to execute a trigger when specified conditions occur. For information, see the *Database Compatibility for Oracle Developers SQL Guide* or *Database Compatibility Stored Procedural Language Guide*. +- Advanced Server has added support for `column_value_long`, `define_column_long`, and `last_error_position` in the `DBMS_SQL` package to define and return a part of the `LONG` column. For information, see the *Database Compatibility for Oracle Developers Built-in Package Guide*. ## Limitations diff --git a/product_docs/docs/epas/13/epas_guide/02_enhanced_compatibility_features.mdx b/product_docs/docs/epas/13/epas_guide/02_enhanced_compatibility_features.mdx index 1de3952d559..3d656604e42 100644 --- a/product_docs/docs/epas/13/epas_guide/02_enhanced_compatibility_features.mdx +++ b/product_docs/docs/epas/13/epas_guide/02_enhanced_compatibility_features.mdx @@ -6,7 +6,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/13/enhanced_compatibility_features.html" --- -Advanced Server includes extended functionality that provides compatibility for syntax supported by Oracle applications. Detailed information about the compatibility features supported by Advanced Server is provided in the Database Compatibility for Oracle Developers Guide; the version-specific guides are available at: +Advanced Server includes extended functionality that provides compatibility for syntax supported by Oracle applications. Detailed information about the compatibility features supported by Advanced Server is provided in the *Database Compatibility for Oracle Developers Guide*; the version-specific guides are available at: [https://www.enterprisedb.com/docs](/epas/latest/epas_compat_ora_dev_guide/) @@ -130,7 +130,7 @@ For detailed information about the functions supported by the Open Client Librar ## Utilities -For detailed information about the compatible syntax supported by the utilities listed below, see the *Database Compatibility for Oracle Developer's Tools and Utilities Guide*, available at: +For detailed information about the compatible syntax supported by the utilities listed below, 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_inst_windows/03_installing_advanced_server_with_the_interactive_installer/01_performing_a_graphical_installation_on_windows.mdx b/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/01_performing_a_graphical_installation_on_windows.mdx index a66eddd4628..fb52d0b1f10 100644 --- a/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/01_performing_a_graphical_installation_on_windows.mdx +++ b/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/01_performing_a_graphical_installation_on_windows.mdx @@ -156,7 +156,7 @@ If you select `Compatible with Oracle`, the installation will include the follow | `utl_url` | Provides a way to escape illegal and reserved characters within an URL. | | `utl_raw` | Provides a way to manipulate or retrieve the length of raw data types. | -This is not a comprehensive list of the compatibility features for Oracle included when Advanced Server is installed in `Compatible with Oracle` mode; for more information, see the *Database Compatibility for Oracle Developer’s Built-in Package Guide* available from the EDB website at: +This is not a comprehensive list of the compatibility features for Oracle included when Advanced Server is installed in `Compatible with Oracle` mode; for more information, see the *Database Compatibility for Oracle Developers Built-in Package Guide* available from the EDB website at: [https://www.enterprisedb.com/docs](/epas/latest/epas_compat_bip_guide/) diff --git a/product_docs/docs/epas/13/epas_inst_windows/index.mdx b/product_docs/docs/epas/13/epas_inst_windows/index.mdx index 9d5bf1fa07f..1ce18fdff89 100644 --- a/product_docs/docs/epas/13/epas_inst_windows/index.mdx +++ b/product_docs/docs/epas/13/epas_inst_windows/index.mdx @@ -10,7 +10,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/installation-getting-started/installation-guide-for-windows/13/genindex.html" --- -The EDB Postgres Advanced Server Installation Guide is a comprehensive guide to installing EDB Postgres Advanced Server (Advanced Server). In this guide you will find detailed information about: +The *EDB Postgres Advanced Server Installation Guide* is a comprehensive guide to installing EDB Postgres Advanced Server (Advanced Server). In this guide you will find detailed information about: - Software prerequisites for Advanced Server 13 installation on Windows. - Graphical installation options available through the interactive setup wizard on Windows. diff --git a/product_docs/docs/epas/13/epas_qs_windows/index.mdx b/product_docs/docs/epas/13/epas_qs_windows/index.mdx index 7bc8729be2e..7f85236c392 100644 --- a/product_docs/docs/epas/13/epas_qs_windows/index.mdx +++ b/product_docs/docs/epas/13/epas_qs_windows/index.mdx @@ -198,7 +198,7 @@ If you select `Compatible with Oracle`, the installation will include the follow | `utl_url` | Provides a way to escape illegal and reserved characters within an URL. | | `utl_raw` | Provides a way to manipulate or retrieve the length of raw data types. | -This is not a comprehensive list of the compatibility features for Oracle included when Advanced Server is installed in `Compatible with Oracle` mode; for more information, see the *Database Compatibility for Oracle Developer’s Built-in Package Guide* available from the EDB website at: +This is not a comprehensive list of the compatibility features for Oracle included when Advanced Server is installed in `Compatible with Oracle` mode; for more information, see the *Database Compatibility for Oracle Developers Built-in Package Guide* available from the EDB website at: [https://www.enterprisedb.com/docs](/epas/latest/epas_compat_bip_guide/) 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 d68086306a3..b74ee1fcf27 100644 --- a/product_docs/docs/epas/13/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/13/epas_rel_notes/index.mdx @@ -123,10 +123,10 @@ The major highlights of this release are : For information about Advanced Server features that are compatible with Oracle databases, see the following guides: -- *Database Compatibility for Oracle Developer's SQL Guide* -- *Database Compatibility for Oracle Developer's Reference Guide* -- *Database Compatibility for Oracle Developer's Built-in Package Guide* -- *Database Compatibility for Oracle Developer's Tools and Utilities Guide* +- *Database Compatibility for Oracle Developers SQL Guide* +- *Database Compatibility for Oracle Developers Reference Guide* +- *Database Compatibility for Oracle Developers Built-in Package Guide* +- *Database Compatibility for Oracle Developers Tools and Utilities Guide* - *Database Compatibility Table Partitioning Guide* - *Database Compatibility Stored Procedural Language Guide* diff --git a/product_docs/docs/epas/13/epas_upgrade_guide/index.mdx b/product_docs/docs/epas/13/epas_upgrade_guide/index.mdx index da84b930e22..0b509701f33 100644 --- a/product_docs/docs/epas/13/epas_upgrade_guide/index.mdx +++ b/product_docs/docs/epas/13/epas_upgrade_guide/index.mdx @@ -10,7 +10,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/installation-getting-started/upgrade-guide/13/genindex.html" --- -The EDB Postgres Advanced Server Upgrade Guide is a comprehensive guide about upgrading EDB Postgres Advanced Server (Advanced Server). In this guide you will find detailed information about using: +The *EDB Postgres Advanced Server Upgrade Guide* is a comprehensive guide about upgrading EDB Postgres Advanced Server (Advanced Server). In this guide you will find detailed information about using: - `pg_upgrade` to upgrade from an earlier version of Advanced Server to Advanced Server 13. - `yum` to perform a minor version upgrade on a Linux host. diff --git a/product_docs/docs/harp/1.0/index.mdx b/product_docs/docs/harp/1.0/index.mdx new file mode 100644 index 00000000000..7138f7ccbec --- /dev/null +++ b/product_docs/docs/harp/1.0/index.mdx @@ -0,0 +1,18 @@ +--- +navTitle: HARP +title: "High Availability Routing for Postgres (HARP)" +directoryDefaults: + description: "High Availability Routing for Postgres (HARP) is a cluster management tool for Bi-directional Replication (BDR) clusters." +--- + +High Availability Routing for Postgres (HARP) is a cluster management tool for [Bi-directional Replication (BDR)](/bdr/latest) clusters. The core design of the tool is to route all application traffic within a data center to only one lead master at a time. A distributed consensus system is used to determine availability of the BDR nodes. On failure or unavailability of the lead master HARP determines a new lead master and changes application traffic routing accordingly. + +Together with the core capabilities of BDR this mechanism of routing application traffic to the lead master node rules out split brain scenarios and allows for fast failover and switchover without risk of data loss. + +HARP requires BDR Enterprise or BDR Standard versions 3.6 and 3.7. + +!!! Note + The documentation for the latest stable release is available here: + [HARP](https://documentation.2ndquadrant.com/harp/release/latest/) + + **This is a protected area of our website, if you need access please [contact us](https://www.enterprisedb.com/contact).** diff --git a/product_docs/docs/pgbouncer/1.0/02_configuration_and_usage.mdx b/product_docs/docs/pgbouncer/1.0/02_configuration_and_usage.mdx index 1ff09199e69..e054db9aa91 100644 --- a/product_docs/docs/pgbouncer/1.0/02_configuration_and_usage.mdx +++ b/product_docs/docs/pgbouncer/1.0/02_configuration_and_usage.mdx @@ -41,7 +41,6 @@ You can specify additional database connection information in the configuration | Parameter | Description | |------------|-------------------------------------------------------------------------------------| -| `name` | The name of the database to which the client application will connect. | | `host` | The IP address of the host. | | `port` | The port on which the host is listening. | | `dbname` | The (optional) database name. | @@ -75,7 +74,6 @@ The `[pgbouncer]` section of the configuration file contains configuration detai | `auth_file` | The path to the authentication file that contains username and passwords of clients that may connect to PgBouncer. The authentication file (userlist.txt) is located in `/etc/edb/pgbouncer/`, and contains *username/password* pairs that specify the identities that clients may use to access PgBouncer. Within the authentication file, the username and password must be specified within double-quotes. To make changes to the identities that can access PgBouncer, you can edit the existing authentication file, or specify an alternate authentication file with the `auth_file` parameter. | | `auth_type` | The authentication method used by PgBouncer. May be: md5, crypt, plain, trust or any. The default value is md5. | | `default_pool_size` | The amount of user connections that are allowed to access the server. The default is 20 active connections. | -| `group_connections` | Clients providing the same application\_name will be grouped to use the same connection. The default is 0. | | `ignore_startup_parameters` | A comma-delimited list of application startup packets that PgBouncer should ignore. The default is application\_name. | | `listen_addr` | The IP address on which PgBouncer listens for client connections. If omitted, only Unix socket connections are allowed; the client must also reside on the same host as PgBouncer and may not specify a host IP address when connecting to PgBouncer. | | `listen_port` | The port that PgBouncer monitors for client connections. By default, PgBouncer listens on port 6432. | @@ -103,7 +101,6 @@ server_reset_query = DISCARD ALL ignore_startup_parameters = application_name max_client_conn = 100 default_pool_size = 20 -group_connections = 0 ``` For more information about the settings used in the `pgbouncer.ini` file, click [here](https://pgbouncer.github.io/config.html). diff --git a/product_docs/docs/repmgr/5.2.1/index.mdx b/product_docs/docs/repmgr/5.2.1/index.mdx index eb4d676fb20..097ceab8074 100644 --- a/product_docs/docs/repmgr/5.2.1/index.mdx +++ b/product_docs/docs/repmgr/5.2.1/index.mdx @@ -7,8 +7,10 @@ directoryDefaults: repmgr (Replication Manager) is among the most popular open-source tools for managing replication and failover of PostgreSQL clusters. It relies on PostgreSQL’s streaming replication and hot standby capabilities allowing DBAs to simplify the process of setting up and managing clusters having high availability as well as read scalability requirements. repmgr is distributed under GNU GPL 3 and maintained by EDB. +repmgr is distributed under GNU GPL 3 and maintained by EDB. repmgr is developed, tested and certified with PostgreSQL and EDB Postgres Extended. repmgr is not certified with EDB Postgres Advanced. + !!! Note - Looking for repmgr documentation? Head over to [repmgr.org](https://repmgr.org/) + Looking for repmgr documentation? Head over to [repmgr.org](https://repmgr.org/) !!! Key capabilities include: diff --git a/src/constants/products.js b/src/constants/products.js index ab35c70cbbc..1120baea702 100644 --- a/src/constants/products.js +++ b/src/constants/products.js @@ -6,6 +6,10 @@ export const products = { name: 'BDR (Bi-Directional Replication)', iconName: IconNames.HIGH_AVAILABILITY, }, + harp: { + name: 'High Availability Routing for Postgres (HARP)', + iconName: IconNames.HIGH_AVAILABILITY, + }, ark: { name: 'Postgres Ark', iconName: IconNames.EDB_ARK }, bart: { name: 'Backup and Recovery Tool', iconName: IconNames.EDB_BART }, efm: { name: 'Failover Manager', iconName: IconNames.EDB_EFM }, diff --git a/src/pages/index.js b/src/pages/index.js index aad1fdf3a8d..8ba331b2564 100644 --- a/src/pages/index.js +++ b/src/pages/index.js @@ -137,6 +137,9 @@ const Page = () => ( BDR (Bi-Directional Replication) + + High Availability Routing for Postgres (HARP) + Replication Server Slony