diff --git a/advocacy_docs/community/contributing/styleguide.mdx b/advocacy_docs/community/contributing/styleguide.mdx index 577473e3ad0..7c284357524 100644 --- a/advocacy_docs/community/contributing/styleguide.mdx +++ b/advocacy_docs/community/contributing/styleguide.mdx @@ -49,7 +49,7 @@ Included in this guide: * 4.6.2 [With compound adjectives](#with-compound-adjectives) * 4.7 [Directing users up and down through a topic](#directing-users-up-and-down-through-a-topic) * 4.8 [Select versus click](#select-versus-click) -* 5 [Common errors/words to avoid](#common-errors/words-to-avoid) +* 5 [Common errors/words to avoid](#common-errorswords-to-avoid) * 5.1 [Login and log in](#login-and-log-in) * 5.2 [Setup and set up](#setup-and-set-up) * 5.3 [Words to avoid](#words-to-avoid) @@ -57,14 +57,14 @@ Included in this guide: * 7 [Font treatments](#font-treatments) * 7.1 [Bold (\*\*text\*\*)](#bold-text)) * 7.2 [Courier aka code or monospace ('text')](#courier-aka-code-or-monospace-text) - * 7.3 [Italics (*text*)](#italics-text) + * 7.3 [Italics (*text*)](#italics-_text_) * 7.4 [Underline](#underline) * 8 [Links](#links) -* 9 [Admonitions: notes, tips, and warnings](#admonitions:-notes,-tips,-and-warnings) +* 9 [Admonitions: notes, tips, and warnings](#admonitions-notes-tips-and-warnings) * 9.1 [Notes](#notes) * 9.2 [Tips](#tips) * 9.3 [Warnings](#warnings) - * 9.4 [Code](#inlinextensionCode) + * 9.4 [Code](#code) * 9.4.1 [Inline code](#inline-code) * 9.4.2 [Code blocks](#code-blocks) * 10 [Tables](#tables) diff --git a/advocacy_docs/migrating/oracle/edb_migration_tools.mdx b/advocacy_docs/migrating/oracle/edb_migration_tools.mdx index 2bd466a2063..8701f379175 100644 --- a/advocacy_docs/migrating/oracle/edb_migration_tools.mdx +++ b/advocacy_docs/migrating/oracle/edb_migration_tools.mdx @@ -148,10 +148,10 @@ The EDB enhanced database connectors are available for use with EDB Postgres Adv [EDB\*Plus](/edb_plus/latest/) is a Java-based command line interface to EDB Postgres Advanced Server. EDB\*Plus accepts SQL commands, SPL anonymous blocks, and EDB\*Plus commands. EDB\*Plus commands are compatible with Oracle SQL\*Plus commands, so you can use the scripts you've already built for Oracle against the EDB Postgres Advanced Server database. #### EDB\*Loader -[EDB\*Loader](/epas/latest/epas_compat_tools_guide/02_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 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](/epas/latest/database_administration/02_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 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. #### Database links and dblink_ora functions -[Database links](/epas/latest/epas_compat_sql/21_create_public_database_link) and [dblink_ora](/epas/latest/epas_compat_ora_dev_guide/06_dblink_ora/) functions are Postgres-extension-enabled capabilities that let you pull data from Oracle to Postgres by way of SQL queries and database function calls. You can also use these technologies to help migrate data from an Oracle database. Both of these methods use the Oracle Call Interface (OCI) to connect to Oracle. After connecting, use a SQL statement to select the data from the “linked” Oracle database and insert the data into the EDB Postgres Advanced Server database. +[Database links](/epas/latest/reference/oracle_compatibility_reference/epas_compat_sql/21_create_public_database_link/) and [dblink_ora](/epas/latest/working_with_oracle_data/06_dblink_ora/) functions are Postgres-extension-enabled capabilities that let you pull data from Oracle to Postgres by way of SQL queries and database function calls. You can also use these technologies to help migrate data from an Oracle database. Both of these methods use the Oracle Call Interface (OCI) to connect to Oracle. After connecting, use a SQL statement to select the data from the “linked” Oracle database and insert the data into the EDB Postgres Advanced Server database. When deciding to use one of these two options, the database link option is usually the preferred one as it's easier to use. However, the dblink_ora functions help you to migrate some data types that the database link option doesn't, such as BLOB and CLOB data. Also, it supports using Oracle-specific functions in the queries that are executed in the Oracle database. This can provide some flexibility in extracting certain types of information, like JSON data embedded in CLOB or BLOB columns. Both of these capabilities are provided with EDB Postgres Advanced Server, but you need to set them up to use them. diff --git a/advocacy_docs/migrating/oracle/oracle_epas_comparison/app_devel_capabilities.mdx b/advocacy_docs/migrating/oracle/oracle_epas_comparison/app_devel_capabilities.mdx index 7b794e65cc7..132bd7bfbc9 100644 --- a/advocacy_docs/migrating/oracle/oracle_epas_comparison/app_devel_capabilities.mdx +++ b/advocacy_docs/migrating/oracle/oracle_epas_comparison/app_devel_capabilities.mdx @@ -35,7 +35,7 @@ Databases are a foundation of today’s data-driven enterprise, and applications ## EDB Postgres Advanced Server-compatible package support -EDB focuses on the most popular functions in packages. For some packages, not all Oracle functions are supported. For specific details, refer to the [EDB Postgres Advanced Server](../../../epas/latest/epas_compat_bip_guide/03_built-in_packages/) documentation. +EDB focuses on the most popular functions in packages. For some packages, not all Oracle functions are supported. For specific details, refer to the [EDB Postgres Advanced Server](/epas/latest/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/) documentation. | Package name | Package description | |----------------|---------------------| diff --git a/advocacy_docs/partner_docs/DBeaverPRO/04-ConfiguringDBeaverPRO.mdx b/advocacy_docs/partner_docs/DBeaverPRO/04-ConfiguringDBeaverPRO.mdx index 87905c2694c..d2ab11ce0d8 100644 --- a/advocacy_docs/partner_docs/DBeaverPRO/04-ConfiguringDBeaverPRO.mdx +++ b/advocacy_docs/partner_docs/DBeaverPRO/04-ConfiguringDBeaverPRO.mdx @@ -50,7 +50,7 @@ Implementing DBeaver PRO with EDB Postgres Advanced Server and EDB Postgres Exte 4. Select **Test Connection**. The success message appears. -[Successful Connection](Images/ExtendedTestConnection.png) +![Successful Connection](Images/ExtendedTestConnection.png) 5. Respond **OK** to the message. Then, on the **Connection Settings** window, select **Finish**. The connection is created and shown in the left-side tree. diff --git a/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/05-UsingEsriArcGISProandEsriArcGISEnterprise.mdx b/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/05-UsingEsriArcGISProandEsriArcGISEnterprise.mdx index 1df16dbc962..3dbb13fe0ec 100644 --- a/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/05-UsingEsriArcGISProandEsriArcGISEnterprise.mdx +++ b/advocacy_docs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/05-UsingEsriArcGISProandEsriArcGISEnterprise.mdx @@ -9,7 +9,7 @@ Esri created a new format for storing data with the geodatabase. If you’re cre This example adds a geodatabase to Esri ArcGIS Pro and creates an enterprise geodatabase from that data, using the sample `HongKong` database. You can substitute a different database or create your own to use. -1. Go to the `HongKong` GDB, or another downloaded geodatabase, as instructed in [GIS data](4-ConfiguringEsriArcGISProandEsriArcGISEnterprise/#gis-data), and select **Download**. +1. Go to the `HongKong` GDB, or another downloaded geodatabase, as instructed in [GIS data](04-ConfiguringEsriArcGISProandEsriArcGISEnterprise/#gis-data), and select **Download**. 2. Locate and unzip the downloaded `HongKong.gdb.zip` file. diff --git a/advocacy_docs/partner_docs/NutanixAHV/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/NutanixAHV/02-PartnerInformation.mdx index bae2cb363c2..e9dedb73c1e 100644 --- a/advocacy_docs/partner_docs/NutanixAHV/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/NutanixAHV/02-PartnerInformation.mdx @@ -7,6 +7,6 @@ description: 'Details of the partner' |   |   | | ----------- | ----------- | | **Partner name** | Nutanix | -| **Website** | [www.nutanix.com](www.nutanix.com) | +| **Website** | [www.nutanix.com](https://www.nutanix.com) | | **Partner product** | Nutanix AHV AOS 5.15.x, 6.5.x, ESXi AOS 5.15.x, 6.5.x | | **Product description** | Nutanix AHV is the native Nutanix hypervisor that offers virtualization capabilities needed to deploy and manage enterprise applications. Using EDB Postgres Advanced Server, EDB Postgres Extended Server, and PostgreSQL Server with Nutanix AHV allows for enterprise-level features to run on a secure, enterprise-grade virtulization platform. | diff --git a/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/04-ConfiguringRepostorDataProtectorforPostgreSQL.mdx b/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/04-ConfiguringRepostorDataProtectorforPostgreSQL.mdx index 948bc82ef22..ff9e4a18fb6 100644 --- a/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/04-ConfiguringRepostorDataProtectorforPostgreSQL.mdx +++ b/advocacy_docs/partner_docs/RepostorDataProtectorforPostgreSQL/04-ConfiguringRepostorDataProtectorforPostgreSQL.mdx @@ -39,9 +39,9 @@ available, including the client Spectrum Protect password. The high-level steps for installing and configuring the integration are: -1. [Configure local Spectrum Protect configuration files.](/#configure-local-spectrum-protect-configuration-files) -1. [Install Repostor Data Protector client.](#install-repostor-data-protector-client) -1. [Verify the connection to PostgreSQL psql.](/#verify-the-connection-to-postgresql-psql) +1. [Configure local Spectrum Protect configuration files.](#configure-the-local-spectrum-protect-configuration-files) +1. [Install the Repostor Data Protector client.](#install-the-repostor-data-protector-client) +1. [Verify the connection to PostgreSQL psql.](#verify-the-connection-to-postgresql-psql) 1. [Configure PostgreSQL `archive_command` to use logwriter.](#configure-postgresql-archive_command-to-use-logwriter) 1. [Set up a backup script.](#set-up-a-backup-script) diff --git a/advocacy_docs/partner_docs/SIBVisionsVisionX/03-SolutionSummary.mdx b/advocacy_docs/partner_docs/SIBVisionsVisionX/03-SolutionSummary.mdx index b8b056ab6a4..8fab694501c 100644 --- a/advocacy_docs/partner_docs/SIBVisionsVisionX/03-SolutionSummary.mdx +++ b/advocacy_docs/partner_docs/SIBVisionsVisionX/03-SolutionSummary.mdx @@ -15,4 +15,4 @@ With SIB Visions VisionX, you're vendor independent and can create a web applica When you change code outside of SIB Visions VisionX in Eclipse, the changes are pushed back into the SIB Visions VisionX visual development environment in real time. This two-way synchronization enables unlimited app development for citizen developers, business users, and pro developers. - [System Architecture](Images/system-architecture-application.png) \ No newline at end of file +![System Architecture](Images/system-architecture-application.png) \ No newline at end of file diff --git a/advocacy_docs/pg_extensions/extensionrefs.json b/advocacy_docs/pg_extensions/extensionrefs.json index f0056b8591b..67247c5c2c0 100644 --- a/advocacy_docs/pg_extensions/extensionrefs.json +++ b/advocacy_docs/pg_extensions/extensionrefs.json @@ -53,8 +53,8 @@ "tsm_system_rows": "https://www.postgresql.org/docs/current/tsm-system-rows.html", "tsm_system_time": "https://www.postgresql.org/docs/current/tsm-system-time.html", "unaccent": "https://www.postgresql.org/docs/current/unaccent.html", - "uuid-ossp": "postgresql.org/docs/current/uuid-ossp.html", - "xml2": "postgresql.org/docs/current/xml2.html", + "uuid-ossp": "https://www.postgresql.org/docs/current/uuid-ossp.html", + "xml2": "https://www.postgresql.org/docs/current/xml2.html", "ip4r": "https://github.com/RhodiumToad/ip4r", "pg_failover_slots": "https://www.enterprisedb.com/docs/pg_extensions/pg_failover_slots/", "pg_permissions": "https://github.com/cybertec-postgresql/pg_permissions", diff --git a/advocacy_docs/pg_extensions/index.mdx b/advocacy_docs/pg_extensions/index.mdx index 033cde65642..e343630ec98 100644 --- a/advocacy_docs/pg_extensions/index.mdx +++ b/advocacy_docs/pg_extensions/index.mdx @@ -84,8 +84,8 @@ Categories of extensions: tsm_system_rows✓✓✓✓✓✓✓✓ tsm_system_time✓✓✓✓✓✓✓✓ unaccent✓✓✓✓✓✓✓✓ -uuid-osspYes✓✓✓✓✓✓✓✓ -xml2Yes✓✓✓✓✓✓✓✓ +uuid-osspYes✓✓✓✓✓✓✓✓ +xml2Yes✓✓✓✓✓✓✓✓ PostgreSQL Non-Contrib Extensions/Modules ip4r✓––––––– pg_cron✓✓✓––✓✓✓ diff --git a/advocacy_docs/pg_extensions/ldap_sync/configuring.mdx b/advocacy_docs/pg_extensions/ldap_sync/configuring.mdx index a402bcc5a0c..be92b23aca5 100644 --- a/advocacy_docs/pg_extensions/ldap_sync/configuring.mdx +++ b/advocacy_docs/pg_extensions/ldap_sync/configuring.mdx @@ -11,7 +11,7 @@ Find the sample EDB LDAP Sync configuration files at `/usr/lib/python3.6/site-pa pgAgent sets up periodic synchronization tasks. Use `edb-pgagent.conf_tmpl` as the default configuration for pgAgent setup with Postgres. Copy it into the configuration directory for pgAgent with Postgres. -For more information, see the [pgAgent documentation](/docs/pem/latest/pem_online_help/10_pgagent/). +For more information, see the [pgAgent documentation](https://www.pgadmin.org/docs/pgadmin4/latest/pgagent.html). ## Setting Postgres database permissions diff --git a/advocacy_docs/postgresql_journey/02_installing/03_linux.mdx b/advocacy_docs/postgresql_journey/02_installing/03_linux.mdx index 501475436d2..beaf1638b32 100644 --- a/advocacy_docs/postgresql_journey/02_installing/03_linux.mdx +++ b/advocacy_docs/postgresql_journey/02_installing/03_linux.mdx @@ -20,7 +20,7 @@ You can quickly install PostgreSQL on most Linux systems by configuring your sys Pre-built packages and instructions for most common Linux & Unix systems are available from postgresql.org: -If you're installing EDB's Postgres Advanced Server, [instructions for Linux & Unix systems can be found on this site](/epas/latest/epas_inst_linux/), along with [a tool to generate installation scripts for each supported platform](https://repos.enterprisedb.com/). +If you're installing EDB's Postgres Advanced Server, [instructions for Linux & Unix systems can be found on this site](/epas/latest/installing/), along with [a tool to generate installation scripts for each supported platform](https://repos.enterprisedb.com/). ## Server installation details diff --git a/advocacy_docs/supported-open-source/barman/single-server-streaming/step02-backup-setup.mdx b/advocacy_docs/supported-open-source/barman/single-server-streaming/step02-backup-setup.mdx index 7924bc54237..4d3d0c842ec 100644 --- a/advocacy_docs/supported-open-source/barman/single-server-streaming/step02-backup-setup.mdx +++ b/advocacy_docs/supported-open-source/barman/single-server-streaming/step02-backup-setup.mdx @@ -89,7 +89,7 @@ create_slot = auto EOF ``` -Note that this references the users (`barman` and `streaming_barman`) that we created [in step #1 - Database Server Configuration](../step01-db-setup/). Also of interest is the value for `slot_name` - this is a replication slot that will also have to be created on the server - but we can instruct Barman to do that for us by setting `create_slot` to `auto`. +Note that this references the users (`barman` and `streaming_barman`) that we created [in step #1 - Database Server Configuration](step01-db-setup/). Also of interest is the value for `slot_name` - this is a replication slot that will also have to be created on the server - but we can instruct Barman to do that for us by setting `create_slot` to `auto`. The installation process created a brand-new barman user on the backup server, so let's switch to that for the rest of this: diff --git a/advocacy_docs/supported-open-source/patroni/installing_patroni.mdx b/advocacy_docs/supported-open-source/patroni/installing_patroni.mdx index 58f04f6c395..8ecc07b244f 100644 --- a/advocacy_docs/supported-open-source/patroni/installing_patroni.mdx +++ b/advocacy_docs/supported-open-source/patroni/installing_patroni.mdx @@ -19,7 +19,7 @@ To install Patroni, configure the [PostgreSQL](https://www.postgresql.org/downlo sudo apt-get install -y patroni ``` -See [Quick start on Debian 11](debian11_quick_start/#patroni) for a more detailed configuration example. +See [Quick start on Debian 11](debian11_quick_start/#4-patroni) for a more detailed configuration example. ### RHEL/CentOS @@ -31,4 +31,4 @@ After you configured the repositories, run the following command to install Patr sudo dnf install -y patroni patroni-etcd ``` -See [Quick start on RHEL8](rhel8_quick_start/#patroni) for a more detailed configuration example. +See [Quick start on RHEL8](rhel8_quick_start/#4-patroni) for a more detailed configuration example. diff --git a/advocacy_docs/supported-open-source/pglogical2/usage.mdx b/advocacy_docs/supported-open-source/pglogical2/usage.mdx index dce68454c54..1e16dafd50f 100644 --- a/advocacy_docs/supported-open-source/pglogical2/usage.mdx +++ b/advocacy_docs/supported-open-source/pglogical2/usage.mdx @@ -350,7 +350,7 @@ There are three preexisting replication sets named "default", "default_insert_only" and "ddl_sql". The "default" replication set is defined to replicate all changes to tables in it. The "default_insert_only" only replicates INSERTs and is meant for tables that don't have primary key (see -[Limitations](#primary-key-required) section for details). +[Limitations](limitations-and-restrictions/#primary-key-or-replica-identity-required) section for details). The "ddl_sql" replication set is defined to replicate schema changes specified by `pglogical.replicate_ddl_command` diff --git a/advocacy_docs/supported-open-source/postgresql/installing/index.mdx b/advocacy_docs/supported-open-source/postgresql/installing/index.mdx index cb5141f7f72..b834f823407 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/index.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/index.mdx @@ -2,6 +2,13 @@ navTitle: Installing title: Installing PostgreSQL indexCards: none +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. +# Leaf template: products/postgresql/index.njk + +redirects: + - /supported-open-source/postgresql/installer navigation: - requirements 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 9b1cabf0563..4103e5c54da 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 @@ -54,4 +54,4 @@ Before you begin the installation process: sudo dnf -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql15-server postgresql15-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. 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 57c6751499e..842d74bb296 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 @@ -54,4 +54,4 @@ Before you begin the installation process: sudo dnf -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql15-server postgresql15-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. 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 cf44197df80..ab4584e37ab 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 @@ -48,4 +48,4 @@ Before you begin the installation process: sudo zypper -n install postgresql-server ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql15-server`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server`. 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 c09677b6239..f8b4152a493 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 @@ -49,4 +49,4 @@ Before you begin the installation process: sudo zypper -n install postgresql-server ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql15-server`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server`. 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 1fb3e6d14ce..33ee7d2dd98 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 @@ -42,4 +42,4 @@ Before you begin the installation process: sudo yum -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql15-server postgresql15-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. 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 e8024039709..8e18e6892b8 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 @@ -37,4 +37,4 @@ Before you begin the installation process: sudo apt-get -y install postgresql- ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql-15`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql-16`. 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 62d817c16c8..a5b22f8e183 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 @@ -37,4 +37,4 @@ Before you begin the installation process: sudo apt-get -y install postgresql- ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql-15`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql-16`. 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 b43454a72e8..f8fdc05082c 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 @@ -58,4 +58,4 @@ Before you begin the installation process: sudo dnf -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql15-server postgresql15-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. 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 9883b477c44..51f23e38505 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 @@ -58,4 +58,4 @@ Before you begin the installation process: sudo dnf -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql15-server postgresql15-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. 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 82eab0899f2..3e897e769e2 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 @@ -48,4 +48,4 @@ Before you begin the installation process: sudo yum -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql15-server postgresql15-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. 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 f461b7dbf08..fe2c8b6c87b 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 @@ -52,4 +52,4 @@ Before you begin the installation process: sudo dnf -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql15-server postgresql15-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. 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 ea968986840..85f8c1cf8d8 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 @@ -52,4 +52,4 @@ Before you begin the installation process: sudo dnf -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql15-server postgresql15-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. 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 496cd607ca6..4381dbba184 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 @@ -48,4 +48,4 @@ Before you begin the installation process: sudo zypper -n install postgresql-server ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql15-server`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server`. 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 3db686f432a..a7bf36393d0 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 @@ -49,4 +49,4 @@ Before you begin the installation process: sudo zypper -n install postgresql-server ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql15-server`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server`. 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 7c609647e78..25f8d6867d2 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 @@ -37,4 +37,4 @@ Before you begin the installation process: sudo apt-get -y install postgresql- ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql-15`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql-16`. 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 52ca7708bd4..e742ba3fbcd 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 @@ -37,4 +37,4 @@ Before you begin the installation process: sudo apt-get -y install postgresql- ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql-15`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql-16`. 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 46c51df78dd..25129c010d1 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 @@ -37,4 +37,4 @@ Before you begin the installation process: sudo apt-get -y install postgresql- ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 15, the package name would be `postgresql-15`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql-16`. diff --git a/install_template/config.yaml b/install_template/config.yaml index 2c496aa4063..de166c1c0ef 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -109,55 +109,55 @@ products: platforms: - name: CentOS 7 arch: x86_64 - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: RHEL 8 arch: ppc64le - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: RHEL 9 arch: ppc64le - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: AlmaLinux 9 or Rocky Linux 9 arch: x86_64 - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: Debian 10 arch: x86_64 - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: Debian 11 arch: x86_64 - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: Ubuntu 18.04 arch: x86_64 - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: Ubuntu 22.04 arch: x86_64 - supported versions: [15] + supported versions: [15, 16] - name: SLES 12 arch: x86_64 - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: SLES 12 arch: ppc64le - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: SLES 15 arch: x86_64 - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: SLES 15 arch: ppc64le - supported versions: [14, 15] + supported versions: [14, 15, 16] - name: EDB ODBC Connector platforms: - name: CentOS 7 @@ -889,55 +889,55 @@ products: platforms: - name: CentOS 7 arch: x86_64 - supported versions: [15] + supported versions: [15, 16] - name: RHEL 8 arch: ppc64le - supported versions: [15] + supported versions: [15, 16] - name: RHEL 9 arch: ppc64le - supported versions: [15] + supported versions: [15, 16] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [15] + supported versions: [15, 16] - name: AlmaLinux 9 or Rocky Linux 9 arch: x86_64 - supported versions: [15] + supported versions: [15, 16] - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [15] + supported versions: [15, 16] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [15] + supported versions: [15, 16] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [15] + supported versions: [15, 16] - name: Debian 10 arch: x86_64 - supported versions: [15] + supported versions: [15, 16] - name: Debian 11 arch: x86_64 - supported versions: [15] + supported versions: [15, 16] - name: Ubuntu 18.04 arch: x86_64 - supported versions: [15] + supported versions: [15, 16] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [15] + supported versions: [15, 16] - name: Ubuntu 22.04 arch: x86_64 - supported versions: [15] + supported versions: [15, 16] - name: SLES 12 arch: x86_64 - supported versions: [15] + supported versions: [15, 16] - name: SLES 12 arch: ppc64le - supported versions: [15] + supported versions: [15, 16] - name: SLES 15 arch: x86_64 - supported versions: [15] + supported versions: [15, 16] - name: SLES 15 arch: ppc64le - supported versions: [15] + supported versions: [15, 16] - name: Replication Server platforms: - name: CentOS 7 diff --git a/install_template/templates/products/failover-manager/base.njk b/install_template/templates/products/failover-manager/base.njk index 3d8dc4d8cd7..7c8193e0626 100644 --- a/install_template/templates/products/failover-manager/base.njk +++ b/install_template/templates/products/failover-manager/base.njk @@ -15,7 +15,7 @@ redirects: {% block product_prerequisites %} - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) {{ super() }} 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 6bce2400b34..36c9f4759b9 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/base.njk @@ -43,7 +43,7 @@ redirects: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. diff --git a/install_template/templates/products/postgresql/index.njk b/install_template/templates/products/postgresql/index.njk index 56934d03067..cc92b9bcd4d 100644 --- a/install_template/templates/products/postgresql/index.njk +++ b/install_template/templates/products/postgresql/index.njk @@ -9,6 +9,8 @@ title: Installing {{ product.name }} {% block frontmatter %} deployPath: advocacy_docs/supported-open-source/postgresql/installing/index.mdx indexCards: none +redirects: +- /supported-open-source/postgresql/installer {% endblock frontmatter %} {% block navigation %} - requirements diff --git a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx index d11fe0dd5a3..6d2a8cc8e26 100644 --- a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx +++ b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx @@ -8,7 +8,7 @@ When you create a distributed high-availability cluster, you need to set up the 1. On the **Nodes Settings** tab, in the **Nodes** section, select **Two Data Nodes** or **Three Data Nodes**. - For more information on node architecture, see [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability). + For more information on node architecture, see [Distributed high availability](../../overview/02_high_availability/distributed_highavailability/). 1. In the **Database Type** section: @@ -39,7 +39,7 @@ After creating the first data group, you can create a second data group for your By default, the settings for your first data group populate the second data group's settings. However, if you want to change certain settings you can. Just know that your changes can change the settings for the entire cluster. That being said, the database type and cloud provider must be consistent across both data groups. The data groups and the witness group must all be in different regions. Otherwise, you can choose the second data group's settings as needed. -When choosing the number of data nodes for the second data group, see [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) for information on node architecture. +When choosing the number of data nodes for the second data group, see [Distributed high availability](../../overview/02_high_availability/distributed_highavailability/) for information on node architecture. !!! Note To maintain high availability, BigAnimal doesn't allow the maintenance windows of data groups to overlap. \ No newline at end of file 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 7e0eed4ce38..36f876bf51f 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 @@ -39,11 +39,11 @@ The following options aren't available when creating your cluster: 1. Select the type of cluster to deploy. - - [Single Node](/biganimal/latest/overview/02_high_availability/#single-node) creates a cluster with one primary and no standby replicas. Suited for test environments where high availability might not be required. You can create single-node clusters running PostgreSQL or EDB Postgres Advanced Server. + - [Single Node](../../overview/02_high_availability/single_node/) creates a cluster with one primary and no standby replicas. Suited for test environments where high availability might not be required. You can create single-node clusters running PostgreSQL or EDB Postgres Advanced Server. - - [Primary/Standby High Availability](/biganimal/latest/overview/02_high_availability/#primarystandby-high-availability) creates a cluster with one primary and one or two standby replicas in different availability zones. You can create primary/standby high-availability clusters running PostgreSQL or EDB Postgres Advanced Server. Only primary/standby high-availability clusters allow you to enable read-only workloads for users. However, if you enable read-only workloads, then you might have to raise the IP address resource limits for the cluster. + - [Primary/Standby High Availability](../../overview/02_high_availability/primary_standby_highavailability/) creates a cluster with one primary and one or two standby replicas in different availability zones. You can create primary/standby high-availability clusters running PostgreSQL or EDB Postgres Advanced Server. Only primary/standby high-availability clusters allow you to enable read-only workloads for users. However, if you enable read-only workloads, then you might have to raise the IP address resource limits for the cluster. - - [Distributed High Availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) creates a cluster, powered by EDB Postgres Distributed, with up to two data groups spread across multiple cloud regions to deliver higher performance and faster recovery. See [Creating a distributed high-availability cluster](creating_an_eha_cluster) for instructions. + - [Distributed High Availability](../../overview/02_high_availability/distributed_highavailability/) creates a cluster, powered by EDB Postgres Distributed, with up to two data groups spread across multiple cloud regions to deliver higher performance and faster recovery. See [Creating a distributed high-availability cluster](creating_an_eha_cluster) for instructions. See [Supported cluster types](/biganimal/latest/overview/02_high_availability/) for more information about the different cluster types. @@ -179,7 +179,7 @@ When enabling read-only workloads, keep in mind the following: - Advisory locks aren't replicated between Postgres nodes, so advisory locks taken on a standby replica don't conflict with advisory locks taken on the primary or another standby replica. We recommend that applications that rely on advisory locking avoid using read-only workloads for those transactions. -For information on replication lag while using read-only workloads, see [Standby replicas](/biganimal/latest/overview/02_high_availability/#standby-replicas). +For information on replication lag while using read-only workloads, see [Standby replicas](/biganimal/latest/overview/02_high_availability/primary_standby_highavailability/#standby-replicas). #### PgBouncer diff --git a/product_docs/docs/biganimal/release/migration/index.mdx b/product_docs/docs/biganimal/release/migration/index.mdx index 89629048058..27a03c742be 100644 --- a/product_docs/docs/biganimal/release/migration/index.mdx +++ b/product_docs/docs/biganimal/release/migration/index.mdx @@ -19,7 +19,7 @@ You can also use the [Migration Toolkit](/migration_toolkit/latest/) for the dat ## Accessing remote Oracle servers from BigAnimal -BigAnimal supports the [edb_dblink_oci](/epas/latest/epas_compat_sql/21_create_public_database_link/#setting-up-an-oracle-instant-client-for-oci-database-link) extension and a set of [dblink_ora](/epas/latest/epas_compat_ora_dev_guide/06_dblink_ora/) functions, which you can use to create Oracle syntax-compatible database links and include calls to functions that are only available in Oracle, respectively. +BigAnimal supports the [edb_dblink_oci](/epas/latest/reference/oracle_compatibility_reference/epas_compat_sql/21_create_public_database_link/) extension and a set of [dblink_ora](/epas/latest/working_with_oracle_data/06_dblink_ora/) functions, which you can use to create Oracle syntax-compatible database links and include calls to functions that are only available in Oracle, respectively. See the following BigAnimal knowlege base articles for step-by-step instructions for creating links to remote Oracle servers from EDB Postgres Advanced Server clusters: diff --git a/product_docs/docs/biganimal/release/overview/02_high_availability/distributed_highavailability.mdx b/product_docs/docs/biganimal/release/overview/02_high_availability/distributed_highavailability.mdx index 72fc2320289..5e06ba49951 100644 --- a/product_docs/docs/biganimal/release/overview/02_high_availability/distributed_highavailability.mdx +++ b/product_docs/docs/biganimal/release/overview/02_high_availability/distributed_highavailability.mdx @@ -59,6 +59,6 @@ Cross-cloud service provider witness nodes are available with AWS, Azure, and Go ## 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/). +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/). For instructions on creating, retrieving information from, and managing a distributed high-availability cluster using the BigAnimal CLI, see [Using the BigAnimal CLI](/biganimal/latest/reference/cli/managing_clusters/#managing-distributed-high-availability-clusters). diff --git a/product_docs/docs/biganimal/release/planning/choosing_cluster_type.mdx b/product_docs/docs/biganimal/release/planning/choosing_cluster_type.mdx index 3fd76d7e8db..9eb55f62aab 100644 --- a/product_docs/docs/biganimal/release/planning/choosing_cluster_type.mdx +++ b/product_docs/docs/biganimal/release/planning/choosing_cluster_type.mdx @@ -7,7 +7,7 @@ Choose the cluster type and configuration that meets your availability requireme 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) | +| Consideration | [Single node](../overview/02_high_availability/single_node/) | [Primary/Standby HA](../overview/02_high_availability/primary_standby_highavailability/) | [HA + standby replica](../overview/02_high_availability/primary_standby_highavailability/#standby-replicas) | [Distributed HA single region](../overview/02_high_availability/distributed_highavailability/#single-data-location) | [Distributed HA multi-region](../overview/02_high_availability/distributed_highavailability/#multiple-data-locations-and-witness-node) | | ------------------------ | --------------------------- | ------------------------------------------------------ | ----------------------------------------- | ----------------------------------------------------- | -------------------------------------------------------------- | | Data replication | None | Physical | Physical | Logical | Logical | | Region | Single | Single | Multi | Single | Multi | diff --git a/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/05_db_configuration_parameters.mdx b/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/05_db_configuration_parameters.mdx index 0b955e3c64a..bd92f248948 100644 --- a/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/05_db_configuration_parameters.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/05_db_configuration_parameters.mdx @@ -9,7 +9,7 @@ The list of parameters is populated based on the type of database you selected o - For PostgreSQL parameters, see [Setting Parameters](https://www.postgresql.org/docs/current/config-setting.html) and [Server Configuration](https://www.postgresql.org/docs/current/runtime-config.html) in the Postgres documentation. -- For EDB Postgres Advanced Server, see [Summary of configuration parameters](/epas/latest/epas_guide/03_database_administration/01_configuration_parameters/02_summary_of_configuration_parameters/#summary_of_configuration_parameters) and [Configuration parameters](/epas/latest/epas_guide/03_database_administration/01_configuration_parameters/). +- For EDB Postgres Advanced Server, see [Summary of configuration parameters](/epas/latest/reference/database_administrator_reference/02_summary_of_configuration_parameters/) and [Configuration parameters](/epas/latest/database_administration/01_configuration_parameters/). - For more information on the types of values parameters accept, see [Parameter Names and Values](https://www.postgresql.org/docs/current/config-setting.html#CONFIG-SETTING-NAMES-VALUES). The types apply to both PostgreSQL and EDB Postgres Advanced Server parameters. diff --git a/product_docs/docs/biganimal/release/using_cluster/04_backup_and_restore.mdx b/product_docs/docs/biganimal/release/using_cluster/04_backup_and_restore.mdx index 57313f0d4da..973251f665a 100644 --- a/product_docs/docs/biganimal/release/using_cluster/04_backup_and_restore.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/04_backup_and_restore.mdx @@ -54,6 +54,6 @@ The restore operation is available for any cluster that has at least one availab 1. Select **Next: Data Group**. 1. Select the **Node Settings** tab. 1. In the **Source** section, select **Fully Restore** or **Point in Time Restore**. A point-in-time restore restores the data group as it was at the specified date and time. -1. In the **Nodes** section, select **Two Data Nodes** or **Three Data Nodes**. For more information on node architecture, see [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability). +1. In the **Nodes** section, select **Two Data Nodes** or **Three Data Nodes**. For more information on node architecture, see [Distributed high availability](/biganimal/latest/overview/02_high_availability/distributed_highavailability/). 1. Follow Steps 3-5 in [Creating a distributed high-availability cluster](../getting_started/creating_a_cluster/creating_an_eha_cluster/). 1. Select **Restore**. diff --git a/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/metrics/index.mdx b/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/metrics/index.mdx index 32ee7c392e3..5f558346286 100644 --- a/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/metrics/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/metrics/index.mdx @@ -444,8 +444,8 @@ The metrics in this group can have these labels: Metrics based on the bdr.node_replication_rates monitoring catalog for monitoring BDR replication performance and replication lag. See -[Monitoring Outgoing Replication](/pgd/latest/monitoring/#monitoring-outgoing-replication) -and [`bdr.node_replication_rates`](/pgd/latest/bdr/catalogs/#bdrnode_replication_rates) +[Monitoring Outgoing Replication](/pgd/latest/monitoring/sql/#monitoring-outgoing-replication) +and [`bdr.node_replication_rates`](/pgd/4/bdr/catalogs/#bdrnode_replication_rates) | Metric | Usage | Description | |----------|-------|-------------| diff --git a/product_docs/docs/biganimal/release/using_cluster/06_demonstration_oracle_compatibility.mdx b/product_docs/docs/biganimal/release/using_cluster/06_demonstration_oracle_compatibility.mdx index 01d21b6b972..ecf404f9ffc 100644 --- a/product_docs/docs/biganimal/release/using_cluster/06_demonstration_oracle_compatibility.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/06_demonstration_oracle_compatibility.mdx @@ -4,7 +4,7 @@ navTitle: "Oracle SQL compatibility" showInteractiveBadge: true --- -BigAnimal lets you run Oracle SQL queries in the cloud using [EDB Postgres Advanced Server](/epas/latest/epas_compat_ora_dev_guide/). This demonstration shows two Oracle SQL-syntax queries running unmodified on a BigAnimal test cluster, populated with the [Chinook sample database](https://github.com/lerocha/chinook-database). +BigAnimal lets you run Oracle SQL queries in the cloud using [EDB Postgres Advanced Server](/epas/latest/fundamentals/epas_fundamentals/epas_compat_ora_dev_guide/). This demonstration shows two Oracle SQL-syntax queries running unmodified on a BigAnimal test cluster, populated with the [Chinook sample database](https://github.com/lerocha/chinook-database). Watch the video, or load up psql and follow along. @@ -123,7 +123,7 @@ This table has a `reportsto` field. That means this is a hierarchical reporting ## Demo #1: Exposing an organization hierarchy with `CONNECT BY` -Construct a [hierarchical query](https://www.enterprisedb.com/docs/epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/05_hierarchical_queries/) to expose this [chain of command](https://en.wikipedia.org/wiki/Chain_of_command). +Construct a [hierarchical query](/epas/latest/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/) to expose this [chain of command](https://en.wikipedia.org/wiki/Chain_of_command). Modern SQL can use a recursive CTE for this, as those are widely supported. But Oracle has, for decades, supported an alternative mechanism for querying hierarchy in the form of `CONNECT BY`, as shown in the following: @@ -230,7 +230,7 @@ LINE 3: string_agg(t.name || ' (' || ROUND(bytes/1048576) || ... HINT: No function matches the given name and argument types. You might need to add explicit type casts. ``` -This isn't difficult to correct, but it requires restructuring the query to replace the grouping construct. Such work can quickly accumulate errors. Fortunately, [EDB Postgres Advanced Server](https://www.enterprisedb.com/docs/epas/latest/) supports [`LISTAGG`](https://www.enterprisedb.com/docs/epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/11_aggregate_functions/#listagg) in addition to `string_agg`, +This isn't difficult to correct, but it requires restructuring the query to replace the grouping construct. Such work can quickly accumulate errors. Fortunately, [EDB Postgres Advanced Server](/epas/latest/) supports [`LISTAGG`](/epas/latest/reference/sql_reference/03_functions_and_operators/11_aggregate_functions/#listagg) in addition to `string_agg`, so this query doesn't need to change when migrating from Oracle. ## Compatibility preserves the value of your existing work diff --git a/product_docs/docs/edb_plus/41/installing/windows.mdx b/product_docs/docs/edb_plus/41/installing/windows.mdx index c613b7fba69..0ee5c919937 100644 --- a/product_docs/docs/edb_plus/41/installing/windows.mdx +++ b/product_docs/docs/edb_plus/41/installing/windows.mdx @@ -14,7 +14,7 @@ Before installing EDB\*Plus, you must first install Java version 1.8 or later. F ## Using StackBuilder Plus -After installing EDB Postgres Advanced Server, you can use StackBuilder Plus to invoke the graphical installer for EDB\*Plus. See [Using StackBuilder Plus](/epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). +After installing EDB Postgres Advanced Server, you can use StackBuilder Plus to invoke the graphical installer for EDB\*Plus. See [Using StackBuilder Plus](/epas/latest/installing/windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). 1. Using the Windows Start menu, open StackBuilder Plus. Follow the prompts until you get to the module selection page. 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 aa8338803ae..d1602cc7066 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -54,13 +54,13 @@ Before you begin the installation process: sudo dnf -y install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 69a4ac393d5..ed0ece9b2bf 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -54,13 +54,13 @@ Before you begin the installation process: sudo dnf -y install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 10e013007cf..74840dd8770 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -56,13 +56,13 @@ Before you begin the installation process: sudo zypper -n install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 d913753f7d8..199186cfe22 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -57,13 +57,13 @@ Before you begin the installation process: sudo zypper -n install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 0e606cc6c3b..31fe49043ff 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -50,13 +50,13 @@ Before you begin the installation process: sudo yum -y install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 4823af7fe01..cf500ec96f9 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -45,13 +45,13 @@ Before you begin the installation process: sudo apt-get -y install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 aed926c23cc..a431749216e 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -45,13 +45,13 @@ Before you begin the installation process: sudo apt-get -y install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 7d413d9584a..e4a73d25b15 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -56,13 +56,13 @@ Before you begin the installation process: sudo dnf -y install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 57b907d622d..ddde064109e 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -56,13 +56,13 @@ Before you begin the installation process: sudo dnf -y install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 97b91e3d00c..3ef87885143 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -56,13 +56,13 @@ Before you begin the installation process: sudo yum -y install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 8f7bbed1b19..2baa7389869 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -50,13 +50,13 @@ Before you begin the installation process: sudo dnf -y install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 8367e274bcd..cbb72595b33 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -50,13 +50,13 @@ Before you begin the installation process: sudo dnf -y install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 0ae8a903ac9..a7b8213e8c1 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -56,13 +56,13 @@ Before you begin the installation process: sudo zypper -n install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 cfc27aade83..ec27c1fc08d 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -57,13 +57,13 @@ Before you begin the installation process: sudo zypper -n install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 7ac3915948b..88167dd624d 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -45,13 +45,13 @@ Before you begin the installation process: sudo apt-get -y install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 39c512770de..42c52a4ac0c 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -45,13 +45,13 @@ Before you begin the installation process: sudo apt-get -y install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: 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 1c0323cc738..fbc4baa92e6 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 @@ -15,7 +15,7 @@ Before you begin the installation process: - Install Postgres on the same host (not needed for witness nodes). - - See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux) + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) - See [PostgreSQL Downloads](https://www.postgresql.org/download/) @@ -45,13 +45,13 @@ Before you begin the installation process: sudo apt-get -y install edb-efm<4x> ``` -Where `<4x>` is the version of Failover Manager that you are installing. For example, if you are installing version 4.8, the package name would be `edb-efm48`. +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.8, the package name is `edb-efm48`. The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. ## Initial configuration -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). After installing on each node of the cluster: diff --git a/product_docs/docs/epas/11/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx b/product_docs/docs/epas/11/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx index 77241f48ada..94a9a9ffa14 100644 --- a/product_docs/docs/epas/11/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx +++ b/product_docs/docs/epas/11/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx @@ -15,4 +15,4 @@ 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 EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/). +For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/11/epas_compat_tools_guide/). diff --git a/product_docs/docs/epas/11/epas_compat_ora_dev_guide/index.mdx b/product_docs/docs/epas/11/epas_compat_ora_dev_guide/index.mdx index fec6bfb39a3..bcf39978790 100644 --- a/product_docs/docs/epas/11/epas_compat_ora_dev_guide/index.mdx +++ b/product_docs/docs/epas/11/epas_compat_ora_dev_guide/index.mdx @@ -17,10 +17,10 @@ Database Compatibility for Oracle means that an application runs in an Oracle en - SQL statements that are compatible with Oracle SQL - System catalog views that are compatible with Oracle’s data dictionary -For detailed information about the compatible SQL syntax, data types, and views, see [SQL reference](/epas/latest/epas_compat_sql/). +For detailed information about the compatible SQL syntax, data types, and views, see [SQL reference](../epas_compat_sql/). -The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Built-in packages](/epas/latest/epas_compat_bip_guide/). +The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Built-in packages](../epas_compat_bip_guide/). -For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools, utilities, and components](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/). +For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools, utilities, and components](../epas_compat_ora_dev_guide/09_tools_and_utilities/). 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 [EDB OCL Connector](/ocl_connector/latest/). diff --git a/product_docs/docs/epas/11/epas_compat_sql/21_create_public_database_link.mdx b/product_docs/docs/epas/11/epas_compat_sql/21_create_public_database_link.mdx index 53ecbdebd04..e8e17939ac1 100644 --- a/product_docs/docs/epas/11/epas_compat_sql/21_create_public_database_link.mdx +++ b/product_docs/docs/epas/11/epas_compat_sql/21_create_public_database_link.mdx @@ -133,7 +133,7 @@ export LD_LIBRARY_PATH=/tmp/instantclient:$LD_LIBRARY_PATH Alternatively, you can also set the value of the `oracle_home` configuration parameter in the `postgresql.conf` file. So, the `oracle_home` configuration parameter is an alternative to the `LD_LIBRARY_PATH` environment variable. For more details on the `oracle_home` configuration -parameter, see [configuration paramters](/epas/latest/epas_compat_ora_dev_guide/01_introduction/05_oracle_home/). +parameter, see [configuration paramters](../epas_compat_ora_dev_guide/01_introduction/05_oracle_home/). The `ORACLE_HOME` environment variable is must to be set and should include the path to the Oracle home directory. For example, diff --git a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx b/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx index 876c83ca452..0b0941c4bc8 100644 --- a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx +++ b/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx @@ -47,9 +47,7 @@ The process for implementing Virtual Private Database is as follows: - Use the `ENABLE_POLICY` procedure to disable or enable an existing policy. - Use the `DROP_POLICY` procedure to remove an existing policy. The `DROP_POLICY` procedure does not drop the policy function or the associated database object. -Once policies are created, they can be viewed in the catalog views, compatible with Oracle databases: `ALL_POLICIES, DBA_POLICIES`, or `USER_POLICIES`. The supported compatible views are listed in the *Database Compatibility for Oracle Developers Catalog Views Guide*, available at the EDB website at: - -[https://www.enterprisedb.com/docs/](/epas/latest/epas_compat_cat_views/) +Once policies are created, they can be viewed in the catalog views, compatible with Oracle databases: `ALL_POLICIES, DBA_POLICIES`, or `USER_POLICIES`. The supported compatible views are listed in [Database Compatibility for Oracle Developers Catalog Views Guide](../../epas_compat_cat_views/). The `SYS_CONTEXT` function is often used with `DBMS_RLS`. The signature is: diff --git a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/index.mdx b/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/index.mdx index 8f94a37acc4..187b4383c8d 100644 --- a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/index.mdx +++ b/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/index.mdx @@ -8,9 +8,7 @@ legacyRedirectsGenerated: This chapter describes the built-in packages that are provided with Advanced Server. For certain packages, non-superusers must be explicitly granted the `EXECUTE` privilege on the package before using any of the package’s functions or procedures. For most of the built-in packages, `EXECUTE` privilege has been granted to `PUBLIC` by default. -For information about using the `GRANT` command to provide access to a package, see the *Database Compatibility for Oracle Developers SQL Guide*, available at: - -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_sql/) +For information about using the `GRANT` command to provide access to a package, see [`GRANT`](../../epas_compat_sql/64_grant/). All built-in packages are owned by the special `sys` user which must be specified when granting or revoking privileges on built-in packages: diff --git a/product_docs/docs/epas/12/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx b/product_docs/docs/epas/12/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx index a4fc8aaf53a..5d0641b46c2 100644 --- a/product_docs/docs/epas/12/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx +++ b/product_docs/docs/epas/12/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx @@ -15,4 +15,4 @@ 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 EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/). +For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/12/epas_compat_tools_guide/). diff --git a/product_docs/docs/epas/12/epas_compat_ora_dev_guide/index.mdx b/product_docs/docs/epas/12/epas_compat_ora_dev_guide/index.mdx index fefbc3d4d11..e84ecc9ad92 100644 --- a/product_docs/docs/epas/12/epas_compat_ora_dev_guide/index.mdx +++ b/product_docs/docs/epas/12/epas_compat_ora_dev_guide/index.mdx @@ -17,10 +17,10 @@ Database Compatibility for Oracle means that an application runs in an Oracle en - SQL statements that are compatible with Oracle SQL - System catalog views that are compatible with Oracle’s data dictionary -For detailed information about the compatible SQL syntax, data types, and views, see [SQL reference](/epas/latest/epas_compat_sql/). +For detailed information about the compatible SQL syntax, data types, and views, see [SQL reference](../epas_compat_sql/). -The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Built-in packages](/epas/latest/epas_compat_bip_guide/). +The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Built-in packages](../epas_compat_bip_guide/). -For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools, utilities, and components](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/). +For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools, utilities, and components](../epas_compat_ora_dev_guide/09_tools_and_utilities/). -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*. +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 [EDB OCL Connector](/ocl_connector/latest/). diff --git a/product_docs/docs/epas/12/epas_compat_spl/14_packages.mdx b/product_docs/docs/epas/12/epas_compat_spl/14_packages.mdx index 1c39ee6c899..8a303ab6517 100644 --- a/product_docs/docs/epas/12/epas_compat_spl/14_packages.mdx +++ b/product_docs/docs/epas/12/epas_compat_spl/14_packages.mdx @@ -19,6 +19,6 @@ A *package* is a named collection of functions, procedures, variables, cursors, For more information about the package support provided by Advanced Server, see the *Database Compatibility for Oracle Developers Built-in Package Guide*, available at: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_bip_guide/) +[https://www.enterprisedb.com/docs](../epas_compat_bip_guide/) For a list of built-in packages, see the Table of Contents, of "Built-In Packages" of the *Database Compatibility for Oracle Developers Built-in Package Guide*. diff --git a/product_docs/docs/epas/12/epas_compat_sql/21_create_public_database_link.mdx b/product_docs/docs/epas/12/epas_compat_sql/21_create_public_database_link.mdx index 4b79ac7d7ce..ae6068b243c 100644 --- a/product_docs/docs/epas/12/epas_compat_sql/21_create_public_database_link.mdx +++ b/product_docs/docs/epas/12/epas_compat_sql/21_create_public_database_link.mdx @@ -135,7 +135,7 @@ export LD_LIBRARY_PATH=/tmp/instantclient:$LD_LIBRARY_PATH Alternatively, you can also set the value of the `oracle_home` configuration parameter in the `postgresql.conf` file. So, the `oracle_home` configuration parameter is an alternative to the `LD_LIBRARY_PATH` environment variable. For more details on the `oracle_home` configuration -parameter, see [configuration paramters](/epas/latest/epas_compat_ora_dev_guide/01_introduction/05_oracle_home/). +parameter, see [configuration paramters](../epas_compat_ora_dev_guide/01_introduction/05_oracle_home/). The `ORACLE_HOME` environment variable is must to be set and should include the path to the Oracle home directory. For example, diff --git a/product_docs/docs/epas/12/epas_guide/02_enhanced_compatibility_features.mdx b/product_docs/docs/epas/12/epas_guide/02_enhanced_compatibility_features.mdx index 7627995a3a2..993234e89dc 100644 --- a/product_docs/docs/epas/12/epas_guide/02_enhanced_compatibility_features.mdx +++ b/product_docs/docs/epas/12/epas_guide/02_enhanced_compatibility_features.mdx @@ -20,7 +20,7 @@ legacyRedirectsGenerated: 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/) +[https://www.enterprisedb.com/docs](/epas/12/epas_compat_ora_dev_guide/) The following sections highlight some of the compatibility features supported by Advanced Server. @@ -45,7 +45,7 @@ Advanced Server supports a highly productive procedural language that allows you For information about using the Stored Procedural Language, see the *Database Compatibility for Stored Procedural Language Guide*, available at: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_spl/) +[https://www.enterprisedb.com/docs](/epas/12/epas_compat_spl/) ## Optimizer Hints @@ -59,19 +59,17 @@ As a rule, the query planner will select the least expensive plan. You can use a An optimizer hint is a directive (or multiple directives) embedded in a comment-like syntax that immediately follows a `DELETE`, `INSERT`, `SELECT` or `UPDATE` command. Keywords in the comment instruct the server to employ or avoid a specific plan when producing the result set. For information about using optimizer hints, see the *Database Compatibility for Oracle Developers Guide*, available at: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_ora_dev_guide/) +[https://www.enterprisedb.com/docs](/epas/12/epas_compat_ora_dev_guide/) ## Data Dictionary Views -Advanced Server includes a set of views that provide information about database objects in a manner compatible with the Oracle data dictionary views. For detailed information about the views available with Advanced Server, see the *Database Compatibility for Oracle Developers Catalog Views Guide*, available at: - -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_cat_views/) +Advanced Server includes a set of views that provide information about database objects in a manner compatible with the Oracle data dictionary views. For detailed information about the views available with Advanced Server, see [Database Compatibility for Oracle Developers Catalog Views Guide](../epas_compat_cat_views/). ## dblink_ora dblink_ora provides an OCI-based database link that allows you to `SELECT, INSERT, UPDATE` or `DELETE` data stored on an Oracle system from within Advanced Server. For detailed information about using `dblink_ora`, and the supported functions and procedures, see the *Database Compatibility for Oracle Developers Guide*, available at: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_ora_dev_guide/) +[https://www.enterprisedb.com/docs](/epas/12/epas_compat_ora_dev_guide/) ## Profile Management @@ -90,7 +88,7 @@ After creating the profile, you can associate the profile with one or more users For information about using profile management commands, see the *Database Compatibility for Oracle Developers Guide*, available at: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_ora_dev_guide/) +[https://www.enterprisedb.com/docs](/epas/12/epas_compat_ora_dev_guide/) ## Built-In Packages @@ -126,7 +124,7 @@ Advanced Server supports a number of built-in packages that provide compatibilit For detailed information about the procedures and functions available within each package, see the *Database Compatibility for Oracle Developers Built-In Package Guide*, available at: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_bip_guide/) +[https://www.enterprisedb.com/docs](../epas_compat_bip_guide/) ## Open Client Library @@ -144,7 +142,7 @@ For detailed information about the functions supported by the Open Client Librar 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/) +[https://www.enterprisedb.com/docs](/epas/12/epas_compat_tools_guide/) **EDB\*Plus** @@ -202,7 +200,7 @@ ECPGPlus supports Pro\*C syntax in C programs when connected to an Advanced Serv For information about using ECPGPlus, see the *EDB Postgres Advanced Server ECPG Connector Guide*, available from the EnterpriseDB website at: -[https://www.enterprisedb.com/docs](/epas/latest/ecpgplus_guide/) +[https://www.enterprisedb.com/docs](/epas/12/ecpgplus_guide/) ## Table Partitioning @@ -217,4 +215,4 @@ Table partitioning is worthwhile only when a table would otherwise be very large For information about database compatibility features supported by Advanced Server see the *Database Compatibility Table Partitioning Guide*, available at: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_table_partitioning/) +[https://www.enterprisedb.com/docs](/epas/12/epas_compat_table_partitioning/) diff --git a/product_docs/docs/epas/12/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx b/product_docs/docs/epas/12/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx index 9ff25b760f2..666cb412180 100644 --- a/product_docs/docs/epas/12/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx +++ b/product_docs/docs/epas/12/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx @@ -343,7 +343,7 @@ Use the `edbldr.empty_csv_field` parameter to specify how EDB\*Loader will treat For more information about the `edbldr.empty_csv_field` parameter in EDB\*Loader, see the *Database Compatibility for Oracle Developers Tools and Utilities Guide* at the EnterpriseDB website: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_tools_guide/) +[https://www.enterprisedb.com/docs](/epas/12/epas_compat_tools_guide/) ## utl_encode.uudecode_redwood diff --git a/product_docs/docs/epas/12/epas_guide/14_edb_clone_schema.mdx b/product_docs/docs/epas/12/epas_guide/14_edb_clone_schema.mdx index c4b99388646..f3be714d457 100644 --- a/product_docs/docs/epas/12/epas_guide/14_edb_clone_schema.mdx +++ b/product_docs/docs/epas/12/epas_guide/14_edb_clone_schema.mdx @@ -111,7 +111,7 @@ shared_preload_libraries = '$libdir/dbms_pipe,$libdir/dbms_aq,$libdir/parallel_c **Step 3:** The Perl Procedural Language (PL/Perl) must be installed on the database and the `CREATE TRUSTED LANGUAGE plperl` command must be run. For Linux, install PL/Perl using the `edb-asxx-server-plperl` RPM package where `xx` is the Advanced Server version number. For Windows, use the EDB Postgres Language Pack. For information on EDB Language Pack, see the *EDB Postgres Language Pack Guide* available at: -[https://www.enterprisedb.com/docs](/epas/latest/language_pack/) +[https://www.enterprisedb.com/docs](/language_pack/latest/) **Step 4:** Connect to the database as a superuser and run the following command: diff --git a/product_docs/docs/epas/12/installing/images/accessing_configuration_files.png b/product_docs/docs/epas/12/installing/images/accessing_configuration_files.png new file mode 100755 index 00000000000..9960bbc4711 --- /dev/null +++ b/product_docs/docs/epas/12/installing/images/accessing_configuration_files.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3757b0d5a882ffcb915dde0530131e2c1d1dab3871d9cb681340b475adeae5f +size 161329 diff --git a/product_docs/docs/epas/12/installing/windows/installing_advanced_server/01_performing_a_graphical_installation_on_windows.mdx b/product_docs/docs/epas/12/installing/windows/installing_advanced_server/01_performing_a_graphical_installation_on_windows.mdx index 465f6a60093..7485aac1b72 100644 --- a/product_docs/docs/epas/12/installing/windows/installing_advanced_server/01_performing_a_graphical_installation_on_windows.mdx +++ b/product_docs/docs/epas/12/installing/windows/installing_advanced_server/01_performing_a_graphical_installation_on_windows.mdx @@ -161,7 +161,7 @@ If you select `Compatible with Oracle`, the installation will include the follow 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/) +[https://www.enterprisedb.com/docs](../../../epas_compat_bip_guide/) If you choose to install in `Compatible with Oracle` mode, the Advanced Server superuser name is `enterprisedb`. diff --git a/product_docs/docs/epas/12/installing/windows_install_details/06_configuring_advanced_server/index.mdx b/product_docs/docs/epas/12/installing/windows_install_details/06_configuring_advanced_server/index.mdx index d223af6e75d..6309041605f 100644 --- a/product_docs/docs/epas/12/installing/windows_install_details/06_configuring_advanced_server/index.mdx +++ b/product_docs/docs/epas/12/installing/windows_install_details/06_configuring_advanced_server/index.mdx @@ -21,7 +21,7 @@ For more information about Modifying the postgresql.conf file and Modifying the You can use your editor of choice to open a configuration file, or on Windows navigate through the `EDB Postgres` menu to open a file. -![Accessing the configuration files through the Windows system menu](../images/accessing_configuration_files.png) +![Accessing the configuration files through the Windows system menu](../../images/accessing_configuration_files.png)
Fig. 1: Accessing the configuration files through the Windows system menu
diff --git a/product_docs/docs/epas/13/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx b/product_docs/docs/epas/13/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx index da19a30e9eb..58915a3ab48 100644 --- a/product_docs/docs/epas/13/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx +++ b/product_docs/docs/epas/13/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx @@ -47,9 +47,7 @@ The process for implementing Virtual Private Database is as follows: - Use the `ENABLE_POLICY` procedure to disable or enable an existing policy. - Use the `DROP_POLICY` procedure to remove an existing policy. The `DROP_POLICY` procedure does not drop the policy function or the associated database object. -Once policies are created, they can be viewed in the catalog views, compatible with Oracle databases: `ALL_POLICIES, DBA_POLICIES`, or `USER_POLICIES`. The supported compatible views are listed in the *Database Compatibility for Oracle Developers Catalog Views Guide*, available at the EDB website at: - -[https://www.enterprisedb.com/docs/](/epas/latest/epas_compat_cat_views/) +Once policies are created, they can be viewed in the catalog views, compatible with Oracle databases: `ALL_POLICIES, DBA_POLICIES`, or `USER_POLICIES`. The supported compatible views are listed in [Database Compatibility for Oracle Developers Catalog Views Guide](../../epas_compat_cat_views/). The `SYS_CONTEXT` function is often used with `DBMS_RLS`. The signature is: diff --git a/product_docs/docs/epas/13/epas_compat_bip_guide/03_built-in_packages/index.mdx b/product_docs/docs/epas/13/epas_compat_bip_guide/03_built-in_packages/index.mdx index e6822147e10..486d534666e 100644 --- a/product_docs/docs/epas/13/epas_compat_bip_guide/03_built-in_packages/index.mdx +++ b/product_docs/docs/epas/13/epas_compat_bip_guide/03_built-in_packages/index.mdx @@ -8,9 +8,7 @@ legacyRedirectsGenerated: This chapter describes the built-in packages that are provided with Advanced Server. For certain packages, non-superusers must be explicitly granted the `EXECUTE` privilege on the package before using any of the package’s functions or procedures. For most of the built-in packages, `EXECUTE` privilege has been granted to `PUBLIC` by default. -For information about using the `GRANT` command to provide access to a package, see the *Database Compatibility for Oracle Developers SQL Guide*, available at: - -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_sql/) +For information about using the `GRANT` command to provide access to a package, see [`GRANT`](../../epas_compat_sql/64_grant/). All built-in packages are owned by the special `sys` user which must be specified when granting or revoking privileges on built-in packages: 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 811bd191eac..832b6fecf3e 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,4 +15,4 @@ 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 EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/). +For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/13/epas_compat_tools_guide/). 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 d1979de07f4..009f62d2a10 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 @@ -19,10 +19,10 @@ Database Compatibility for Oracle means that an application runs in an Oracle en - SQL statements that are compatible with Oracle SQL - System catalog views that are compatible with Oracle’s data dictionary -For detailed information about the compatible SQL syntax, data types, and views, see the [SQL reference](/epas/latest/epas_compat_sql/). +For detailed information about the compatible SQL syntax, data types, and views, see [SQL reference](../epas_compat_sql/). -The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Built-in packages](/epas/latest/epas_compat_bip_guide/). +The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Built-in packages](../epas_compat_bip_guide/). -For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools and utilities](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/). +For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools, utilities, and components](../epas_compat_ora_dev_guide/09_tools_and_utilities/). 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 [EDB OCL Connector](/ocl_connector/latest/). diff --git a/product_docs/docs/epas/13/epas_compat_spl/14_packages.mdx b/product_docs/docs/epas/13/epas_compat_spl/14_packages.mdx index 5280c9cadea..c28845dc03a 100644 --- a/product_docs/docs/epas/13/epas_compat_spl/14_packages.mdx +++ b/product_docs/docs/epas/13/epas_compat_spl/14_packages.mdx @@ -19,6 +19,6 @@ A *package* is a named collection of functions, procedures, variables, cursors, For more information about the package support provided by Advanced Server, see the *Database Compatibility for Oracle Developers Built-in Package Guide*, available at: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_bip_guide/) +[https://www.enterprisedb.com/docs](../epas_compat_bip_guide/) For a list of built-in packages, see the Table of Contents, of "Built-In Packages" of the *Database Compatibility for Oracle Developers Built-in Package Guide*. 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 f6b26959846..73420446533 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 @@ -134,7 +134,7 @@ export LD_LIBRARY_PATH=/tmp/instantclient:$LD_LIBRARY_PATH Alternatively, you can also set the value of the `oracle_home` configuration parameter in the `postgresql.conf` file. So, the `oracle_home` configuration parameter is an alternative to the `LD_LIBRARY_PATH` environment variable. For more details on the `oracle_home` configuration -parameter, see [configuration paramters](/epas/latest/epas_compat_ora_dev_guide/01_introduction/05_oracle_home/). +parameter, see [configuration paramters](../epas_compat_ora_dev_guide/01_introduction/05_oracle_home/). The `ORACLE_HOME` environment variable is must to be set and should include the path to the Oracle home directory. For example, 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 105364ce8c9..2a095c49162 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 @@ -8,7 +8,7 @@ legacyRedirectsGenerated: 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/) +[https://www.enterprisedb.com/docs](/epas/13/epas_compat_ora_dev_guide/) The following sections highlight some of the compatibility features supported by Advanced Server. @@ -33,7 +33,7 @@ Advanced Server supports a highly productive procedural language that allows you For information about using the Stored Procedural Language, see the *Database Compatibility for Stored Procedural Language Guide*, available at: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_spl/) +[https://www.enterprisedb.com/docs](/epas/13/epas_compat_spl/) ## Optimizer Hints @@ -47,19 +47,18 @@ As a rule, the query planner will select the least expensive plan. You can use a An optimizer hint is a directive (or multiple directives) embedded in a comment-like syntax that immediately follows a `DELETE`, `INSERT`, `SELECT` or `UPDATE` command. Keywords in the comment instruct the server to employ or avoid a specific plan when producing the result set. For information about using optimizer hints, see the *Database Compatibility for Oracle Developers Guide*, available at: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_ora_dev_guide/) +[https://www.enterprisedb.com/docs](/epas/13/epas_compat_ora_dev_guide/) ## Data Dictionary Views -Advanced Server includes a set of views that provide information about database objects in a manner compatible with the Oracle data dictionary views. For detailed information about the views available with Advanced Server, see the *Database Compatibility for Oracle Developers Catalog Views Guide*, available at: +Advanced Server includes a set of views that provide information about database objects in a manner compatible with the Oracle data dictionary views. For detailed information about the views available with Advanced Server, see [Database Compatibility for Oracle Developers Catalog Views Guide](../epas_compat_cat_views/). -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_cat_views/) ## dblink_ora dblink_ora provides an OCI-based database link that allows you to `SELECT, INSERT, UPDATE` or `DELETE` data stored on an Oracle system from within Advanced Server. For detailed information about using `dblink_ora`, and the supported functions and procedures, see the *Database Compatibility for Oracle Developers Guide*, available at: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_ora_dev_guide/) +[https://www.enterprisedb.com/docs](/epas/13/epas_compat_ora_dev_guide/) ## Profile Management @@ -78,7 +77,7 @@ After creating the profile, you can associate the profile with one or more users For information about using profile management commands, see the *Database Compatibility for Oracle Developers Guide*, available at: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_ora_dev_guide/) +[https://www.enterprisedb.com/docs](/epas/13/epas_compat_ora_dev_guide/) ## Built-In Packages @@ -114,7 +113,7 @@ Advanced Server supports a number of built-in packages that provide compatibilit For detailed information about the procedures and functions available within each package, see the *Database Compatibility for Oracle Developers Built-In Package Guide*, available at: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_bip_guide/) +[https://www.enterprisedb.com/docs](../epas_compat_bip_guide/) ## Open Client Library @@ -132,7 +131,7 @@ For detailed information about the functions supported by the Open Client Librar 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/) +[https://www.enterprisedb.com/docs](/epas/13/epas_compat_tools_guide/) **EDB\*Plus** @@ -189,7 +188,7 @@ ECPGPlus supports Pro\*C syntax in C programs when connected to an Advanced Serv For information about using ECPGPlus, see the *EDB Postgres Advanced Server ECPG Connector Guide*, available from the EDB website at: -[https://www.enterprisedb.com/docs](/epas/latest/ecpgplus_guide/) +[https://www.enterprisedb.com/docs](/epas/13/ecpgplus_guide/) ## Table Partitioning @@ -204,4 +203,4 @@ Table partitioning is worthwhile only when a table would otherwise be very large For information about database compatibility features supported by Advanced Server see the *Database Compatibility Table Partitioning Guide*, available at: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_table_partitioning/) +[https://www.enterprisedb.com/docs](/epas/13/epas_compat_table_partitioning/) diff --git a/product_docs/docs/epas/13/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx b/product_docs/docs/epas/13/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx index 8016dee2aec..d6c5c1438b8 100644 --- a/product_docs/docs/epas/13/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx +++ b/product_docs/docs/epas/13/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx @@ -343,7 +343,7 @@ Use the `edbldr.empty_csv_field` parameter to specify how EDB\*Loader will treat For more information about the `edbldr.empty_csv_field` parameter in EDB\*Loader, see the *Database Compatibility for Oracle Developers Tools and Utilities Guide* at the EDB website: -[https://www.enterprisedb.com/docs](/epas/latest/epas_compat_tools_guide/) +[https://www.enterprisedb.com/docs](/epas/13/epas_compat_tools_guide/) ## utl_encode.uudecode_redwood diff --git a/product_docs/docs/epas/13/epas_guide/14_edb_clone_schema.mdx b/product_docs/docs/epas/13/epas_guide/14_edb_clone_schema.mdx index 22f7eec7f20..f6bbe31b9c3 100644 --- a/product_docs/docs/epas/13/epas_guide/14_edb_clone_schema.mdx +++ b/product_docs/docs/epas/13/epas_guide/14_edb_clone_schema.mdx @@ -109,7 +109,7 @@ shared_preload_libraries = '$libdir/dbms_pipe,$libdir/dbms_aq,$libdir/parallel_c **Step 3:** The Perl Procedural Language (PL/Perl) must be installed on the database and the `CREATE TRUSTED LANGUAGE plperl` command must be run. For Linux, install PL/Perl using the `edb-asxx-server-plperl` RPM package where `xx` is the Advanced Server version number. For Windows, use the EDB Postgres Language Pack. For information on EDB Language Pack, see the *EDB Postgres Language Pack Guide* available at: -[https://www.enterprisedb.com/docs](/epas/latest/language_pack/) +[https://www.enterprisedb.com/docs](/language_pack/latest/) **Step 4:** Connect to the database as a superuser and run the following command: 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 7f85236c392..2cf007a2b06 100644 --- a/product_docs/docs/epas/13/epas_qs_windows/index.mdx +++ b/product_docs/docs/epas/13/epas_qs_windows/index.mdx @@ -200,7 +200,7 @@ If you select `Compatible with Oracle`, the installation will include the follow 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/) +[https://www.enterprisedb.com/docs](../epas_compat_bip_guide/) If you choose to install in `Compatible with Oracle` mode, the Advanced Server superuser name is `enterprisedb`. diff --git a/product_docs/docs/epas/13/installing/windows/installing_advanced_server/01_performing_a_graphical_installation_on_windows.mdx b/product_docs/docs/epas/13/installing/windows/installing_advanced_server/01_performing_a_graphical_installation_on_windows.mdx index ee69c717c61..b4ce3631b87 100644 --- a/product_docs/docs/epas/13/installing/windows/installing_advanced_server/01_performing_a_graphical_installation_on_windows.mdx +++ b/product_docs/docs/epas/13/installing/windows/installing_advanced_server/01_performing_a_graphical_installation_on_windows.mdx @@ -159,7 +159,7 @@ If you select `Compatible with Oracle`, the installation will include the follow 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/) +[https://www.enterprisedb.com/docs](../../../epas_compat_bip_guide/) If you choose to install in `Compatible with Oracle` mode, the Advanced Server superuser name is `enterprisedb`. diff --git a/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx b/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx index e9a28663066..6ed320bdf7b 100644 --- a/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx +++ b/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx @@ -51,7 +51,7 @@ The process for implementing Virtual Private Database is as follows: 1. Use the `ENABLE_POLICY` procedure to disable or enable an existing policy. 1. Use the `DROP_POLICY` procedure to remove an existing policy. The `DROP_POLICY` procedure doesn't drop the policy function or the associated database object. -Once you create policies, you can view them in the catalog views compatible with Oracle databases: `ALL_POLICIES`, `DBA_POLICIES`, or `USER_POLICIES`. The supported compatible views are listed in [Catalog views](/epas/latest/epas_compat_cat_views/). +Once you create policies, you can view them in the catalog views compatible with Oracle databases: `ALL_POLICIES`, `DBA_POLICIES`, or `USER_POLICIES`. The supported compatible views are listed in [Catalog views](../../epas_compat_cat_views/). The `SYS_CONTEXT` function is often used with `DBMS_RLS`. The signature is: diff --git a/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/index.mdx b/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/index.mdx index 27fd12ec1e5..7e66070fabf 100644 --- a/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/index.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: Built-in packages are provided with EDB Postgres Advanced Server. For certain packages, non-superusers must be explicitly granted the `EXECUTE` privilege on the package before using any of the package’s functions or procedures. For most of the built-in packages, `EXECUTE` privilege is granted to `PUBLIC` by default. -For information about using the `GRANT` command to provide access to a package, see [SQL reference](/epas/latest/epas_compat_sql/). +For information about using the `GRANT` command to provide access to a package, see [`GRANT`](../../epas_compat_sql/64_grant/). All built-in packages are owned by the special `sys` user that must be specified when granting or revoking privileges on built-in packages: diff --git a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx index daecfb55d11..6958621ada5 100644 --- a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx +++ b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx @@ -4,7 +4,7 @@ title: "edb_redwood_raw_names" -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, and user names appear in uppercase letters when viewed from Oracle catalogs. For a complete list of supported catalog views, see [Catalog views](/epas/latest/epas_compat_cat_views/). 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, and user names appear in uppercase letters when viewed from Oracle catalogs. For a complete list of supported catalog views, see [Catalog views](../../epas_compat_cat_views/). 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 stored in the PostgreSQL system catalogs when viewed from the Oracle catalogs. Thus, names created without quotation marks appear in lowercase as expected in PostgreSQL. Names created in quotation marks appear exactly as they were created but without the quotation marks. diff --git a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx index bb12a54c905..e049bcbe7b3 100644 --- a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx +++ b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx @@ -14,5 +14,5 @@ Compatible tools and utility programs allow you to work with EDB Postgres Advanc - EDB\*Wrap - The Dynamic Runtime Instrumentation Tools Architecture (DRITA) -For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/). +For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/14/epas_compat_tools_guide/). diff --git a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/index.mdx b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/index.mdx index a86f3a6b1cd..42418535777 100644 --- a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/index.mdx @@ -18,11 +18,10 @@ Database compatibility for Oracle means that an application runs in an Oracle en - SQL statements that are compatible with Oracle SQL - System catalog views that are compatible with Oracle’s data dictionary -For detailed information about the compatible SQL syntax, data types, and views, see [SQL reference](/epas/latest/epas_compat_sql/). +For detailed information about the compatible SQL syntax, data types, and views, see [SQL reference](../epas_compat_sql/). -For the compatibility offered by the procedures and functions that are part of the built-in packages, see [Built-in packages](/epas/latest/epas_compat_bip_guide/). +The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Built-in packages](../epas_compat_bip_guide/). -For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools and utilities](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/). +For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools, utilities, and components](../epas_compat_ora_dev_guide/09_tools_and_utilities/). 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 [EDB OCL Connector](/ocl_connector/latest/). - diff --git a/product_docs/docs/epas/14/epas_compat_reference/02_the_sql_language/01_sql_syntax/01_lexical_structure.mdx b/product_docs/docs/epas/14/epas_compat_reference/02_the_sql_language/01_sql_syntax/01_lexical_structure.mdx index 8ec4a0b67b2..bfefa0f6e87 100644 --- a/product_docs/docs/epas/14/epas_compat_reference/02_the_sql_language/01_sql_syntax/01_lexical_structure.mdx +++ b/product_docs/docs/epas/14/epas_compat_reference/02_the_sql_language/01_sql_syntax/01_lexical_structure.mdx @@ -24,4 +24,4 @@ INSERT INTO MY_TABLE VALUES (3, 'hi there'); This is a sequence of three commands, one per line, although that format isn't required. You can enter more than one command on a line, and commands can usually split across lines. -The SQL syntax isn't very consistent regarding the tokens that identify commands and the ones that are operands or parameters. The first few tokens are generally the command name, so the example contains a `SELECT`, an `UPDATE`, and an `INSERT` command. But, for instance, the `UPDATE` command always requires a `SET` token to appear in a certain position, and this variation of `INSERT` also requires a `VALUES` token to be complete. The precise syntax rules for each command are described in [SQL reference](/epas/latest/epas_compat_sql/). +The SQL syntax isn't very consistent regarding the tokens that identify commands and the ones that are operands or parameters. The first few tokens are generally the command name, so the example contains a `SELECT`, an `UPDATE`, and an `INSERT` command. But, for instance, the `UPDATE` command always requires a `SET` token to appear in a certain position, and this variation of `INSERT` also requires a `VALUES` token to be complete. The precise syntax rules for each command are described in [SQL reference](../../../epas_compat_sql/). diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx index adaba5e4452..94aa8ba7abf 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx @@ -31,7 +31,7 @@ However, certain data types have alternative names referred to as *aliases*, whi For example, you can specify fixed-length character data types as `CHAR` or `CHARACTER`. You can specify variable-length character data types 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 EDB Postgres Advanced Server, see [Data types](/epas/latest/epas_compat_reference/02_the_sql_language/02_data_types/). +For detailed information about the data types supported by EDB Postgres Advanced Server, see [Data types](/epas/14/epas_compat_reference/02_the_sql_language/02_data_types/). Thus, when attempting to create overloaded subprograms, the formal parameter data types aren't considered different if the specified data types are aliases of each other. diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx index 3c59b62d730..8aa54196332 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx @@ -30,7 +30,7 @@ If specified, `qualifier` is the subprogram or labeled anonymous block in which schema_name.package_name.public_variable_name ``` -For more information about supported package syntax, see [Database Compatibility for Oracle Developers: Built-in Package](/epas_compat_bip_guide/03_built-in_packages/). +For more information about supported package syntax, see [Database Compatibility for Oracle Developers: Built-in Package](../../../epas_compat_bip_guide/03_built-in_packages/). You can access variables in the following ways: diff --git a/product_docs/docs/epas/14/epas_compat_spl/10_collections/02_nested_tables.mdx b/product_docs/docs/epas/14/epas_compat_spl/10_collections/02_nested_tables.mdx index 095e5d5b040..6048238b9da 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/10_collections/02_nested_tables.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/10_collections/02_nested_tables.mdx @@ -30,7 +30,7 @@ Where: `objtype` is a previously defined object type. !!! Note - You can use the `CREATE TYPE` command to define a nested table type that's available to all SPL programs in the database. See [Database Compatibility for Oracle Developers: SQL](/epas_compat_sql) for more information about the `CREATE TYPE` command. + You can use the `CREATE TYPE` command to define a nested table type that's available to all SPL programs in the database. See [Database Compatibility for Oracle Developers: SQL](../../epas_compat_sql/39_create_type/) for more information about the `CREATE TYPE` command. To use the table, you must declare a *variable* of that nested table type. The following is the syntax for declaring a table variable: diff --git a/product_docs/docs/epas/14/epas_compat_spl/14_packages.mdx b/product_docs/docs/epas/14/epas_compat_spl/14_packages.mdx index dde4471edc6..4fe75f00d4d 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/14_packages.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/14_packages.mdx @@ -17,4 +17,4 @@ A *package* is a named collection of functions, procedures, variables, cursors, - You can declare Other functions, procedures, variables, types, and so on in the package as *private*. Private entities can be referenced and used by function and procedures in the package but not by other external applications. Private entities are for use only by programs in the package. - You can overload function and procedure names in a package. One or more functions or procedures can be defined with the same name but with different signatures. This ability lets you create identically named programs that perform the same job but on different types of input. -For more information about the package support provided by EDB Postgres Advanced Server, see [Built-in packages](/epas/latest/epas_compat_bip_guide/). \ No newline at end of file +For more information about the package support provided by EDB Postgres Advanced Server, see [Built-in packages](../epas_compat_bip_guide/). \ No newline at end of file diff --git a/product_docs/docs/epas/14/epas_compat_sql/21_create_public_database_link.mdx b/product_docs/docs/epas/14/epas_compat_sql/21_create_public_database_link.mdx index 19cc89709ed..1507129fcb4 100644 --- a/product_docs/docs/epas/14/epas_compat_sql/21_create_public_database_link.mdx +++ b/product_docs/docs/epas/14/epas_compat_sql/21_create_public_database_link.mdx @@ -131,7 +131,7 @@ export LD_LIBRARY_PATH=/tmp/instantclient:$LD_LIBRARY_PATH Alternatively, you can set the value of the `oracle_home` configuration parameter in the `postgresql.conf` file. The `oracle_home` configuration parameter is an alternative to the `LD_LIBRARY_PATH` environment variable. For more details on the `oracle_home` configuration -parameter, see [configuration parameters](/epas/latest/epas_compat_ora_dev_guide/01_introduction/05_oracle_home/). +parameter, see [configuration paramters](../epas_compat_ora_dev_guide/01_introduction/05_oracle_home/). The `ORACLE_HOME` environment variable must be set and include the path to the Oracle home directory. For example, diff --git a/product_docs/docs/epas/14/epas_compat_sql/31_create_queue_table.mdx b/product_docs/docs/epas/14/epas_compat_sql/31_create_queue_table.mdx index ef3f80cb973..ecd5756eb5e 100644 --- a/product_docs/docs/epas/14/epas_compat_sql/31_create_queue_table.mdx +++ b/product_docs/docs/epas/14/epas_compat_sql/31_create_queue_table.mdx @@ -46,7 +46,7 @@ The name of the queue table must be unique among queue tables in the same schema `type_name` - The name of an existing type that describes the payload of each entry in the queue table. For information about defining a type, see [CREATE TYPE](/#create_type). + The name of an existing type that describes the payload of each entry in the queue table. For information about defining a type, see [CREATE TYPE](39_create_type/). `option_name option_value` diff --git a/product_docs/docs/epas/14/epas_compat_sql/34_create_sequence.mdx b/product_docs/docs/epas/14/epas_compat_sql/34_create_sequence.mdx index 5d09b411cd4..5c06b612fc9 100644 --- a/product_docs/docs/epas/14/epas_compat_sql/34_create_sequence.mdx +++ b/product_docs/docs/epas/14/epas_compat_sql/34_create_sequence.mdx @@ -27,7 +27,7 @@ CREATE SEQUENCE [ INCREMENT BY ] If you include a schema name, then the sequence is created in the specified schema. Otherwise it's created in the current schema. The sequence name differ from the name of any other sequence, table, index, or view in the same schema. -After you create a sequence, use the functions `NEXTVAL` and `CURRVAL` to operate on it. These functions are documented in [SQL reference](/epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/09_sequence_manipulation_functions/). +After you create a sequence, use the functions `NEXTVAL` and `CURRVAL` to operate on it. These functions are documented in [SQL reference](/epas/14/epas_compat_reference/02_the_sql_language/03_functions_and_operators/09_sequence_manipulation_functions/). ## Parameters diff --git a/product_docs/docs/epas/14/epas_compat_sql/36_create_table.mdx b/product_docs/docs/epas/14/epas_compat_sql/36_create_table.mdx index 13970152ed5..d94690f9a69 100644 --- a/product_docs/docs/epas/14/epas_compat_sql/36_create_table.mdx +++ b/product_docs/docs/epas/14/epas_compat_sql/36_create_table.mdx @@ -97,7 +97,7 @@ You can define table constraints and column constraints. A column constraint is `data_type` - The data type of the column. This can include array specifiers. For more information on the data types included with EDB Postgres Advanced Server, see [SQL reference](/epas/latest/epas_compat_reference/02_the_sql_language/02_data_types/). + The data type of the column. This can include array specifiers. For more information on the data types included with EDB Postgres Advanced Server, see [SQL reference](/epas/14/epas_compat_reference/02_the_sql_language/02_data_types/). `DEFAULT default_expr` @@ -217,7 +217,7 @@ You can define table constraints and column constraints. A column constraint is ## Notes -EDB Postgres Advanced Server creates an index for each unique constraint and primary key constraint to enforce the uniqueness. Thus, you don't need to create an explicit index for primary key columns. For more information, see [`CREATE INDEX`](/#create_index). +EDB Postgres Advanced Server creates an index for each unique constraint and primary key constraint to enforce the uniqueness. Thus, you don't need to create an explicit index for primary key columns. For more information, see [`CREATE INDEX`](24_create_index/). ## Examples diff --git a/product_docs/docs/epas/14/epas_compat_sql/37_create_table_as.mdx b/product_docs/docs/epas/14/epas_compat_sql/37_create_table_as.mdx index cace39be689..cf46390db22 100644 --- a/product_docs/docs/epas/14/epas_compat_sql/37_create_table_as.mdx +++ b/product_docs/docs/epas/14/epas_compat_sql/37_create_table_as.mdx @@ -32,7 +32,7 @@ CREATE [ GLOBAL TEMPORARY ] TABLE `GLOBAL TEMPORARY` - Specify to create the table as a temporary table. For details, see [`CREATE TABLE`](/#create_table). + Specify to create the table as a temporary table. For details, see [`CREATE TABLE`](./36_create_table.mdx). `table_name` @@ -44,4 +44,4 @@ CREATE [ GLOBAL TEMPORARY ] TABLE `query` - A query statement (a `SELECT` command). For a description of the allowed syntax, see [`SELECT`](/#select). + A query statement (a `SELECT` command). For a description of the allowed syntax, see [`SELECT`](./71_select.mdx). diff --git a/product_docs/docs/epas/14/epas_compat_sql/43_create_view.mdx b/product_docs/docs/epas/14/epas_compat_sql/43_create_view.mdx index e7e34cbae74..50d2b8e783b 100644 --- a/product_docs/docs/epas/14/epas_compat_sql/43_create_view.mdx +++ b/product_docs/docs/epas/14/epas_compat_sql/43_create_view.mdx @@ -39,7 +39,7 @@ If you provide a schema name, then the view is created in the specified schema. `query` - A query (that is, a `SELECT` statement) that provides the columns and rows of the view. See [`SELECT`](/#select) for information about valid queries. + A query (that is, a `SELECT` statement) that provides the columns and rows of the view. See [`SELECT`](./71_select.mdx) for information about valid queries. ## Notes diff --git a/product_docs/docs/epas/14/epas_compat_sql/71_select.mdx b/product_docs/docs/epas/14/epas_compat_sql/71_select.mdx index 1276ee800b2..1b590872a9a 100644 --- a/product_docs/docs/epas/14/epas_compat_sql/71_select.mdx +++ b/product_docs/docs/epas/14/epas_compat_sql/71_select.mdx @@ -57,7 +57,7 @@ You must have `SELECT` privilege on a table to read its values. The use of `FOR `optimizer_hint` - Comment-embedded hints to the optimizer for selecting an execution plan. See [Database compatibility for Oracle developers](/epas/latest/epas_compat_ora_dev_guide/) for information about optimizer hints. + Comment-embedded hints to the optimizer for selecting an execution plan. See [Database compatibility for Oracle developers](/epas/14/epas_compat_ora_dev_guide/) for information about optimizer hints. ## FROM clause diff --git a/product_docs/docs/epas/14/epas_compat_tools_guide/index.mdx b/product_docs/docs/epas/14/epas_compat_tools_guide/index.mdx index f590f2fb7c2..2d5f6fd1261 100644 --- a/product_docs/docs/epas/14/epas_compat_tools_guide/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_tools_guide/index.mdx @@ -13,9 +13,9 @@ These tools and utilities allow a developer that works with Oracle utilities to These compatible tools and utilities that are supported by EDB Postgres Advanced Server: -- [EDB\*Loader](/epas/latest/epas_compat_tools_guide/02_edb_loader/) -- [EDB\*Wrap](/epas/latest/epas_compat_tools_guide/03_edb_wrap/) -- [Dynamic Runtime Instrumentation](/epas/latest/epas_compat_tools_guide/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/) +- [EDB\*Loader](/epas/14/epas_compat_tools_guide/02_edb_loader/) +- [EDB\*Wrap](/epas/14/epas_compat_tools_guide/03_edb_wrap/) +- [Dynamic Runtime Instrumentation](/epas/14/epas_compat_tools_guide/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/) The EDB\*Plus command line client provides a user interface to EDB Postgres Advanced Server that supports SQL\*Plus commands; EDB\*Plus allows you to: diff --git a/product_docs/docs/epas/14/epas_guide/02_enhanced_compatibility_features.mdx b/product_docs/docs/epas/14/epas_guide/02_enhanced_compatibility_features.mdx index 477fe9d18db..9e5993c609a 100644 --- a/product_docs/docs/epas/14/epas_guide/02_enhanced_compatibility_features.mdx +++ b/product_docs/docs/epas/14/epas_guide/02_enhanced_compatibility_features.mdx @@ -19,7 +19,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.026.html" --- -EDB Postgres Advanced Server includes extended functionality that provides compatibility for syntax supported by Oracle applications. See [Database compatibility for Oracle developers](/epas/latest/epas_compat_ora_dev_guide/) for detailed information about the compatibility features supported by EDB Postgres Advanced Server. +EDB Postgres Advanced Server includes extended functionality that provides compatibility for syntax supported by Oracle applications. See [Database compatibility for Oracle developers](/epas/14/epas_compat_ora_dev_guide/) for detailed information about the compatibility features supported by EDB Postgres Advanced Server. ## Enabling compatibility features @@ -28,7 +28,7 @@ You can install EDB Postgres Advanced Server in several ways to take advantage o - Use the `INITDBOPTS` variable in the EDB Postgres Advanced Server service configuration file to specify `--redwood-like` before initializing your cluster. - When invoking `initdb` to initialize your cluster compatible with Oracle mode, include the `--redwood-like` or `--no-redwood-compat` option to initialize your cluster in Oracle non-compatible mode. -See [Configuration parameters compatible with Oracle databases](/epas/latest/epas_compat_ora_dev_guide/01_introduction/) and [Managing an EDB Postgres Advanced Server installation](/epas/latest/installing/linux_install_details/managing_an_advanced_server_installation/) for more information about the installation options supported by the EDB Postgres Advanced Server installers. +See [Configuration parameters compatible with Oracle databases](/epas/14/epas_compat_ora_dev_guide/01_introduction/) and [Managing an EDB Postgres Advanced Server installation](/epas/latest/installing/linux_install_details/managing_an_advanced_server_installation/) for more information about the installation options supported by the EDB Postgres Advanced Server installers. ## Stored procedural language @@ -38,7 +38,7 @@ EDB Postgres Advanced Server supports a highly productive procedural language th - Provides a seamless development and testing environment. - Allows you to create reusable code. -See [Stored procedural language](/epas/latest/epas_compat_spl/) for more information. +See [Stored procedural language](/epas/14/epas_compat_spl/) for more information. ## Optimizer hints @@ -48,15 +48,15 @@ When you invoke a `DELETE`, `INSERT`, `SELECT`, or `UPDATE` command, the server - Parameter values assigned in the Query Tuning section of the `postgresql.conf` file - Column statistics that are gathered by the `ANALYZE` command -As a rule, the query planner selects the least expensive plan. You can use an *optimizer hint* to influence the server as it selects a query plan. An optimizer hint is one or more directives embedded in a comment-like syntax that immediately follows a `DELETE`, `INSERT`, `SELECT`, or `UPDATE` command. Keywords in the comment instruct the server to use or avoid a specific plan when producing the result set. See [Optimizer hints](/epas/latest/epas_compat_ora_dev_guide/05_optimizer_hints/) for more information. +As a rule, the query planner selects the least expensive plan. You can use an *optimizer hint* to influence the server as it selects a query plan. An optimizer hint is one or more directives embedded in a comment-like syntax that immediately follows a `DELETE`, `INSERT`, `SELECT`, or `UPDATE` command. Keywords in the comment instruct the server to use or avoid a specific plan when producing the result set. See [Optimizer hints](/epas/14/epas_compat_ora_dev_guide/05_optimizer_hints/) for more information. ## Data dictionary views -EDB Postgres Advanced Server includes a set of views that provide information about database objects in a manner compatible with the Oracle data dictionary views. See [Database compatibility for Oracle developers: catalog views](/epas/latest/epas_compat_cat_views) for detailed information about the views available with EDB Postgres Advanced Server. +EDB Postgres Advanced Server includes a set of views that provide information about database objects in a manner compatible with the Oracle data dictionary views. See [Catalog views](../epas_compat_cat_views/) for detailed information about the views available with EDB Postgres Advanced Server. ## dblink_ora -dblink_ora provides an OCI-based database link that allows you to `SELECT`, `INSERT`, `UPDATE`, or `DELETE` data stored on an Oracle system from EDB Postgres Advanced Server. See [dblink_ora](/epas/latest/epas_compat_ora_dev_guide/06_dblink_ora/) for detailed information about using `dblink_ora` and the supported functions and procedures. +dblink_ora provides an OCI-based database link that allows you to `SELECT`, `INSERT`, `UPDATE`, or `DELETE` data stored on an Oracle system from EDB Postgres Advanced Server. See [dblink_ora](/epas/14/epas_compat_ora_dev_guide/06_dblink_ora/) for detailed information about using `dblink_ora` and the supported functions and procedures. ## Profile management @@ -75,7 +75,7 @@ When a user connects to the server, the server enforces the profile that's assoc Profiles are shared by all databases in a cluster, but each cluster can have multiple profiles. A single user with access to multiple databases uses the same profile when connecting to each database in the cluster. -See [Profile management](/epas/latest/epas_compat_ora_dev_guide/04_profile_management/) for information about using profile management commands. +See [Profile management](/epas/14/epas_compat_ora_dev_guide/04_profile_management/) for information about using profile management commands. ## Built-in packages @@ -109,7 +109,7 @@ EDB Postgres Advanced Server supports a number of built-in packages that provide | UTL_SMTP | The UTL_SMTP package lets you send emails over the Simple Mail Transfer Protocol (SMTP). | | UTL_URL | The UTL_URL package provides a way to escape illegal and reserved characters in a URL. | -See [Built-in packages](/epas/latest/epas_compat_bip_guide/03_built-in_packages/) for detailed information about the procedures and functions available in each package. +See [Built-in packages](../epas_compat_bip_guide/03_built-in_packages/) for detailed information about the procedures and functions available in each package. ## Open Client Library @@ -123,7 +123,7 @@ For detailed information about the functions supported by the Open Client Librar ## Utilities -For detailed information about the compatible syntax supported by these utilities, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/). +For detailed information about the compatible syntax supported by these utilities, see [Tools, utilities, and components](/epas/14/epas_compat_tools_guide/). ### EDB\*Plus @@ -176,7 +176,7 @@ ECPGPlus supports Pro\*C syntax in C programs when connected to an EDB Postgres - Pro\*C-compatible anonymous blocks - A `CALL` statement compatible with Oracle databases -See [ECPGPlus](/epas/latest/ecpgplus_guide/) for information. +See [ECPGPlus](/epas/14/ecpgplus_guide/) for information. ## Table partitioning @@ -189,4 +189,4 @@ In a partitioned table, one logically large table is broken into smaller physica Table partitioning is worthwhile only when a table would otherwise be very large. The exact point at which a table benefits from partitioning depends on the application. A good estimation is when the size of the table exceeds the physical memory of the database server. -For information about database compatibility features supported by EDB Postgres Advanced Server, see [Table partitioning](/epas/latest/epas_compat_table_partitioning/). +For information about database compatibility features supported by EDB Postgres Advanced Server, see [Table partitioning](/epas/14/epas_compat_table_partitioning/). diff --git a/product_docs/docs/epas/14/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx b/product_docs/docs/epas/14/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx index 1be5e8d5e2c..6825ed58c09 100644 --- a/product_docs/docs/epas/14/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx +++ b/product_docs/docs/epas/14/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx @@ -339,7 +339,7 @@ Use the `edbldr.empty_csv_field` parameter to specify how EDB\*Loader treats an | `empty_string` | An empty field is treated as a string of length zero. | | `pgsql` | An empty field is treated as a `NULL` if it doesn't contain quotes and as an empty string if it contains quotes. | -For more information about the `edbldr.empty_csv_field` parameter in EDB\*Loader, see the [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/). +For more information about the `edbldr.empty_csv_field` parameter in EDB\*Loader, see the [Tools, utilities, and components](/epas/14/epas_compat_tools_guide/). ## utl_encode.uudecode_redwood diff --git a/product_docs/docs/epas/14/epas_guide/14_edb_clone_schema.mdx b/product_docs/docs/epas/14/epas_guide/14_edb_clone_schema.mdx index f077f96b47c..3acb1469ba6 100644 --- a/product_docs/docs/epas/14/epas_guide/14_edb_clone_schema.mdx +++ b/product_docs/docs/epas/14/epas_guide/14_edb_clone_schema.mdx @@ -100,7 +100,7 @@ Perform this installation on any database to be used as the source or target dat shared_preload_libraries = '$libdir/dbms_pipe,$libdir/dbms_aq,$libdir/parallel_clone' ``` -1. Install the Perl procedural language (PL/Perl) on the database, and run the `CREATE TRUSTED LANGUAGE plperl` command. For Linux, install PL/Perl using the `edb-asxx-server-plperl` RPM package, where `xx` is the EDB Postgres Advanced Server version number. For Windows, use the EDB Postgres Language Pack. For information on EDB Language Pack, see the [EDB Postgres Language Pack](/epas/latest/language_pack/). +1. Install the Perl procedural language (PL/Perl) on the database, and run the `CREATE TRUSTED LANGUAGE plperl` command. For Linux, install PL/Perl using the `edb-asxx-server-plperl` RPM package, where `xx` is the EDB Postgres Advanced Server version number. For Windows, use the EDB Postgres Language Pack. For information on EDB Language Pack, see the [EDB Postgres Language Pack](/language_pack/latest/). 1. Connect to the database as a superuser and run the following command: diff --git a/product_docs/docs/epas/14/epas_qs_windows/index.mdx b/product_docs/docs/epas/14/epas_qs_windows/index.mdx index f0d0a9865e4..588f3a6e66a 100644 --- a/product_docs/docs/epas/14/epas_qs_windows/index.mdx +++ b/product_docs/docs/epas/14/epas_qs_windows/index.mdx @@ -187,7 +187,7 @@ If you select `Compatible with Oracle`, the installation includes the following This is not a comprehensive list of the compatibility features for Oracle included when EDB Postgres 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/) +[https://www.enterprisedb.com/docs](../epas_compat_bip_guide/) If you choose to install in `Compatible with Oracle` mode, the EDB Postgres Advanced Server superuser name is `enterprisedb`. diff --git a/product_docs/docs/epas/14/installing/linux_install_details/rpm_packages.mdx b/product_docs/docs/epas/14/installing/linux_install_details/rpm_packages.mdx index b112d003293..b08723e8b77 100644 --- a/product_docs/docs/epas/14/installing/linux_install_details/rpm_packages.mdx +++ b/product_docs/docs/epas/14/installing/linux_install_details/rpm_packages.mdx @@ -52,7 +52,7 @@ Note: The available package list is subject to change. | edb-as14-server-sslutils | This package installs functionality that provides SSL support. | | edb-as14-server-cloneschema | This package installs the EDB Clone Schema extension. For more information about EDB Clone Schema, see the *EDB Postgres Advanced Server Guide*. | | edb-as14-server-parallel-clone | This package installs functionality that supports the EDB Clone Schema extension. | -| edb-as14-pgagent | Installs pgAgent; pgAgent is a job scheduler for EDB Postgres Advanced Server. Before installing this package, you must install EPEL; for detailed information about installing EPEL, see [Linux installation troubleshooting](/epas/latest/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux/). | +| edb-as14-pgagent | Installs pgAgent; pgAgent is a job scheduler for EDB Postgres Advanced Server. Before installing this package, you must install EPEL; for detailed information about installing EPEL, see [Linux installation troubleshooting](/epas/14/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux/). | | edb-as14-edbplus | The `edb-edbplus` package contains the files required to install the EDB\*Plus command line client. EDB\*Plus commands are compatible with Oracle's SQL\*Plus. | | edb-as14-pgsnmpd | SNMP (Simple Network Management Protocol) is a protocol that allows you to supervise an apparatus connected to the network. | | edb-as14-pgpool41-extensions | This package creates pgPool extensions required by the server for use with pgpool. | @@ -65,7 +65,7 @@ Note: The available package list is subject to change. | edb-as14-slony-replication | Installs the meta RPM for Slony-I. | | edb-as14-slony-replication-core | Slony-I builds a primary-standby system that includes all features and capabilities needed to replicate large databases to a reasonably limited number of standby systems. | | edb-as14-slony-replication-docs | This package contains the Slony project documentation (in pdf form). | -| edb-as14-slony-replication-tools | This package contains the Slony altperl tools and utilities that are useful when deploying Slony replication environments. Before installing this package, you must install EPEL; for detailed information about installing EPEL, see [Linux installation troubleshooting](/epas/latest/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux/). | +| edb-as14-slony-replication-tools | This package contains the Slony altperl tools and utilities that are useful when deploying Slony replication environments. Before installing this package, you must install EPEL; for detailed information about installing EPEL, see [Linux installation troubleshooting](/epas/14/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux/). | | edb-as14-libicu | These packages contain supporting library files. | The following table lists the packages for EDB Postgres Advanced Server 14 supporting components. @@ -149,11 +149,11 @@ apt list edb* | edb-as14-postgis3-gui | This package provides a GUI for POSTGIS. | | edb-as14-postgis-jdbc | This package provides support for POSTGIS. | | edb-as14-postgis-scripts | This package provides support for POSTGIS. | -| edb-as14-pgagent | This package installs pgAgent; pgAgent is a job scheduler for EDB Postgres Advanced Server. Before installing this package, you must install EPEL; for detailed information about installing EPEL, see [Linux installation troubleshooting](/epas/latest/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux/). | +| edb-as14-pgagent | This package installs pgAgent; pgAgent is a job scheduler for EDB Postgres Advanced Server. Before installing this package, you must install EPEL; for detailed information about installing EPEL, see [Linux installation troubleshooting](/epas/14/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux/). | | edb-as14-slony-replication | This package installs the meta RPM for Slony-I. | | edb-as14-slony-replication-core | This package contains core portions of Slony-I to build a primary-standby system that includes all features and capabilities needed to replicate large databases to a reasonably limited number of standby systems. | | edb-as14-slony-replication-docs | This package contains the Slony project documentation (in pdf form). | -| edb-as14-slony-replication-tools | This package contains the Slony altperl tools and utilities that are useful when deploying Slony replication environments. Before installing this package, you must install EPEL; for detailed information about installing EPEL, see [Linux installation troubleshooting](/epas/latest/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux/). | +| edb-as14-slony-replication-tools | This package contains the Slony altperl tools and utilities that are useful when deploying Slony replication environments. Before installing this package, you must install EPEL; for detailed information about installing EPEL, see [Linux installation troubleshooting](/epas/14/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux/). | | edb-as14-hdfs-fdw | The Hadoop Data Adapter allows you to query and join data from Hadoop environments with your Postgres or EDB Postgres Advanced Server instances. It is YARN Ready certified with HortonWorks, and provides optimizations for performance with predicate pushdown support. | | edb-as14-hdfs-fdw-doc | Documentation for the Hadoop Data Adapter. | | edb-as14-mongo-fdw | This EDB EDB Postgres Advanced Server extension implements a Foreign Data Wrapper for MongoDB. | diff --git a/product_docs/docs/epas/14/installing/windows/installing_advanced_server_with_the_interactive_installer/performing_a_graphical_installation_on_windows.mdx b/product_docs/docs/epas/14/installing/windows/installing_advanced_server_with_the_interactive_installer/performing_a_graphical_installation_on_windows.mdx index 69a6e065f8c..915763810fd 100644 --- a/product_docs/docs/epas/14/installing/windows/installing_advanced_server_with_the_interactive_installer/performing_a_graphical_installation_on_windows.mdx +++ b/product_docs/docs/epas/14/installing/windows/installing_advanced_server_with_the_interactive_installer/performing_a_graphical_installation_on_windows.mdx @@ -151,7 +151,7 @@ If you select `Compatible with Oracle`, the installation includes the following This is not a comprehensive list of the compatibility features for Oracle included when EDB Postgres 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/) +[https://www.enterprisedb.com/docs](../../../epas_compat_bip_guide/) If you choose to install in `Compatible with Oracle` mode, the EDB Postgres Advanced Server superuser name is `enterprisedb`. diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx index 091381bf409..48425b9bdd0 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx @@ -21,7 +21,7 @@ Where: !!! Note - If there are no parameters to pass, you can call the procedure with an empty parameter list, or you can omit the parentheses. - - The syntax for calling a procedure is the same as in the preceding syntax diagram when executing it with the `EXEC` command in PSQL or EDB\*Plus. See [SQL reference](/../../../../reference/oracle_compatibility_reference/epas_compat_sql/63_exec) for information about the `EXEC` command. + - The syntax for calling a procedure is the same as in the preceding syntax diagram when executing it with the `EXEC` command in PSQL or EDB\*Plus. See [SQL reference](../../../../reference/oracle_compatibility_reference/epas_compat_sql/63_exec/) for information about the `EXEC` command. This example calls the procedure from an anonymous block: diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx index df0a1fbe18b..35712c77b2d 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx @@ -34,7 +34,7 @@ If specified, `qualifier` is the subprogram or labeled anonymous block in which schema_name.package_name.public_variable_name ``` -For more information about supported package syntax, see [Built-in packages](/epas_compat_bip_guide/03_built-in_packages/). +For more information about supported package syntax, see [Built-in packages](../../../../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/). ## Requirements diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx index 9bee8240e19..1438206d820 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx @@ -42,7 +42,7 @@ Where: `objtype` is a previously defined object type. !!! Note - You can use the `CREATE TYPE` command to define a nested table type that's available to all SPL programs in the database. See [SQL reference](/../../../reference/oracle_compatibility_reference/epas_compat_sql/39_create_type/) for more information about the `CREATE TYPE` command. + You can use the `CREATE TYPE` command to define a nested table type that's available to all SPL programs in the database. See [SQL reference](../../../reference/oracle_compatibility_reference/epas_compat_sql/39_create_type/) for more information about the `CREATE TYPE` command. ## Declaring a variable diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/01_interval_range_partitioning.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/01_interval_range_partitioning.mdx index 1310eed303c..b95324f0067 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/01_interval_range_partitioning.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/01_interval_range_partitioning.mdx @@ -14,7 +14,7 @@ The high value of a range partition, also known as the transition point, is dete Suppose an interval is set to one month. If data is inserted for two months after the current transition point, only the partition for the second month is created and not the intervening partition. For example, you can create an interval-range-partitioned table with a monthly interval and a current transition point of February 15, 2023. If you try to insert data for May 10, 2023, then the required partition for April 15 to May 15, 2023 is created and data is inserted into that partition. The partition for February 15, 2023 to March 15, 2023 and March 15, 2023 to April 15, 2023 is skipped. -For information about interval range partitioning syntax, see [CREATE TABLE...PARTITION BY](/../../../reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/#create_table_partition_by). +For information about interval range partitioning syntax, see [CREATE TABLE...PARTITION BY](../../../reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/). ## Restrictions on interval range partitioning diff --git a/product_docs/docs/epas/15/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/02_automatic_list_partitioning.mdx b/product_docs/docs/epas/15/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/02_automatic_list_partitioning.mdx index 035194c97ed..e44e9e933ad 100644 --- a/product_docs/docs/epas/15/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/02_automatic_list_partitioning.mdx +++ b/product_docs/docs/epas/15/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/02_automatic_list_partitioning.mdx @@ -10,7 +10,7 @@ Automatic list partitioning is an extension to `LIST` partitioning that allows a For example, consider a table named `sales` with a `sales_state` column that contains the existing partition values `CALIFORNIA` and `FLORIDA`. Each of the `sales_state` values increases with a rise in the statewise sales. A sale in a new state, for example, `INDIANA` and `OHIO`, requires creating new partitions. If you implement automatic list partitioning, the new partitions `INDIANA` and `OHIO` are automatically created, and data is entered into the `sales` table. -For information about automatic list partitioning syntax, see [CREATE TABLE...PARTITION BY](/../../../reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/#create_table_partition_by). +For information about automatic list partitioning syntax, see [CREATE TABLE...PARTITION BY](../../../reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/). ## Restrictions for automatic list partitioning diff --git a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/index.mdx b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/index.mdx index a42768a9f7c..54678857595 100644 --- a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/index.mdx +++ b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/index.mdx @@ -7,7 +7,7 @@ redirects: -These configuration parameters are for use with the EDB Postgres Advanced Server database [auditing feature](/../../../epas_security_guide/05_edb_audit_logging/). +These configuration parameters are for use with the EDB Postgres Advanced Server database [auditing feature](../../../../epas_security_guide/05_edb_audit_logging/).
diff --git a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx index ec08ae632bb..41d34a503da 100644 --- a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx +++ b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx @@ -344,7 +344,7 @@ Use the `edbldr.empty_csv_field` parameter to specify how EDB\*Loader treats an | `empty_string` | An empty field is treated as a string of length zero. | | `pgsql` | An empty field is treated as a `NULL` if it doesn't contain quotes and as an empty string if it contains quotes. | -For more information about the `edbldr.empty_csv_field` parameter in EDB\*Loader, see [Tools, utilities, and components](/../../02_edb_loader). +For more information about the `edbldr.empty_csv_field` parameter in EDB\*Loader, see [Tools, utilities, and components](../../02_edb_loader). ## utl_encode.uudecode_redwood diff --git a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/14_audit_archiver.mdx b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/14_audit_archiver.mdx index 05af7eacce6..bc83700ebe8 100644 --- a/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/14_audit_archiver.mdx +++ b/product_docs/docs/epas/15/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/14_audit_archiver.mdx @@ -6,7 +6,7 @@ redirects: -These configuration parameters are used by the EDB Postgres Advanced Server database [audit archiving feature](/../../../epas_security_guide/05_edb_audit_logging/08_audit_log_archiving/). +These configuration parameters are used by the EDB Postgres Advanced Server database [audit archiving feature](../../../epas_security_guide/05_edb_audit_logging/08_audit_log_archiving/). ## edb_audit_archiver diff --git a/product_docs/docs/epas/15/installing/windows/managing_an_advanced_server_installation/configuring_epas.mdx b/product_docs/docs/epas/15/installing/windows/managing_an_advanced_server_installation/configuring_epas.mdx index e59c6a2821e..0fcb6378cc2 100644 --- a/product_docs/docs/epas/15/installing/windows/managing_an_advanced_server_installation/configuring_epas.mdx +++ b/product_docs/docs/epas/15/installing/windows/managing_an_advanced_server_installation/configuring_epas.mdx @@ -15,7 +15,7 @@ You can easily update parameters that determine the behavior of EDB Postgres Adv - The `pg_hba.conf` file specifies your preferences for network authentication and authorization. - The `pg_ident.conf` file maps operating system identities (user names) to EDB Postgres Advanced Server identities (roles) when using `ident`-based authentication. -For more information about modifying the `postgresql.conf` and `pg_hba.conf` files, see [Setting parameters](../../../../database_administration/01_configuration_parameters/01_setting_new_parameters). +For more information about modifying the `postgresql.conf` and `pg_hba.conf` files, see [Setting parameters](../../../database_administration/01_configuration_parameters/01_setting_new_parameters/). You can use your editor of choice to open a configuration file. On Windows, you can navigate through the **EDB Postgres** menu to open a file. diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/index.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/index.mdx index fbd0abd39db..ea18d15e874 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/index.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/index.mdx @@ -45,7 +45,7 @@ ALTER TABLE SET SUBPARTITION TEMPLATE (); You can use the `ALTER TABLE… SET SUBPARTITION TEMPLATE` command to update the subpartition template for range, list, or hash-partitioned table. If you're specifying a subpartition descriptor for a partition, use a subpartition descriptor instead of a subpartition template. You can use the subpartition template whenever a subpartition descriptor isn't specified for a partition. If you don't specify either the subpartition descriptor or subpartition template, then by default a single subpartition is created. -For more information about creating a subpartition template, see [CREATE TABLE...PARTITION BY](../../04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/#create_table_partition_by). +For more information about creating a subpartition template, see [CREATE TABLE...PARTITION BY](../../04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/). !!! Note The partitions added to a table after invoking `ALTER TABLE… SET SUBPARTITION TEMPLATE` command use the new `SUBPARTITION TEMPLATE`. diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/index.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/index.mdx index 96a8a7e1ae6..998d0219e04 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/index.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/index.mdx @@ -5,7 +5,7 @@ indexCards: simple description: "Listing of the catalog views support provided by EDB Postgres Advanced Server" redirects: - /epas/latest/epas_compat_cat_views/ #generated for docs/epas/reorg-role-use-case-mode - - ../../../../epas_compat_ora_dev_guide/08_oracle_catalog_views/ + - /epas/latest/epas_compat_ora_dev_guide/08_oracle_catalog_views/ --- Catalog views provide information about database objects. There are two catagories of catalog views: diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns.mdx index 6a57d62ab4a..b919b3b35bf 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.175.html" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/09_all_ind_columns/ + - /epas/latest/epas_compat_cat_views/09_all_ind_columns/ --- diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/19_all_source.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/19_all_source.mdx index 5a78401a66d..e8850148a5b 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/19_all_source.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/19_all_source.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.183.html" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/19_all_source/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/19_all_source/ + - /epas/latest/epas_compat_cat_views/19_all_source/ --- diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns.mdx index 00567bac4ef..b49f01eed69 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.186.html" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/22_all_tab_columns/ + - /epas/latest/epas_compat_cat_views/22_all_tab_columns/ --- diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs.mdx index 3274d3a26be..fb4943a7db9 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs.mdx @@ -2,7 +2,7 @@ title: "ALL_TAB_PRIVS" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/25_all_tab_privs/ + - /epas/latest/epas_compat_cat_views/25_all_tab_privs/ --- diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/37_dba_directories.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/37_dba_directories.mdx index f46df25c2f7..08ee8ec9c39 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/37_dba_directories.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/37_dba_directories.mdx @@ -5,7 +5,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.138.html" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/37_dba_directories/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/37_dba_directories/ + - /epas/latest/epas_compat_cat_views/37_dba_directories/ --- diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/72_user_jobs.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/72_user_jobs.mdx index 4a7fd1995bc..f4e6c7d14cd 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/72_user_jobs.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/72_user_jobs.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.228.html" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/72_user_jobs/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/72_user_jobs/ + - /epas/latest/epas_compat_cat_views/72_user_jobs/ --- diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms.mdx index 50f2cbf04d8..a2ee6eb3e6a 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.237.html" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/82_user_synonyms/ + - /epas/latest/epas_compat_cat_views/82_user_synonyms/ --- diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions.mdx index a7003d67bb9..368dff07edf 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.239.html" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/84_user_tab_partitions/ + - /epas/latest/epas_compat_cat_views/84_user_tab_partitions/ --- diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/21_create_public_database_link.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/21_create_public_database_link.mdx index c02a857f215..59e30b55470 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/21_create_public_database_link.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/21_create_public_database_link.mdx @@ -133,7 +133,7 @@ export LD_LIBRARY_PATH=/tmp/instantclient:$LD_LIBRARY_PATH Alternatively, you can set the value of the `oracle_home` configuration parameter in the `postgresql.conf` file. The `oracle_home` configuration parameter is an alternative to the `LD_LIBRARY_PATH` environment variable. For more details on the `oracle_home` configuration -parameter, see [configuration parameters](/../../database_administration_reference/01_introduction/05_oracle_home/). +parameter, see [configuration parameters](../../database_administrator_reference/01_introduction/05_oracle_home/). The `ORACLE_HOME` environment variable must be set and include the path to the Oracle home directory. For example, diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/31_create_queue_table.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/31_create_queue_table.mdx index 39761a31bd9..fd2b1563d2b 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/31_create_queue_table.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/31_create_queue_table.mdx @@ -48,7 +48,7 @@ The name of the queue table must be unique among queue tables in the same schema `type_name` - The name of an existing type that describes the payload of each entry in the queue table. For information about defining a type, see [CREATE TYPE](/#create_type). + The name of an existing type that describes the payload of each entry in the queue table. For information about defining a type, see [CREATE TYPE](39_create_type/). `option_name option_value` diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table.mdx index 707dd428206..39778b4a492 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table.mdx @@ -219,7 +219,7 @@ You can define table constraints and column constraints. A column constraint is ## Notes -EDB Postgres Advanced Server creates an index for each unique constraint and primary key constraint to enforce the uniqueness. Thus, you don't need to create an explicit index for primary key columns. For more information, see [`CREATE INDEX`](/#create_index). +EDB Postgres Advanced Server creates an index for each unique constraint and primary key constraint to enforce the uniqueness. Thus, you don't need to create an explicit index for primary key columns. For more information, see [`CREATE INDEX`](24_create_index/). ## Examples diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/37_create_table_as.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/37_create_table_as.mdx index 287017b1e98..cb8a42ec106 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/37_create_table_as.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/37_create_table_as.mdx @@ -34,7 +34,7 @@ CREATE [ GLOBAL TEMPORARY ] TABLE `GLOBAL TEMPORARY` - Specify to create the table as a temporary table. For details, see [`CREATE TABLE`](/#create_table). + Specify to create the table as a temporary table. For details, see [`CREATE TABLE`](36_create_table/). `table_name` @@ -46,4 +46,4 @@ CREATE [ GLOBAL TEMPORARY ] TABLE `query` - A query statement (a `SELECT` command). For a description of the allowed syntax, see [`SELECT`](/#select). + A query statement (a `SELECT` command). For a description of the allowed syntax, see [`SELECT`](71_select/). diff --git a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/43_create_view.mdx b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/43_create_view.mdx index 699333eaa02..ed876db1ec1 100644 --- a/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/43_create_view.mdx +++ b/product_docs/docs/epas/15/reference/oracle_compatibility_reference/epas_compat_sql/43_create_view.mdx @@ -41,7 +41,7 @@ If you provide a schema name, then the view is created in the specified schema. `query` - A query (that is, a `SELECT` statement) that provides the columns and rows of the view. See [`SELECT`](/#select) for information about valid queries. + A query (that is, a `SELECT` statement) that provides the columns and rows of the view. See [`SELECT`](71_select/) for information about valid queries. ## Notes diff --git a/product_docs/docs/epas/15/reference/sql_reference/index.mdx b/product_docs/docs/epas/15/reference/sql_reference/index.mdx index 3cf911adc7b..6eb9c772e7b 100644 --- a/product_docs/docs/epas/15/reference/sql_reference/index.mdx +++ b/product_docs/docs/epas/15/reference/sql_reference/index.mdx @@ -10,7 +10,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.005.html" redirects: - /epas/latest/epas_compat_reference/ #generated for docs/epas/reorg-role-use-case-mode - - ../../../epas_compat_reference/02_the_sql_language #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/epas_compat_reference/02_the_sql_language #generated for docs/epas/reorg-role-use-case-mode - ../../reference/sql_reference/02_the_sql_language/ --- diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx index 091381bf409..48425b9bdd0 100644 --- a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx +++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx @@ -21,7 +21,7 @@ Where: !!! Note - If there are no parameters to pass, you can call the procedure with an empty parameter list, or you can omit the parentheses. - - The syntax for calling a procedure is the same as in the preceding syntax diagram when executing it with the `EXEC` command in PSQL or EDB\*Plus. See [SQL reference](/../../../../reference/oracle_compatibility_reference/epas_compat_sql/63_exec) for information about the `EXEC` command. + - The syntax for calling a procedure is the same as in the preceding syntax diagram when executing it with the `EXEC` command in PSQL or EDB\*Plus. See [SQL reference](../../../../reference/oracle_compatibility_reference/epas_compat_sql/63_exec/) for information about the `EXEC` command. This example calls the procedure from an anonymous block: diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx index df0a1fbe18b..35712c77b2d 100644 --- a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx +++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx @@ -34,7 +34,7 @@ If specified, `qualifier` is the subprogram or labeled anonymous block in which schema_name.package_name.public_variable_name ``` -For more information about supported package syntax, see [Built-in packages](/epas_compat_bip_guide/03_built-in_packages/). +For more information about supported package syntax, see [Built-in packages](../../../../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/). ## Requirements diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx index 9bee8240e19..1438206d820 100644 --- a/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx +++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx @@ -42,7 +42,7 @@ Where: `objtype` is a previously defined object type. !!! Note - You can use the `CREATE TYPE` command to define a nested table type that's available to all SPL programs in the database. See [SQL reference](/../../../reference/oracle_compatibility_reference/epas_compat_sql/39_create_type/) for more information about the `CREATE TYPE` command. + You can use the `CREATE TYPE` command to define a nested table type that's available to all SPL programs in the database. See [SQL reference](../../../reference/oracle_compatibility_reference/epas_compat_sql/39_create_type/) for more information about the `CREATE TYPE` command. ## Declaring a variable diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/01_interval_range_partitioning.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/01_interval_range_partitioning.mdx index 1310eed303c..b95324f0067 100644 --- a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/01_interval_range_partitioning.mdx +++ b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/01_interval_range_partitioning.mdx @@ -14,7 +14,7 @@ The high value of a range partition, also known as the transition point, is dete Suppose an interval is set to one month. If data is inserted for two months after the current transition point, only the partition for the second month is created and not the intervening partition. For example, you can create an interval-range-partitioned table with a monthly interval and a current transition point of February 15, 2023. If you try to insert data for May 10, 2023, then the required partition for April 15 to May 15, 2023 is created and data is inserted into that partition. The partition for February 15, 2023 to March 15, 2023 and March 15, 2023 to April 15, 2023 is skipped. -For information about interval range partitioning syntax, see [CREATE TABLE...PARTITION BY](/../../../reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/#create_table_partition_by). +For information about interval range partitioning syntax, see [CREATE TABLE...PARTITION BY](../../../reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/). ## Restrictions on interval range partitioning diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/02_automatic_list_partitioning.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/02_automatic_list_partitioning.mdx index 035194c97ed..e44e9e933ad 100644 --- a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/02_automatic_list_partitioning.mdx +++ b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/02_automatic_list_partitioning.mdx @@ -10,7 +10,7 @@ Automatic list partitioning is an extension to `LIST` partitioning that allows a For example, consider a table named `sales` with a `sales_state` column that contains the existing partition values `CALIFORNIA` and `FLORIDA`. Each of the `sales_state` values increases with a rise in the statewise sales. A sale in a new state, for example, `INDIANA` and `OHIO`, requires creating new partitions. If you implement automatic list partitioning, the new partitions `INDIANA` and `OHIO` are automatically created, and data is entered into the `sales` table. -For information about automatic list partitioning syntax, see [CREATE TABLE...PARTITION BY](/../../../reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/#create_table_partition_by). +For information about automatic list partitioning syntax, see [CREATE TABLE...PARTITION BY](../../../reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/). ## Restrictions for automatic list partitioning diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/index.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/index.mdx index a42768a9f7c..54678857595 100644 --- a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/index.mdx +++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/index.mdx @@ -7,7 +7,7 @@ redirects: -These configuration parameters are for use with the EDB Postgres Advanced Server database [auditing feature](/../../../epas_security_guide/05_edb_audit_logging/). +These configuration parameters are for use with the EDB Postgres Advanced Server database [auditing feature](../../../../epas_security_guide/05_edb_audit_logging/).
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx index ec08ae632bb..41d34a503da 100644 --- a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx +++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx @@ -344,7 +344,7 @@ Use the `edbldr.empty_csv_field` parameter to specify how EDB\*Loader treats an | `empty_string` | An empty field is treated as a string of length zero. | | `pgsql` | An empty field is treated as a `NULL` if it doesn't contain quotes and as an empty string if it contains quotes. | -For more information about the `edbldr.empty_csv_field` parameter in EDB\*Loader, see [Tools, utilities, and components](/../../02_edb_loader). +For more information about the `edbldr.empty_csv_field` parameter in EDB\*Loader, see [Tools, utilities, and components](../../02_edb_loader). ## utl_encode.uudecode_redwood diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/14_audit_archiver.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/14_audit_archiver.mdx index 05af7eacce6..bc83700ebe8 100644 --- a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/14_audit_archiver.mdx +++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/14_audit_archiver.mdx @@ -6,7 +6,7 @@ redirects: -These configuration parameters are used by the EDB Postgres Advanced Server database [audit archiving feature](/../../../epas_security_guide/05_edb_audit_logging/08_audit_log_archiving/). +These configuration parameters are used by the EDB Postgres Advanced Server database [audit archiving feature](../../../epas_security_guide/05_edb_audit_logging/08_audit_log_archiving/). ## edb_audit_archiver diff --git a/product_docs/docs/epas/16/database_administration/02_edb_loader/index.mdx b/product_docs/docs/epas/16/database_administration/02_edb_loader/index.mdx index 008e4971961..8e9503d26d5 100644 --- a/product_docs/docs/epas/16/database_administration/02_edb_loader/index.mdx +++ b/product_docs/docs/epas/16/database_administration/02_edb_loader/index.mdx @@ -9,6 +9,8 @@ navigation: - using_edb_loader - building_the_control_file - invoking_edb_loader +redirects: + - /epas/latest/epas_compat_tools_guide/02_edb_loader legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.16.html" diff --git a/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/configuring_epas.mdx b/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/configuring_epas.mdx index e59c6a2821e..0fcb6378cc2 100644 --- a/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/configuring_epas.mdx +++ b/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/configuring_epas.mdx @@ -15,7 +15,7 @@ You can easily update parameters that determine the behavior of EDB Postgres Adv - The `pg_hba.conf` file specifies your preferences for network authentication and authorization. - The `pg_ident.conf` file maps operating system identities (user names) to EDB Postgres Advanced Server identities (roles) when using `ident`-based authentication. -For more information about modifying the `postgresql.conf` and `pg_hba.conf` files, see [Setting parameters](../../../../database_administration/01_configuration_parameters/01_setting_new_parameters). +For more information about modifying the `postgresql.conf` and `pg_hba.conf` files, see [Setting parameters](../../../database_administration/01_configuration_parameters/01_setting_new_parameters/). You can use your editor of choice to open a configuration file. On Windows, you can navigate through the **EDB Postgres** menu to open a file. diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/ecpgplus_statements.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/ecpgplus_statements.mdx index 4e1811f9467..52183d3e342 100644 --- a/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/ecpgplus_statements.mdx +++ b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/ecpgplus_statements.mdx @@ -68,7 +68,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.101.html" redirects: - /epas/latest/ecpgplus_guide/07_reference/ #generated for docs/epas/reorg-role-use-case-mode - - ../../../application_programming/ecpgplus_guide/07_reference/ + - /epas/latest/application_programming/ecpgplus_guide/07_reference/ --- diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/index.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/index.mdx index 26063d266b0..c855e0c154e 100644 --- a/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/index.mdx +++ b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/index.mdx @@ -67,9 +67,6 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.100.html" - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.102.html" - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.101.html" -redirects: - - ../../../ecpgplus_guide/07_reference #generated for docs/epas/reorg-role-use-case-mode - - ../../../application_programming/ecpgplus_guide/07_reference/ --- diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/index.mdx index fbd0abd39db..ea18d15e874 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/index.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/index.mdx @@ -45,7 +45,7 @@ ALTER TABLE SET SUBPARTITION TEMPLATE (); You can use the `ALTER TABLE… SET SUBPARTITION TEMPLATE` command to update the subpartition template for range, list, or hash-partitioned table. If you're specifying a subpartition descriptor for a partition, use a subpartition descriptor instead of a subpartition template. You can use the subpartition template whenever a subpartition descriptor isn't specified for a partition. If you don't specify either the subpartition descriptor or subpartition template, then by default a single subpartition is created. -For more information about creating a subpartition template, see [CREATE TABLE...PARTITION BY](../../04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/#create_table_partition_by). +For more information about creating a subpartition template, see [CREATE TABLE...PARTITION BY](../../04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/). !!! Note The partitions added to a table after invoking `ALTER TABLE… SET SUBPARTITION TEMPLATE` command use the new `SUBPARTITION TEMPLATE`. diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/20_to_refcursor.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/20_to_refcursor.mdx index ca3536b3ac1..9026c136f1a 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/20_to_refcursor.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/20_to_refcursor.mdx @@ -1,7 +1,7 @@ --- title: "TO_REFCURSOR" redirects: - - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/17_open_cursor/ #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/20_to_refcursor/ #generated for docs/epas/reorg-role-use-case-mode --- The `TO_REFCURSOR` function transforms an open cursor into a REF CURSOR for use in SQL statements. This program is only used with SELECT cursors. diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/index.mdx index 96a8a7e1ae6..998d0219e04 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/index.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/index.mdx @@ -5,7 +5,7 @@ indexCards: simple description: "Listing of the catalog views support provided by EDB Postgres Advanced Server" redirects: - /epas/latest/epas_compat_cat_views/ #generated for docs/epas/reorg-role-use-case-mode - - ../../../../epas_compat_ora_dev_guide/08_oracle_catalog_views/ + - /epas/latest/epas_compat_ora_dev_guide/08_oracle_catalog_views/ --- Catalog views provide information about database objects. There are two catagories of catalog views: diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns.mdx index 6a57d62ab4a..b919b3b35bf 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.175.html" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/09_all_ind_columns/ + - /epas/latest/epas_compat_cat_views/09_all_ind_columns/ --- diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/19_all_source.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/19_all_source.mdx index 5a78401a66d..e8850148a5b 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/19_all_source.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/19_all_source.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.183.html" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/19_all_source/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/19_all_source/ + - /epas/latest/epas_compat_cat_views/19_all_source/ --- diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns.mdx index 00567bac4ef..b49f01eed69 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.186.html" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/22_all_tab_columns/ + - /epas/latest/epas_compat_cat_views/22_all_tab_columns/ --- diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs.mdx index 3274d3a26be..fb4943a7db9 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs.mdx @@ -2,7 +2,7 @@ title: "ALL_TAB_PRIVS" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/25_all_tab_privs/ + - /epas/latest/epas_compat_cat_views/25_all_tab_privs/ --- diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/37_dba_directories.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/37_dba_directories.mdx index f46df25c2f7..08ee8ec9c39 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/37_dba_directories.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/37_dba_directories.mdx @@ -5,7 +5,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.138.html" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/37_dba_directories/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/37_dba_directories/ + - /epas/latest/epas_compat_cat_views/37_dba_directories/ --- diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/72_user_jobs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/72_user_jobs.mdx index 4a7fd1995bc..f4e6c7d14cd 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/72_user_jobs.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/72_user_jobs.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.228.html" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/72_user_jobs/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/72_user_jobs/ + - /epas/latest/epas_compat_cat_views/72_user_jobs/ --- diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms.mdx index 50f2cbf04d8..a2ee6eb3e6a 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.237.html" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/82_user_synonyms/ + - /epas/latest/epas_compat_cat_views/82_user_synonyms/ --- diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions.mdx index a7003d67bb9..368dff07edf 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.239.html" redirects: - /epas/latest/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions/ #generated for docs/epas/reorg-role-use-case-mode - - /epas/15/epas_compat_cat_views/84_user_tab_partitions/ + - /epas/latest/epas_compat_cat_views/84_user_tab_partitions/ --- diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/21_create_public_database_link.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/21_create_public_database_link.mdx index e3920aeae4f..c05196e1f3a 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/21_create_public_database_link.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/21_create_public_database_link.mdx @@ -133,7 +133,7 @@ export LD_LIBRARY_PATH=/tmp/instantclient:$LD_LIBRARY_PATH Alternatively, you can set the value of the `oracle_home` configuration parameter in the `postgresql.conf` file. The `oracle_home` configuration parameter is an alternative to the `LD_LIBRARY_PATH` environment variable. For more details on the `oracle_home` configuration -parameter, see [configuration parameters](/../../database_administration_reference/01_introduction/05_oracle_home/). +parameter, see [configuration parameters](../../database_administrator_reference/01_introduction/05_oracle_home/). The `ORACLE_HOME` environment variable must be set and include the path to the Oracle home directory. For example, diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/31_create_queue_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/31_create_queue_table.mdx index 39761a31bd9..fd2b1563d2b 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/31_create_queue_table.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/31_create_queue_table.mdx @@ -48,7 +48,7 @@ The name of the queue table must be unique among queue tables in the same schema `type_name` - The name of an existing type that describes the payload of each entry in the queue table. For information about defining a type, see [CREATE TYPE](/#create_type). + The name of an existing type that describes the payload of each entry in the queue table. For information about defining a type, see [CREATE TYPE](39_create_type/). `option_name option_value` diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table.mdx index 707dd428206..39778b4a492 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table.mdx @@ -219,7 +219,7 @@ You can define table constraints and column constraints. A column constraint is ## Notes -EDB Postgres Advanced Server creates an index for each unique constraint and primary key constraint to enforce the uniqueness. Thus, you don't need to create an explicit index for primary key columns. For more information, see [`CREATE INDEX`](/#create_index). +EDB Postgres Advanced Server creates an index for each unique constraint and primary key constraint to enforce the uniqueness. Thus, you don't need to create an explicit index for primary key columns. For more information, see [`CREATE INDEX`](24_create_index/). ## Examples diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/37_create_table_as.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/37_create_table_as.mdx index 287017b1e98..cb8a42ec106 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/37_create_table_as.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/37_create_table_as.mdx @@ -34,7 +34,7 @@ CREATE [ GLOBAL TEMPORARY ] TABLE `GLOBAL TEMPORARY` - Specify to create the table as a temporary table. For details, see [`CREATE TABLE`](/#create_table). + Specify to create the table as a temporary table. For details, see [`CREATE TABLE`](36_create_table/). `table_name` @@ -46,4 +46,4 @@ CREATE [ GLOBAL TEMPORARY ] TABLE `query` - A query statement (a `SELECT` command). For a description of the allowed syntax, see [`SELECT`](/#select). + A query statement (a `SELECT` command). For a description of the allowed syntax, see [`SELECT`](71_select/). diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/43_create_view.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/43_create_view.mdx index 699333eaa02..ed876db1ec1 100644 --- a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/43_create_view.mdx +++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/43_create_view.mdx @@ -41,7 +41,7 @@ If you provide a schema name, then the view is created in the specified schema. `query` - A query (that is, a `SELECT` statement) that provides the columns and rows of the view. See [`SELECT`](/#select) for information about valid queries. + A query (that is, a `SELECT` statement) that provides the columns and rows of the view. See [`SELECT`](71_select/) for information about valid queries. ## Notes diff --git a/product_docs/docs/epas/16/reference/sql_reference/index.mdx b/product_docs/docs/epas/16/reference/sql_reference/index.mdx index 3cf911adc7b..6eb9c772e7b 100644 --- a/product_docs/docs/epas/16/reference/sql_reference/index.mdx +++ b/product_docs/docs/epas/16/reference/sql_reference/index.mdx @@ -10,7 +10,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.005.html" redirects: - /epas/latest/epas_compat_reference/ #generated for docs/epas/reorg-role-use-case-mode - - ../../../epas_compat_reference/02_the_sql_language #generated for docs/epas/reorg-role-use-case-mode + - /epas/latest/epas_compat_reference/02_the_sql_language #generated for docs/epas/reorg-role-use-case-mode - ../../reference/sql_reference/02_the_sql_language/ --- diff --git a/product_docs/docs/eprs/7/01_introduction/04_permitted_conf_and_permutations.mdx b/product_docs/docs/eprs/7/01_introduction/04_permitted_conf_and_permutations.mdx index 58ddd45c6dd..53fc550019c 100644 --- a/product_docs/docs/eprs/7/01_introduction/04_permitted_conf_and_permutations.mdx +++ b/product_docs/docs/eprs/7/01_introduction/04_permitted_conf_and_permutations.mdx @@ -26,7 +26,7 @@ EDB Postgres Advanced Server supports two compatibility configuration modes of o - Oracle-compatible configuration mode. Operations are performed using Oracle syntax and semantics for data types, functions, database object creation, and so forth. This mode is useful when your applications are migrated from Oracle or you want your applications built in an Oracle-compatible fashion. - PostgreSQL-compatible configuration mode. Operations are performed using native PostgreSQL syntax and semantics. This mode is useful when your applications are migrated from PostgreSQL or you want your applications built in a PostgreSQL-compatible fashion. -For more information on features supported in Oracle compatible configuration mode, see [Database compatibility for Oracle developers](/epas/latest/epas_compat_ora_dev_guide/). +For more information on features supported in Oracle compatible configuration mode, see [Database compatibility for Oracle developers](/epas/latest/fundamentals/epas_fundamentals/epas_compat_ora_dev_guide/). Select the compatibility configuration mode when you install EDB Postgees Advanced Server. diff --git a/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/08_snapshot_replication.mdx b/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/08_snapshot_replication.mdx index 45bdf9ff500..54549d2174d 100644 --- a/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/08_snapshot_replication.mdx +++ b/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/08_snapshot_replication.mdx @@ -13,7 +13,7 @@ In snapshot replication, the target tables are completely reloaded from the sour If the target table (regardless of database type) contains a large object data type such as `BYTEA`, `BLOB`, or `CLOB`, then rows are loaded one at a time per batch using an `INSERT` statement. This approach avoids a heap space error resulting from potentially large rows. Loading time can be decreased by allowing multiple inserts per batch, which you can do by adjusting the configuration option `lobBatchSize` described in [Optimizing snapshot replication](../../05_smr_operation/08_optimizing_performance/01_optimizing_snapshot_replication/#optimizing_snapshot_replication). !!! Note - EDB Postgres Advanced Server supports a number of aliases for data types. Such aliases that translate to `BYTEA` are treated as large object data types. See [SQL reference](/epas/latest/epas_compat_reference/) for a listing of EDB Postgres Advanced Server data types. (See [Database compatibility for Oracle developers](/epas/latest/epas_compat_ora_dev_guide/) for EDB Postgres Advanced Server version 9.5 or earlier versions.) + EDB Postgres Advanced Server supports a number of aliases for data types. Such aliases that translate to `BYTEA` are treated as large object data types. See [SQL reference](/epas/14/epas_compat_reference/) for a listing of EDB Postgres Advanced Server data types. (See [Database compatibility for Oracle developers](/epas/latest/fundamentals/epas_fundamentals/epas_compat_ora_dev_guide/) for EDB Postgres Advanced Server version 9.5 or earlier versions.) Under certain circumstances, the corresponding Postgres target table created for certain types of Oracle partitioned tables is a set of inherited tables. In these cases, the `SQL DELETE` statement is used on the inherited child tables instead of truncation. See [Replicating Oracle partitioned tables](../../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables/#replicate_oracle_partitioned_tables). diff --git a/product_docs/docs/eprs/7/05_smr_operation/05_managing_subscription.mdx b/product_docs/docs/eprs/7/05_smr_operation/05_managing_subscription.mdx index 02595d09ac6..76cbe3bee5d 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/05_managing_subscription.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/05_managing_subscription.mdx @@ -20,11 +20,11 @@ This information is saved in the replication system metadata when you create a s You can update the metadata stored for the subscription server, the subscription database definition, and subscriptions to keep the information consistent with the actual replication system environment. !!! Note - For managing a publication of a replication system, see [Managing a publication](../../07_common_operations/06_managing_publication/#managing_publication). + For managing a publication of a replication system, see [Managing a publication](../07_common_operations/06_managing_publication/#managing_publication). ## Update a subscription server -When you register a subscription server in the Replication Server console, you can choose to save the subscription server’s network location (IP address and port number), admin user name, and encrypted password in a server login file on the computer on which you're running the Replication Server console. See [Saving server login information](../../04_intro_xdb_console/#saving_server_login_info) for details. +When you register a subscription server in the Replication Server console, you can choose to save the subscription server’s network location (IP address and port number), admin user name, and encrypted password in a server login file on the computer on which you're running the Replication Server console. See [Saving server login information](../04_intro_xdb_console/#saving_server_login_info) for details. To update the subscription server, first open the Replication Server console. The subscription server whose login information you want to alter in the server login file must appear as a Subscription Server node in the replication tree. diff --git a/product_docs/docs/eprs/7/07_common_operations/10_replicating_postgres_partitioned_tables.mdx b/product_docs/docs/eprs/7/07_common_operations/10_replicating_postgres_partitioned_tables.mdx index 952c7ded0e9..84b396f904a 100644 --- a/product_docs/docs/eprs/7/07_common_operations/10_replicating_postgres_partitioned_tables.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/10_replicating_postgres_partitioned_tables.mdx @@ -12,7 +12,7 @@ The following are the partitioning techniques: - Postgres declarative partitioning (applies to both PostgreSQL and EDB Postgres Advanced Server version 10 and later) - Postgres table inheritance (applies to both PostgreSQL and EDB Postgres Advanced Server) -If you're using EDB Postgres Advanced Server, you can create partitioned tables using the `CREATE TABLE` statement with partitioning syntax compatible with Oracle databases. For information on partitioning compatible with Oracle databases, see [Table partitioning](../../../epas/latest/epas_compat_table_partitioning/). +If you're using EDB Postgres Advanced Server, you can create partitioned tables using the `CREATE TABLE` statement with partitioning syntax compatible with Oracle databases. For information on partitioning compatible with Oracle databases, see [Table partitioning](/epas/latest/application_programming/epas_compat_table_partitioning/). If you're using version 10 or later of PostgreSQL or EDB Postgres Advanced Server, you can use declarative partitioning to create partitioned tables. The `CREATE TABLE` syntax for creating a declarative partitioned table is similar to the partitioning compatible with Oracle databases. However, you must create the individual partitions of the declarative partitioned table separately with their own `CREATE TABLE` statements. diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx index 55084edb365..6106031dd0c 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx @@ -47,7 +47,7 @@ The `views` parameter applies only for a snapshot-only publication. It's ignored !!! Note - Column mappings are applied when you create subscriptions. If you add a table which qualifies for column mapping to the related publication, then Replication Server applies the column mapping for the newly added table. For more information on column mappings, see [Creating a subscription](/36_creating_subscription_cli). + Column mappings are applied when you create subscriptions. If you add a table which qualifies for column mapping to the related publication, then Replication Server applies the column mapping for the newly added table. For more information on column mappings, see [Creating a subscription](36_creating_subscription_cli). !!! ## Parameters diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables.mdx index 922278d3519..f33210ca32c 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables.mdx @@ -26,7 +26,7 @@ The most common types of Oracle table partitioning are the following: - Truncate operation on child partition table: You can truncate child partitions in Oracle using the `ALTER` command. Replication Server doesn't support the `ALTER` command when the source database type is Oracle or SQL server. In this case, don't truncate child partition tables outside the Replication Server, leading to data consistency across nodes. !!! Note - If you're using EDB Postgres Advanced Server, table partitioning using Oracle-compatible table partitioning syntax is an available feature. See the section on table partitioning in the [Database compatibility for Oracle developers](/epas/latest/epas_compat_ora_dev_guide/) for information. See [Replicating Postgres partitioned tables](../../../07_common_operations/10_replicating_postgres_partitioned_tables/#replicating_postgres_partitioned_tables) for information on including Postgres partitioned tables in a replication system. The `importPartitionAsTable` option described here applies only to table partitioning in an Oracle database. + If you're using EDB Postgres Advanced Server, table partitioning using Oracle-compatible table partitioning syntax is an available feature. See the section on table partitioning in the [Database compatibility for Oracle developers](/epas/latest/fundamentals/epas_fundamentals/epas_compat_ora_dev_guide/) for information. See [Replicating Postgres partitioned tables](../../../07_common_operations/10_replicating_postgres_partitioned_tables/#replicating_postgres_partitioned_tables) for information on including Postgres partitioned tables in a replication system. The `importPartitionAsTable` option described here applies only to table partitioning in an Oracle database. The `importPartitionAsTable` option controls what happens when an Oracle partitioned table is part of the publication. diff --git a/product_docs/docs/eprs/7/installing/installing_jdbc_driver.mdx b/product_docs/docs/eprs/7/installing/installing_jdbc_driver.mdx index 931fe13675c..c99b0669673 100644 --- a/product_docs/docs/eprs/7/installing/installing_jdbc_driver.mdx +++ b/product_docs/docs/eprs/7/installing/installing_jdbc_driver.mdx @@ -6,7 +6,7 @@ title: "Installing a JDBC driver" The JDBC driver you use depends on the database you're using. If you're using: -- **EDB Postgres Advanced Server**, use the EDB JDBC driver. To download the latest driver, see [EDB Connectors](https://enterprisedb.com/software-downloads-postgres#edb-connectors) on the EDB Downloads page. For installation instructions, see [Installing and configuring EDB JDBC Connector](/jdbc_connector/latest/04_installing_and_configuring_the_jdbc_connector/). +- **EDB Postgres Advanced Server**, use the EDB JDBC driver. To download the latest driver, see [EDB Connectors](https://enterprisedb.com/software-downloads-postgres#edb-connectors) on the EDB Downloads page. For installation instructions, see [Installing and configuring EDB JDBC Connector](/jdbc_connector/latest/installing/). - **PostgreSQL**, use the PostgreSQL JDBC driver. To download the latest supported driver (Java 8), see the [JDBC drivers section](https://jdbc.postgresql.org/download/) on the PostgreSQL Downloads page. diff --git a/product_docs/docs/eprs/7/installing/windows.mdx b/product_docs/docs/eprs/7/installing/windows.mdx index 1981241c7ef..8aea144fbdd 100644 --- a/product_docs/docs/eprs/7/installing/windows.mdx +++ b/product_docs/docs/eprs/7/installing/windows.mdx @@ -32,7 +32,7 @@ Proceed to [Using the graphical installer](#using-the-graphical-installer). ## Using Stack Builder or StackBuilder Plus -If you're using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installer/03_using_stackbuilder/). +If you're using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installing/03_using_stackbuilder/). 1. In Stack Builder, follow the prompts until you get to the module selection page. @@ -42,7 +42,7 @@ If you're using PostgreSQL, you can invoke the graphical installer with Stack Bu 1. Proceed to [Using the graphical installer](#using-the-graphical-installer). -If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). +If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/installing/windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). 1. In StackBuilder Plus, follow the prompts until you get to the module selection page. diff --git a/product_docs/docs/hadoop_data_adapter/2/configuring.mdx b/product_docs/docs/hadoop_data_adapter/2/configuring.mdx index 1de99c8528c..3a145596d3c 100644 --- a/product_docs/docs/hadoop_data_adapter/2/configuring.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/configuring.mdx @@ -23,7 +23,7 @@ Modify the configuration file, adding the `hdfs_fdw.jvmpath` parameter to the en If you're using EDB Postgres Advanced Server and have a `DATE` column in your database, you must set `edb_redwood_date = OFF` in the `postgresql.conf` file. -After setting the parameter values, restart the Postgres server. For detailed information about controlling the service on an EDB Postgres Advanced Server host, see the [EDB Postgres Advanced Server documentation](../epas/latest). +After setting the parameter values, restart the Postgres server. For detailed information about controlling the service on an EDB Postgres Advanced Server host, see the [EDB Postgres Advanced Server documentation](/epas/latest). Before using the Hadoop Foreign Data Wrapper: diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/05a_using_advanced_queueing.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/05a_using_advanced_queueing.mdx index a76f04ad66a..cdd831b1873 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/05a_using_advanced_queueing.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/05a_using_advanced_queueing.mdx @@ -7,7 +7,7 @@ title: "Using advanced queueing" EDB Postgres Advanced Server advanced queueing provides message queueing and message processing for the EDB Postgres Advanced Server database. User-defined messages are stored in a queue, and a collection of queues is stored in a queue table. You must first create a queue table before creating a queue that depends on it. -On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add or remove messages from a queue or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, see the [EDB Postgres Advanced Server documentation](/epas/latest/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/). +On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add or remove messages from a queue or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, see the [DBMS_AQ](/epas/latest/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/). On the client side, the application uses EDB-JDBC driver's JMS API to enqueue and dequeue message. diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/windows.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/windows.mdx index 2409e792f5f..70b3d598c36 100644 --- a/product_docs/docs/jdbc_connector/42.5.4.1/installing/windows.mdx +++ b/product_docs/docs/jdbc_connector/42.5.4.1/installing/windows.mdx @@ -30,9 +30,9 @@ Proceed to [Using the graphical installer](#using-the-graphical-installer). ## Using Stack Builder or StackBuilder Plus -If you're using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installer/03_using_stackbuilder/). +If you're using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installing/03_using_stackbuilder/). -If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). +If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/installing/windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). 1. In Stack Builder or StackBuilder Plus, follow the prompts until you get to the module selection page. diff --git a/product_docs/docs/livecompare/2/bdr_support.mdx b/product_docs/docs/livecompare/2/bdr_support.mdx index 031c8ea012f..7585dd5b5fb 100644 --- a/product_docs/docs/livecompare/2/bdr_support.mdx +++ b/product_docs/docs/livecompare/2/bdr_support.mdx @@ -103,7 +103,7 @@ To enable pglogical metadata fetch instead of PGD, set `logical_replication_mode Using replication sets in PGD, you can configure specific tables to include in the PGD replication. You can also specify the nodes to receive data from these tables by configuring the node to subscribe to the replication set the table belongs to. This setting allows for different architectures such as PGD sharding and the use of PGD witness nodes. -A PGD witness is a regular PGD node that doesn't replicate any DML from other nodes. The purpose of the witness is to provide quorum in Raft Consensus voting. (For details on the PGD witness node, see [Witness nodes](/pgd/latest/nodes/#witness-nodes) in the PGD documentation.) Replication set configuration determines whether the witness replicates DDLs. This means that there are two types of PGD witnesses: +A PGD witness is a regular PGD node that doesn't replicate any DML from other nodes. The purpose of the witness is to provide quorum in Raft Consensus voting. (For details on the PGD witness node, see [Witness nodes](/pgd/latest/node_management/witness_nodes/) in the PGD documentation.) Replication set configuration determines whether the witness replicates DDLs. This means that there are two types of PGD witnesses: - A completely empty node, without any data nor tables - A node that replicates DDL from other nodes, so it has empty tables diff --git a/product_docs/docs/migration_toolkit/55/06_building_toolkit.properties_file.mdx b/product_docs/docs/migration_toolkit/55/06_building_toolkit.properties_file.mdx index b89aad31b72..fd0f0cd7426 100644 --- a/product_docs/docs/migration_toolkit/55/06_building_toolkit.properties_file.mdx +++ b/product_docs/docs/migration_toolkit/55/06_building_toolkit.properties_file.mdx @@ -157,7 +157,7 @@ The URL contains the following information: - `TARGET_DB_PASSWORD` — Contains the password of the specified user. -- `sslmode` — Either "require" or "verify-full". See [Recommended settings for SSL mode](../../../biganimal/latest/using_cluster/02_connect_to_cluster/#recommended-settings-for-ssl-mode). Listed at the end of the **Service URI** value on the **Connect** tab in the BigAnimal portal. +- `sslmode` — Either "require" or "verify-full". See [Recommended settings for SSL mode](../../../biganimal/latest/using_cluster/02_connecting_your_cluster/connecting_from_a_client/#recommended-settings-for-ssl-mode). Listed at the end of the **Service URI** value on the **Connect** tab in the BigAnimal portal. ## Defining an Oracle URL diff --git a/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx b/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx index b0d38582974..00f1d46fd45 100644 --- a/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx +++ b/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx @@ -565,7 +565,7 @@ This example uses the `dblink_ora` `COPY API` to migrate all tables from the `HR $./runMTK.sh -copyViaDBLinkOra -allTables HR ``` -The target EDB Postgres Advanced Server database must have `dblink_ora` installed and configured. See [dblink_ora](/epas/latest/epas_compat_ora_dev_guide/06_dblink_ora). +The target EDB Postgres Advanced Server database must have `dblink_ora` installed and configured. See [dblink_ora](/epas/latest/working_with_oracle_data/06_dblink_ora/). `-allDBLinks [link_Name_1=password_1,link_Name_2=password_2,...]` diff --git a/product_docs/docs/migration_toolkit/55/installing/installing_jdbc_driver.mdx b/product_docs/docs/migration_toolkit/55/installing/installing_jdbc_driver.mdx index 9b5a27c847f..0d6bdb6f9e1 100644 --- a/product_docs/docs/migration_toolkit/55/installing/installing_jdbc_driver.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/installing_jdbc_driver.mdx @@ -10,7 +10,7 @@ Migration Toolkit requires Java version 1.8.0 or later. ## Choosing a driver Which JDBC driver you use depends on the what database you are migrating from or to: -- If you're migrating to or from EDB Postgres Advanced Server, use the EDB JDBC driver. To download the latest driver, see [EDB Connectors](https://enterprisedb.com/software-downloads-postgres#edb-connectors) on the EDB Downloads page. For installation instructions, see [Installing and configuring EDB JDBC Connector](/jdbc_connector/latest/04_installing_and_configuring_the_jdbc_connector/). +- If you're migrating to or from EDB Postgres Advanced Server, use the EDB JDBC driver. To download the latest driver, see [EDB Connectors](https://enterprisedb.com/software-downloads-postgres#edb-connectors) on the EDB Downloads page. For installation instructions, see [Installing and configuring EDB JDBC Connector](/jdbc_connector/latest/installing/). !!! Note The EDB JDBC driver is not available for Mac OS. diff --git a/product_docs/docs/migration_toolkit/55/installing/macos.mdx b/product_docs/docs/migration_toolkit/55/installing/macos.mdx index 94a9f3a6028..438f72a6488 100644 --- a/product_docs/docs/migration_toolkit/55/installing/macos.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/macos.mdx @@ -25,7 +25,7 @@ export JAVA_HOME=$(/usr/libexec/java_home) ## Using Stack Builder -If you are using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installer/03_using_stackbuilder/). +If you are using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installing/03_using_stackbuilder/). 1. In Stack Builder, follow the prompts until you get to the module selection page. diff --git a/product_docs/docs/migration_toolkit/55/installing/windows.mdx b/product_docs/docs/migration_toolkit/55/installing/windows.mdx index b0cacea5b00..343847e5ce4 100644 --- a/product_docs/docs/migration_toolkit/55/installing/windows.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/windows.mdx @@ -37,7 +37,7 @@ Proceed to the [Using the graphical installer](#using-the-graphical-installer) s ## Using Stack Builder or StackBuilder Plus -If you are using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installer/03_using_stackbuilder/). +If you are using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installing/03_using_stackbuilder/). 1. In Stack Builder, follow the prompts until you get to the module selection page. @@ -49,7 +49,7 @@ If you are using PostgreSQL, you can invoke the graphical installer with Stack B 1. Proceed to [Using the graphical installer](#using-the-graphical-installer). -If you are using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). +If you are using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/installing/windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). 1. In StackBuilder Plus, follow the prompts until you get to the module selection page. diff --git a/product_docs/docs/net_connector/4.0.10.2/12_using_advanced_queueing.mdx b/product_docs/docs/net_connector/4.0.10.2/12_using_advanced_queueing.mdx index 8c62de28412..c3b680ade3e 100644 --- a/product_docs/docs/net_connector/4.0.10.2/12_using_advanced_queueing.mdx +++ b/product_docs/docs/net_connector/4.0.10.2/12_using_advanced_queueing.mdx @@ -10,7 +10,7 @@ legacyRedirectsGenerated: EDB Postgres Advanced Server Advanced Queueing provides message queueing and message processing for the Advanced Server database. User-defined messages are stored in a queue; a collection of queues is stored in a queue table. You should first create a queue table before creating a queue that is dependent on it. -On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add or remove messages from a queue, or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, click [here](https://www.enterprisedb.com/docs/en/11.0/EPAS_BIP_Guide_v11/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.14.html#pID0E01HG0HA). +On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add or remove messages from a queue, or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, click [here](https://www.enterprisedb.com/docs/en/11.0/EPAS_BIP_Guide_v11/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.14.html). On the client side, application uses EDB.NET driver to enqueue/dequeue message. @@ -488,5 +488,5 @@ The `EDBAQVisibility` class represents the visibility options available. | On_Commit | The enqueue/dequeue is part of the current transaction. | !!! Note - - To review the default options for the above parameters, click [here](https://www.enterprisedb.com/docs/en/11.0/EPAS_BIP_Guide_v11/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.14.html#pID0E01HG0HA/). + - To review the default options for the above parameters, click [here](https://www.enterprisedb.com/docs/en/11.0/EPAS_BIP_Guide_v11/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.14.html). - EDB Advanced Queueing functionality uses user-defined types for calling enqueue/dequeue operations. `Server Compatibility Mode=NoTypeLoading` cannot be used with Advanced Queueing because `NoTypeLoading` will not load any user-defined types. diff --git a/product_docs/docs/net_connector/4.1.6.1/12_using_advanced_queueing.mdx b/product_docs/docs/net_connector/4.1.6.1/12_using_advanced_queueing.mdx index f6a807ae432..8ed208fc57d 100644 --- a/product_docs/docs/net_connector/4.1.6.1/12_using_advanced_queueing.mdx +++ b/product_docs/docs/net_connector/4.1.6.1/12_using_advanced_queueing.mdx @@ -10,7 +10,7 @@ legacyRedirectsGenerated: EDB Postgres Advanced Server Advanced Queueing provides message queueing and message processing for the Advanced Server database. User-defined messages are stored in a queue; a collection of queues is stored in a queue table. You should first create a queue table before creating a queue that is dependent on it. -On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add or remove messages from a queue, or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, click [here](https://www.enterprisedb.com/docs/en/11.0/EPAS_BIP_Guide_v11/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.14.html#pID0E01HG0HA). +On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add or remove messages from a queue, or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, click [here](https://www.enterprisedb.com/docs/en/11.0/EPAS_BIP_Guide_v11/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.14.html). On the client side, application uses EDB.NET driver to enqueue/dequeue message. @@ -488,5 +488,5 @@ The `EDBAQVisibility` class represents the visibility options available. | On_Commit | The enqueue/dequeue is part of the current transaction. | !!! Note - - To review the default options for the above parameters, click [here](https://www.enterprisedb.com/docs/en/11.0/EPAS_BIP_Guide_v11/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.14.html#pID0E01HG0HA/). + - To review the default options for the above parameters, click [here](https://www.enterprisedb.com/docs/en/11.0/EPAS_BIP_Guide_v11/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.14.html). - EDB Advanced Queueing functionality uses user-defined types for calling enqueue/dequeue operations. `Server Compatibility Mode=NoTypeLoading` cannot be used with Advanced Queueing because `NoTypeLoading` will not load any user-defined types. diff --git a/product_docs/docs/net_connector/5.0.7.1/12_using_advanced_queueing.mdx b/product_docs/docs/net_connector/5.0.7.1/12_using_advanced_queueing.mdx index 1cc0b985b04..83cb3d017df 100644 --- a/product_docs/docs/net_connector/5.0.7.1/12_using_advanced_queueing.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/12_using_advanced_queueing.mdx @@ -7,13 +7,13 @@ title: "Using advanced queueing" EDB Postgres Advanced Server advanced queueing provides message queueing and message processing for the EDB Postgres Advanced Server database. User-defined messages are stored in a queue. A collection of queues is stored in a queue table. Create a queue table before creating a queue that depends on it. -On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add or remove messages from a queue or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/#pID0E01HG0HA). +On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add or remove messages from a queue or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, see [DBMS_AQ](/epas/latest/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/). On the client side, the application uses the EDB.NET driver to enqueue and dequeue messages. ## Enqueueing or dequeueing a message -For more information about using EDB Postgres Advanced Server's advanced queueing functionality, see the [Database Compatibility for Oracle Developers Built-in Package Guide](/epas/latest/epas_compat_bip_guide/). +For more information about using EDB Postgres Advanced Server's advanced queueing functionality, see the [Database Compatibility for Oracle Developers Built-in Package Guide](/epas/latest/reference/oracle_compatibility_reference/epas_compat_bip_guide/). ### Server-side setup @@ -486,5 +486,5 @@ The `EDBAQVisibility` class represents the visibility options available. | On_Commit | The enqueue/dequeue is part of the current transaction. | !!! Note -- To review the default options for these parameters, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/#pID0E01HG0HA/). +- To review the default options for these parameters, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/). - EDB advanced queueing functionality uses user-defined types for calling enqueue/dequeue operations. `Server Compatibility Mode=NoTypeLoading` can't be used with advanced queueing because `NoTypeLoading` doesn't load any user-defined types. diff --git a/product_docs/docs/net_connector/6.0.2.1/12_using_advanced_queueing.mdx b/product_docs/docs/net_connector/6.0.2.1/12_using_advanced_queueing.mdx index 1cc0b985b04..83cb3d017df 100644 --- a/product_docs/docs/net_connector/6.0.2.1/12_using_advanced_queueing.mdx +++ b/product_docs/docs/net_connector/6.0.2.1/12_using_advanced_queueing.mdx @@ -7,13 +7,13 @@ title: "Using advanced queueing" EDB Postgres Advanced Server advanced queueing provides message queueing and message processing for the EDB Postgres Advanced Server database. User-defined messages are stored in a queue. A collection of queues is stored in a queue table. Create a queue table before creating a queue that depends on it. -On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add or remove messages from a queue or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/#pID0E01HG0HA). +On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add or remove messages from a queue or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, see [DBMS_AQ](/epas/latest/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/). On the client side, the application uses the EDB.NET driver to enqueue and dequeue messages. ## Enqueueing or dequeueing a message -For more information about using EDB Postgres Advanced Server's advanced queueing functionality, see the [Database Compatibility for Oracle Developers Built-in Package Guide](/epas/latest/epas_compat_bip_guide/). +For more information about using EDB Postgres Advanced Server's advanced queueing functionality, see the [Database Compatibility for Oracle Developers Built-in Package Guide](/epas/latest/reference/oracle_compatibility_reference/epas_compat_bip_guide/). ### Server-side setup @@ -486,5 +486,5 @@ The `EDBAQVisibility` class represents the visibility options available. | On_Commit | The enqueue/dequeue is part of the current transaction. | !!! Note -- To review the default options for these parameters, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/#pID0E01HG0HA/). +- To review the default options for these parameters, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/). - EDB advanced queueing functionality uses user-defined types for calling enqueue/dequeue operations. `Server Compatibility Mode=NoTypeLoading` can't be used with advanced queueing because `NoTypeLoading` doesn't load any user-defined types. diff --git a/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx b/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx index 80029584880..1a926587a89 100644 --- a/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx +++ b/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx @@ -13,7 +13,7 @@ On the client side, the application uses the EDB.NET driver to enqueue and deque ## Enqueueing or dequeueing a message -For more information about using EDB Postgres Advanced Server's advanced queueing functionality, see [Built-in packages](/epas/latest/epas_compat_bip_guide/). +For more information about using EDB Postgres Advanced Server's advanced queueing functionality, see [Built-in packages](/epas/latest/reference/oracle_compatibility_reference/epas_compat_bip_guide/). ### Server-side setup @@ -488,5 +488,5 @@ The `EDBAQVisibility` class represents the visibility options available. | On_Commit | The enqueue/dequeue is part of the current transaction. | !!! Note -- To review the default options for these parameters, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/#pID0E01HG0HA/). +- To review the default options for these parameters, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/). - EDB advanced queueing functionality uses user-defined types for calling enqueue/dequeue operations. `Server Compatibility Mode=NoTypeLoading` can't be used with advanced queueing because `NoTypeLoading` doesn't load any user-defined types. diff --git a/product_docs/docs/net_connector/7.0.6.1/12_using_advanced_queueing.mdx b/product_docs/docs/net_connector/7.0.6.1/12_using_advanced_queueing.mdx index 80029584880..1a926587a89 100644 --- a/product_docs/docs/net_connector/7.0.6.1/12_using_advanced_queueing.mdx +++ b/product_docs/docs/net_connector/7.0.6.1/12_using_advanced_queueing.mdx @@ -13,7 +13,7 @@ On the client side, the application uses the EDB.NET driver to enqueue and deque ## Enqueueing or dequeueing a message -For more information about using EDB Postgres Advanced Server's advanced queueing functionality, see [Built-in packages](/epas/latest/epas_compat_bip_guide/). +For more information about using EDB Postgres Advanced Server's advanced queueing functionality, see [Built-in packages](/epas/latest/reference/oracle_compatibility_reference/epas_compat_bip_guide/). ### Server-side setup @@ -488,5 +488,5 @@ The `EDBAQVisibility` class represents the visibility options available. | On_Commit | The enqueue/dequeue is part of the current transaction. | !!! Note -- To review the default options for these parameters, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/#pID0E01HG0HA/). +- To review the default options for these parameters, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/). - EDB advanced queueing functionality uses user-defined types for calling enqueue/dequeue operations. `Server Compatibility Mode=NoTypeLoading` can't be used with advanced queueing because `NoTypeLoading` doesn't load any user-defined types. diff --git a/product_docs/docs/ocl_connector/15/04_open_client_library/index.mdx b/product_docs/docs/ocl_connector/15/04_open_client_library/index.mdx index d32c9026ac4..abbf377bc34 100644 --- a/product_docs/docs/ocl_connector/15/04_open_client_library/index.mdx +++ b/product_docs/docs/ocl_connector/15/04_open_client_library/index.mdx @@ -9,7 +9,7 @@ The Open Client Library provides application interoperability with the Oracle Ca The following diagram compares the Open Client Library and Oracle Call Interface application stacks. -![Comparison with Oracle Call Interface](images/oracle_call_interface.png) +![Comparison with Oracle Call Interface](../images/oracle_call_interface.png) The EDB implementation of the Open Client Library is written in C. diff --git a/product_docs/docs/ocl_connector/15/installing/windows.mdx b/product_docs/docs/ocl_connector/15/installing/windows.mdx index 0dfc9bb3234..3492cb8a10a 100644 --- a/product_docs/docs/ocl_connector/15/installing/windows.mdx +++ b/product_docs/docs/ocl_connector/15/installing/windows.mdx @@ -23,7 +23,7 @@ Proceed to [Using the graphical installer](#using-the-graphical-installer). ## Using StackBuilder Plus -If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). +If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/installing/windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). 1. In StackBuilder Plus, follow the prompts until you get to the module selection page. diff --git a/product_docs/docs/ocl_connector/16/installing/index.mdx b/product_docs/docs/ocl_connector/16/installing/index.mdx index f42dd76e1fc..91500ee7fd4 100644 --- a/product_docs/docs/ocl_connector/16/installing/index.mdx +++ b/product_docs/docs/ocl_connector/16/installing/index.mdx @@ -7,11 +7,11 @@ title: Installing EDB OCL Connector # Leaf template: products/edb-ocl-connector/index.njk redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/ - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/11_updating_rpm_install/ - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/07_ocl_connector14_rhel8_ppcle/ - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/06_ocl_connector14_ubuntu18_deb9_x86/ + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/ + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/11_updating_rpm_install/ + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/07_ocl_connector14_rhel8_ppcle/ + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/06_ocl_connector14_ubuntu18_deb9_x86/ navigation: - linux_x86_64 diff --git a/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_rhel_8.mdx index e807b9a1b2a..2df40e9aeb9 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_rhel_8.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_rhel_8.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on RHEL 8 ppc64le # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_rhel8_ppcle + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_rhel8_ppcle --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_rhel_9.mdx index f062e997850..41999caf1d8 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_rhel_9.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_rhel_9.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on RHEL 9 ppc64le # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_rhel9_ppcle + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_rhel9_ppcle --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_sles_12.mdx index 41e5c0199d8..17fa4031e1c 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_sles_12.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_sles_12.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on SLES 12 ppc64le # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_sles12_ppcle + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_sles12_ppcle --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_sles_15.mdx index 922ba0b2c23..76b9571c467 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_sles_15.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_sles_15.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on SLES 15 ppc64le # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_sles15_ppcle + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_sles15_ppcle --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_centos_7.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_centos_7.mdx index f79c6dbaa82..864165b4141 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_centos_7.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_centos_7.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on CentOS 7 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_centos7_x86 + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_centos7_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_debian_10.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_debian_10.mdx index d19a2b41a28..c4caf1aa383 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_debian_10.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_debian_10.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on Debian 10 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb10_x86 + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb10_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_debian_11.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_debian_11.mdx index ae3cb3405ac..9f10d8a9bd0 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_debian_11.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_debian_11.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on Debian 11 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb11_x86 + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb11_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_other_linux_8.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_other_linux_8.mdx index 7e4f344c2cb..ecc4a960858 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_other_linux_8.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_other_linux_8.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on AlmaLinux 8 or Rocky Linux 8 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_other_linux8_x86 + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_other_linux8_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_other_linux_9.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_other_linux_9.mdx index 1df2cd2c0fd..17b7ce99e6e 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_other_linux_9.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_other_linux_9.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on AlmaLinux 9 or Rocky Linux 9 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_other_linux9_x86 + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_other_linux9_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_7.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_7.mdx index 19070b5ce72..f35857f4c88 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_7.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_7.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on RHEL 7 or OL 7 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel7_x86 + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel7_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_8.mdx index 37b76de73f3..915c757fc3d 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_8.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_8.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on RHEL 8 or OL 8 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel8_x86 + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel8_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_9.mdx index cc84cedea39..35742e29644 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_9.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_9.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on RHEL 9 or OL 9 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel9_x86 + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel9_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_sles_12.mdx index 863f6bdb4cb..950ffce2e6b 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_sles_12.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_sles_12.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on SLES 12 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_sles12_x86 + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_sles12_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_sles_15.mdx index 54f2f854c18..640b0e57f22 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_sles_15.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_sles_15.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on SLES 15 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_sles15_x86 + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_sles15_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_ubuntu_18.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_ubuntu_18.mdx index f791fc3f257..f7918403d02 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_ubuntu_18.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_ubuntu_18.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on Ubuntu 18.04 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_ubuntu18_x86 + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_ubuntu18_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_ubuntu_20.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_ubuntu_20.mdx index e4c9c508378..a4df02a1a47 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_ubuntu_20.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_ubuntu_20.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on Ubuntu 20.04 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_ubuntu20_x86 + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_ubuntu20_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_ubuntu_22.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_ubuntu_22.mdx index 2cf14134c10..c1b4f4c0fc2 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_ubuntu_22.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_ubuntu_22.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on Ubuntu 22.04 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_ubuntu22_x86 + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_ubuntu22_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/16/installing/windows.mdx b/product_docs/docs/ocl_connector/16/installing/windows.mdx index 0dfc9bb3234..3492cb8a10a 100644 --- a/product_docs/docs/ocl_connector/16/installing/windows.mdx +++ b/product_docs/docs/ocl_connector/16/installing/windows.mdx @@ -23,7 +23,7 @@ Proceed to [Using the graphical installer](#using-the-graphical-installer). ## Using StackBuilder Plus -If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). +If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/installing/windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). 1. In StackBuilder Plus, follow the prompts until you get to the module selection page. diff --git a/product_docs/docs/odbc_connector/13/installing/windows.mdx b/product_docs/docs/odbc_connector/13/installing/windows.mdx index e9a009cd95c..9721c0d8498 100644 --- a/product_docs/docs/odbc_connector/13/installing/windows.mdx +++ b/product_docs/docs/odbc_connector/13/installing/windows.mdx @@ -24,9 +24,9 @@ Proceed to [Using the graphical installer](#using-the-graphical-installer). ## Using Stack Builder or StackBuilder Plus -If you're using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installer/03_using_stackbuilder/). +If you're using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installing/03_using_stackbuilder/). -If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). +If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/installing/windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). 1. In Stack Builder or StackBuilder Plus, follow the prompts until you get to the module selection page. diff --git a/product_docs/docs/odbc_connector/16/02_requirements_overview.mdx b/product_docs/docs/odbc_connector/16/02_requirements_overview.mdx index 8b5747f586e..06a2bccbe1f 100644 --- a/product_docs/docs/odbc_connector/16/02_requirements_overview.mdx +++ b/product_docs/docs/odbc_connector/16/02_requirements_overview.mdx @@ -11,7 +11,7 @@ This table lists the latest ODBC Connector versions and their supported correspo | ODBC Connector | EPAS 16 | EPAS 15 | EPAS 14 | EPAS 13 | EPAS 12 | EPAS 11 | | ------------------------------------------------------------------------------ | ------- | ------- | ------- | ------- | ------- | ------- | -| [16.00.0000.01](01_odbc_rel_notes/odbc_16.00.00000.01_rel_notes) | Y | Y | Y | Y | Y | Y | +| [16.00.0000.01](01_odbc_rel_notes/odbc_16.00.0000.01_rel_notes/) | Y | Y | Y | Y | Y | Y | | [13.02.0.02](/odbc_connector/13/01_odbc_rel_notes/odbc_13.2.0.02_rel_notes) | N | Y | Y | Y | Y | Y | | [13.02.0.01](/odbc_connector/13/01_odbc_rel_notes/02_odbc_13.2.0.01_rel_notes) | N | N | Y | Y | Y | Y | | [13.01.0.02](/odbc_connector/13/01_odbc_rel_notes/03_odbc_13.1.0.02_rel_notes) | N | N | Y | Y | Y | Y | diff --git a/product_docs/docs/odbc_connector/16/installing/windows.mdx b/product_docs/docs/odbc_connector/16/installing/windows.mdx index e9a009cd95c..9721c0d8498 100644 --- a/product_docs/docs/odbc_connector/16/installing/windows.mdx +++ b/product_docs/docs/odbc_connector/16/installing/windows.mdx @@ -24,9 +24,9 @@ Proceed to [Using the graphical installer](#using-the-graphical-installer). ## Using Stack Builder or StackBuilder Plus -If you're using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installer/03_using_stackbuilder/). +If you're using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installing/03_using_stackbuilder/). -If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). +If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/installing/windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). 1. In Stack Builder or StackBuilder Plus, follow the prompts until you get to the module selection page. 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 baf63d9ce0f..7b5760a00b7 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 9ff8005f7e0..119c4512b15 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 d7c0f2a107a..bd27908a4e3 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 @@ -42,7 +42,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 ff9f9c51e17..2e9bfdeb147 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 @@ -42,7 +42,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 05ef5b0a7ff..690a3ac19f6 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 79ba1612af3..4c0696ad053 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 4f2577265b7..264e0e3d051 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 ab35eaf12a9..6f369de808f 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 @@ -39,7 +39,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 0168048ba24..9abd84e5dbe 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 @@ -39,7 +39,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 2c553141972..3ec36ed156d 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 6a97d006fdf..2c33f9ff1c0 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 166a865dea5..eb56bc73d79 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 dc0730e8ca7..939325a44d9 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 @@ -42,7 +42,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 84b683ec804..3b02b4784fb 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 @@ -42,7 +42,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 b54bcaba898..81ce9bfee01 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 8a8bdb2bd65..211f8aa85c7 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 78b6c571be3..63ff7f20118 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. diff --git a/product_docs/docs/pem/8/installing/prerequisites.mdx b/product_docs/docs/pem/8/installing/prerequisites.mdx index a8121148640..78c2d9edbf7 100644 --- a/product_docs/docs/pem/8/installing/prerequisites.mdx +++ b/product_docs/docs/pem/8/installing/prerequisites.mdx @@ -88,7 +88,7 @@ To install a Postgres Enterprise Manager server on Linux, you may need to perfor Where `` is the Postgres server version. !!! Note For Debian and Ubuntu users - The postgres community repository for apt (used by Debian and Ubuntu) does not include `sslutils` and therefore this must be installed from the EDB repository along with [PEM](/installing_pem_server_using_edb_repository/index.mdx). + The postgres community repository for apt (used by Debian and Ubuntu) does not include `sslutils` and therefore this must be installed from the EDB repository along with PEM. Debian 10 and Ubuntu 20 changed the requirements for accepting certificates. diff --git a/product_docs/docs/pem/8/pem_online_help/01_toc_pem_getting_started/07_pem_define_connection.mdx b/product_docs/docs/pem/8/pem_online_help/01_toc_pem_getting_started/07_pem_define_connection.mdx index 9c0f9939bd4..39f8f8651e3 100644 --- a/product_docs/docs/pem/8/pem_online_help/01_toc_pem_getting_started/07_pem_define_connection.mdx +++ b/product_docs/docs/pem/8/pem_online_help/01_toc_pem_getting_started/07_pem_define_connection.mdx @@ -25,7 +25,7 @@ Use fields on the `Connection` tab to specify connection details for the server: - Specify the IP address of the server host, or the fully qualified domain name in the `Host name/address` field. On Unix based systems, the address field may be left blank to use the default PostgreSQL Unix Domain Socket on the local machine, or may be set to an alternate path containing a PostgreSQL socket. If you enter a path, the path must begin with a "/". - Specify the port number of the host in the `Port` field. -- Use the `Maintenance database` field to specify the name of the initial database that PEM will connect to, and that will contain the [pgAgent](../10_pgagent/#pgagent) schema and admin pack objects if installed (both are optional). If you are planning to monitor PGD via PEM, then specify the PGD-enabled database name in this field. On an Advanced Server database, the maintenance database is named 'edb'. PostgreSQL 8.1 and above, the maintenance DB for PostgreSQL is named 'postgres'; on earlier versions, `template1` is often used, though it is preferable to create a `postgres` database for this purpose to avoid cluttering the template database. +- Use the `Maintenance database` field to specify the name of the initial database that PEM will connect to, and that will contain the [pgAgent](https://www.pgadmin.org/download/) schema and admin pack objects if installed (both are optional). If you are planning to monitor PGD via PEM, then specify the PGD-enabled database name in this field. On an Advanced Server database, the maintenance database is named 'edb'. PostgreSQL 8.1 and above, the maintenance DB for PostgreSQL is named 'postgres'; on earlier versions, `template1` is often used, though it is preferable to create a `postgres` database for this purpose to avoid cluttering the template database. - Set the `Kerberos Authentication` to `Yes` to use the Kerberos Authentication for a monitored server. By default, the monitored server uses the same authentication method as the PEM Server. If the monitored server does not want to use Kerberos Authentication then `ALLOW_DATABASE_CONNECTION_WITHOUT_KERBEROS` must be set to `TRUE` in `config_local.py` file. - Specify the name that will be used when authenticating with the server in the `Username` field. If the `Kerberos Authentication` method is used then the username field will be populated automatically and will be disabled. - Provide the password associated with the specified user in the `Password` field. If the `Kerberos Authentication` method is used then this field is disabled. diff --git a/product_docs/docs/pem/9/considerations/setup_ha_using_efm.mdx b/product_docs/docs/pem/9/considerations/setup_ha_using_efm.mdx index 4a39ea076a0..dd306a05d46 100644 --- a/product_docs/docs/pem/9/considerations/setup_ha_using_efm.mdx +++ b/product_docs/docs/pem/9/considerations/setup_ha_using_efm.mdx @@ -31,9 +31,9 @@ The following must use the VIP address: 1. Install the following on the primary and one or more standbys: - - [EDB Postgres Advanced Server](/epas/latest/epas_inst_linux/) (backend database for PEM Server) + - [EDB Postgres Advanced Server](/epas/latest/installing/) (backend database for PEM Server) - [PEM server](/pem/latest/installing/) - - [EDB Failover Manager 4.1](/efm/latest/efm_user/03_installing_efm/) + - [EDB Failover Manager 4.1](/efm/latest/installing/) Refer to the installation instructions in the product documentation using these links or see the instructions on the [EDB repos website](https://repos.enterprisedb.com). Replace `USERNAME:PASSWORD` with your username and password in the instructions to access the EDB repositories. 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 b4085dddb46..350a950fbee 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 9f804f241f1..fd7290b0810 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 a3c750413d7..65c0d5592f7 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 @@ -42,7 +42,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 bdc2ae521ed..340511fe68e 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 @@ -42,7 +42,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 e5adf907b55..65710bca03f 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 d9fb512340c..7494eac3612 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 cb8034c98d4..7f9c937608a 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 d0d1d27da0f..0748849744b 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 @@ -39,7 +39,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 7bf9b704295..5afc96433cf 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 @@ -39,7 +39,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 d667314d9ff..e0d0e61ff61 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 9bc79f25be6..e3e78b3a7f3 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 34c4442af4c..cafb3c3cb60 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 fd002ff92f5..8ab890fcf64 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 @@ -42,7 +42,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 0d19fd43e3a..d128d55c673 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 @@ -42,7 +42,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 d22bcc5136c..242609095f4 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 89a6e7c6c69..11a2cd7c1b8 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. 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 46ae2a6a3e8..58ca41c8382 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 @@ -38,7 +38,7 @@ Before you begin the installation process: The PostgreSQL community repository is required only if you are using PostgreSQL as the backend database for PEM server. -- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). +- Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/installing/) or [Installing PostgreSQL](/supported-open-source/postgresql/installing/). - Review [configuration and authentication requirements](../prerequisites/) for PEM. diff --git a/product_docs/docs/pem/9/installing/prerequisites.mdx b/product_docs/docs/pem/9/installing/prerequisites.mdx index b27ac53b8da..513ca0934f1 100644 --- a/product_docs/docs/pem/9/installing/prerequisites.mdx +++ b/product_docs/docs/pem/9/installing/prerequisites.mdx @@ -88,7 +88,7 @@ To install a Postgres Enterprise Manager server on Linux, you may need to perfor Where `` is the Postgres server version. !!! Note For Debian and Ubuntu users - The postgres community repository for apt (used by Debian and Ubuntu) does not include `sslutils` and therefore this must be installed from the EDB repository along with [PEM](/installing_pem_server_using_edb_repository/index.mdx). + The postgres community repository for apt (used by Debian and Ubuntu) does not include `sslutils` and therefore this must be installed from the EDB repository along with PEM. Debian 10 and Ubuntu 20 changed the requirements for accepting certificates. diff --git a/product_docs/docs/pem/9/installing/windows/index.mdx b/product_docs/docs/pem/9/installing/windows/index.mdx index 3bac0a96fbb..b0c42ebe947 100644 --- a/product_docs/docs/pem/9/installing/windows/index.mdx +++ b/product_docs/docs/pem/9/installing/windows/index.mdx @@ -37,7 +37,7 @@ The PEM server backend database can be an EDB distribution of the PostgreSQL or - For detailed information about installing and configuring a standalone PEM agent, see [Installing the PEM agent on Windows](../../installing_pem_agent/windows_agent). -- Language pack installers contain supported languages that you can use with EDB Postgres Advanced Server and EDB PostgreSQL database installers. The language pack installer allows you to install Perl, TCL/TK, and Python without installing supporting software from third-party vendors. For more information about installing and using the language pack, see [EDB Postgres language pack](/epas/latest/language_pack/). +- Language pack installers contain supported languages that you can use with EDB Postgres Advanced Server and EDB PostgreSQL database installers. The language pack installer allows you to install Perl, TCL/TK, and Python without installing supporting software from third-party vendors. For more information about installing and using the language pack, see [EDB Postgres language pack](/language_pack/latest/). - For troubleshooting the installation or configuration of the PEM agent, see [Troubleshooting PEM agent](../../troubleshooting_agent/). diff --git a/product_docs/docs/pem/9/profiling_workloads/index_advisor.mdx b/product_docs/docs/pem/9/profiling_workloads/index_advisor.mdx index 5fa1ed75e6b..5008195bccd 100644 --- a/product_docs/docs/pem/9/profiling_workloads/index_advisor.mdx +++ b/product_docs/docs/pem/9/profiling_workloads/index_advisor.mdx @@ -19,7 +19,7 @@ Diagnostic output from the Index Advisor includes: - DDL statements you can use to create the recommended indexes -Index Advisor can make indexing recommendations based on trace data captured by SQL Profiler. To open Index Advisor, select one or more queries in the SQL Profiler Trace Data pane and select **Index Advisor** from the toolbar. For more information about configuring and using Index Advisor, see [EDB Postgres Advanced Server](/epas/latest/managing_performance/02_index_advisor/). +Index Advisor can make indexing recommendations based on trace data captured by SQL Profiler. To open Index Advisor, select one or more queries in the SQL Profiler Trace Data pane and select **Index Advisor** from the toolbar. For more information about configuring and using Index Advisor, see [EDB Postgres Advanced Server](/epas/15/managing_performance/02_index_advisor/). !!! Note Index Advisor can't analyze statements invoked by a non-superuser. If you attempt to analyze statements invoked by a non-superuser, the server log includes the following error: diff --git a/product_docs/docs/pgbouncer/1/installing/windows.mdx b/product_docs/docs/pgbouncer/1/installing/windows.mdx index c58b315ff7d..be878ab0f76 100644 --- a/product_docs/docs/pgbouncer/1/installing/windows.mdx +++ b/product_docs/docs/pgbouncer/1/installing/windows.mdx @@ -27,9 +27,9 @@ Proceed to [Using the graphical installer](#using-the-graphical-installer). ## Using Stack Builder or StackBuilder Plus -If you're using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installer/03_using_stackbuilder/). +If you're using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installing/03_using_stackbuilder/). -If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). +If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/installing/windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). 1. In Stack Builder or StackBuilder Plus, follow the prompts until you get to the module selection page. diff --git a/product_docs/docs/pgd/3.7/bdr/index.mdx b/product_docs/docs/pgd/3.7/bdr/index.mdx index 53bd5ab5cb6..6cfd6fe3faf 100644 --- a/product_docs/docs/pgd/3.7/bdr/index.mdx +++ b/product_docs/docs/pgd/3.7/bdr/index.mdx @@ -44,7 +44,7 @@ provides a solution for building multi-master clusters with mesh topology. This means that you can write to any server and the changes will be sent row-by-row to all the other servers that are part of the same BDR group. -BDR 3 ("BDR3") is built on the [pglogical 3.7](https://www.enterprisedb.com/docs/pglogical/latest/) +BDR 3 ("BDR3") is built on the [pglogical 3.7](../pglogical/) extension. However, everything you need to know about BDR3 is included here and it is unnecessary, as well as potentially confusing, to refer to pglogical 3.7 docs. diff --git a/product_docs/docs/pgd/3.7/bdr/overview.mdx b/product_docs/docs/pgd/3.7/bdr/overview.mdx index 3f38c70c0c1..585befc9e5a 100644 --- a/product_docs/docs/pgd/3.7/bdr/overview.mdx +++ b/product_docs/docs/pgd/3.7/bdr/overview.mdx @@ -37,7 +37,7 @@ replicate either from the master or from another standby. You don't have to write to all the masters, all of the time; it's a frequent configuration to direct writes mostly to just one master. However, if you just want one-way replication, the use of -[pglogical](https://www.enterprisedb.com/docs/pglogical/latest/) may be more appropriate. +[pglogical](../pglogical/) may be more appropriate. ### Asynchronous, by default diff --git a/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx b/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx index e422c0e9bc3..a0355088c93 100644 --- a/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx +++ b/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx @@ -17,7 +17,7 @@ navigation: --- High Availability Routing for Postgres (HARP) is a cluster-management tool for -[Bi-directional Replication (BDR)](/bdr/latest) clusters. The core design of +[Bi-directional Replication (BDR)](../../bdr/) clusters. The core design of the tool is to route all application traffic in a single data center or region to only one node at a time. This node, designated the lead master, acts as the principle write target to reduce the potential for data conflicts. diff --git a/product_docs/docs/pgd/3.7/harp/09_consensus-layer.mdx b/product_docs/docs/pgd/3.7/harp/09_consensus-layer.mdx index 81f852cad74..0343e31b2fe 100644 --- a/product_docs/docs/pgd/3.7/harp/09_consensus-layer.mdx +++ b/product_docs/docs/pgd/3.7/harp/09_consensus-layer.mdx @@ -17,8 +17,8 @@ supported DCS implementations. ## BDR driver compatibility The `bdr` native consensus layer is available from BDR versions -[3.6.21](/bdr/3.7/release-notes/#bdr-362) -and [3.7.3](/bdr/3.7/release-notes/#bdr-373). +[3.6.21](/pgd/3.6/release-notes/#bdr-3621-2020-aug-14) +and [3.7.3](/pgd/3.7/bdr/release-notes/#bdr-373-2020-aug-06). For the purpose of maintaining a voting quorum, BDR Logical Standby nodes don't participate in consensus communications in a EDB Postgres Distributed cluster. Don't count these in the total node list to fulfill DCS quorum requirements. diff --git a/product_docs/docs/pgd/3.7/harp/index.mdx b/product_docs/docs/pgd/3.7/harp/index.mdx index 7ddbea33d25..acfd2e51864 100644 --- a/product_docs/docs/pgd/3.7/harp/index.mdx +++ b/product_docs/docs/pgd/3.7/harp/index.mdx @@ -6,7 +6,7 @@ directoryDefaults: --- High Availability Routing for Postgres (HARP) is a cluster-management tool for -[Bi-directional Replication (BDR)](/bdr/latest) clusters. The core design of +[Bi-directional Replication (BDR)](../bdr/) clusters. The core design of the tool is to route all application traffic in a single data center or region to only one node at a time. This node, designated the lead master, acts as the principle write target to reduce the potential for data conflicts. diff --git a/product_docs/docs/pgd/4/deployments/index.mdx b/product_docs/docs/pgd/4/deployments/index.mdx index 839597db544..8a5c9f0110e 100644 --- a/product_docs/docs/pgd/4/deployments/index.mdx +++ b/product_docs/docs/pgd/4/deployments/index.mdx @@ -8,7 +8,7 @@ You can deploy and install EDB Postgres Distributed products using the following - TPAexec is an orchestration tool that uses Ansible to build Postgres clusters as specified by TPA (Trusted Postgres Architecture), a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations are as applicable to quick testbed setups as to production environments. -- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility, running in your cloud account and operated by the Postgres experts. BigAnimal makes it easy to set up, manage, and scale your databases. The addition of extreme high availability support through EDB Postres Distributed allows single-region Always On Gold clusters: two BDR groups in different availability zones in a single cloud region, with a witness node in a third availability zone. See the [Extreme high availability](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-beta) topic in the [BigAnimal documentation](/biganimal/latest) for more information. +- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility, running in your cloud account and operated by the Postgres experts. BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high availability support through EDB Postres Distributed allows single-region or multi-region clusters with one or two data groups. See the [Distributed high availability](/biganimal/latest/overview/02_high_availability/distributed_highavailability/) topic in the [BigAnimal documentation](/biganimal/latest) for more information. Coming soon: diff --git a/product_docs/docs/pgd/4/harp/09_consensus-layer.mdx b/product_docs/docs/pgd/4/harp/09_consensus-layer.mdx index bba250427cd..891cb88bab6 100644 --- a/product_docs/docs/pgd/4/harp/09_consensus-layer.mdx +++ b/product_docs/docs/pgd/4/harp/09_consensus-layer.mdx @@ -19,8 +19,8 @@ supported DCS implementations. ## BDR driver compatibility The `bdr` native consensus layer is available from BDR versions -[3.6.21](/bdr/3.7/release-notes/#bdr-362) -and [3.7.3](/bdr/3.7/release-notes/#bdr-373). +[3.6.21](/pgd/3.6/release-notes/#bdr-3621-2020-aug-14) +and [3.7.3](/pgd/3.7/bdr/release-notes/#bdr-373-2020-aug-06). For the purpose of maintaining a voting quorum, BDR Logical Standby nodes and BDR Subscriber-Only nodes don't participate in consensus communications in a EDB Postgres Distributed cluster. Don't count these in the total node list to fulfill DCS quorum requirements. diff --git a/product_docs/docs/pgd/4/rel_notes/pgd_4.0.0_rel_notes.mdx b/product_docs/docs/pgd/4/rel_notes/pgd_4.0.0_rel_notes.mdx index 9d54a21fe71..4b6bcd7c651 100644 --- a/product_docs/docs/pgd/4/rel_notes/pgd_4.0.0_rel_notes.mdx +++ b/product_docs/docs/pgd/4/rel_notes/pgd_4.0.0_rel_notes.mdx @@ -21,7 +21,7 @@ versions are 3.7 and 3.6. | BDR | 4.0.0 | Feature | There is no pglogical 4.0 extension that corresponds to the BDR 4.0 extension. BDR no longer has a requirement for pglogical.

This means also that only BDR extension and schema exist and any configuration parameters were renamed from `pglogical.` to `bdr.`.

| | BDR | 4.0.0 | Feature | Some configuration options have change defaults for better post-install experience:
- Parallel apply is now enabled by default (with 2 writers). Allows for better performance, especially with streaming enabled.
- `COPY` and `CREATE INDEX CONCURRENTLY` are now streamed directly to writer in parallel (on Postgres versions where streaming is supported) to all available nodes by default, eliminating or at least reducing replication lag spikes after these operations.
- The timeout for global locks have been increased to 10 minutes
- The `bdr.min_worker_backoff_delay` now defaults to 1s so that subscriptions retry connection only once per second on error | | BDR | 4.0.0 | Feature | Greatly reduced the chance of false positives in conflict detection during node join for table that use origin based conflict detection | -| BDR | 4.0.0 | Feature | Move configuration of CAMO pairs to SQL catalogs

To reduce chances of misconfiguration and make CAMO pairs within the BDR cluster known globally, move the CAMO configuration from the individual node's postgresql.conf to BDR system catalogs managed by Raft. This for example can prevent against inadvertently dropping a node that's still configured to be a CAMO partner for another active node.

Please see the [Upgrades chapter](/pgd/latest/upgrades/#upgrading-a-camo-enabled-cluster) for details on the upgrade process.

This deprecates GUCs `bdr.camo_partner_of` and `bdr.camo_origin_for` and replaces the functions `bdr.get_configured_camo_origin_for()` and `get_configured_camo_partner_of` with `bdr.get_configured_camo_partner`.

| +| BDR | 4.0.0 | Feature | Move configuration of CAMO pairs to SQL catalogs

To reduce chances of misconfiguration and make CAMO pairs within the BDR cluster known globally, move the CAMO configuration from the individual node's postgresql.conf to BDR system catalogs managed by Raft. This for example can prevent against inadvertently dropping a node that's still configured to be a CAMO partner for another active node.

Please see the [Upgrades chapter](/pgd/latest/upgrades/manual_overview/#upgrading-a-camo-enabled-cluster) for details on the upgrade process.

This deprecates GUCs `bdr.camo_partner_of` and `bdr.camo_origin_for` and replaces the functions `bdr.get_configured_camo_origin_for()` and `get_configured_camo_partner_of` with `bdr.get_configured_camo_partner`.

| | HARP | 2.0.0 | Change | Complete rewrite of system in golang to optimize all operations | | HARP | 2.0.0 | Change | Cluster state can now be bootstrapped or revised via YAML | | HARP | 2.0.0 | Feature | Configuration now in YAML, configuration file changed from `harp.ini` to `config.yml` | diff --git a/product_docs/docs/pgd/4/rel_notes/pgd_4.1.0_rel_notes.mdx b/product_docs/docs/pgd/4/rel_notes/pgd_4.1.0_rel_notes.mdx index 6e348d3ada0..bbf7aefa5ba 100644 --- a/product_docs/docs/pgd/4/rel_notes/pgd_4.1.0_rel_notes.mdx +++ b/product_docs/docs/pgd/4/rel_notes/pgd_4.1.0_rel_notes.mdx @@ -13,10 +13,10 @@ EDB Postgres Distributed version 4.1.0 includes the following: | ------------------------ | ------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | CLI | 1.0.0 | Feature | Ability to gather information such as the current state of replication, consensus, and nodes for an EDB Postgres Distributed cluster using new [command-line interface (CLI)](/pgd/latest/cli). | | BDR | 4.1.0 | Feature | Support [in-place major upgrades](/pgd/latest/upgrades/bdr_pg_upgrade/) of Postgres on a data node with a new command-line utility, bdr_pg_upgrade. This utility uses the standard pg_upgrade command, and reduces the time and network bandwidth needed to do major version upgrades of a EDB Postgres Distributed cluster. | -| BDR | 4.1.0 | Feature | Enable the ability to configure a [replication lag threshold](/pgd/latest/bdr/lag-control/). After the threshold is met, the transaction commits get throttled. This threshold allows limiting RPO without incurring the latency impact on every transaction that comes with synchronous replication. | -| BDR | 4.1.0 | Feature | [Global sequences](/pgd/latest/bdr/sequences/#bdr-global-sequences) are automatically configured based on data type replacing the need to set up custom sequence handling configuration on every node. The new SnowflakeID algorithm replaces Timeshard, which had limitations. | +| BDR | 4.1.0 | Feature | Enable the ability to configure a [replication lag threshold](/pgd/latest/durability/lag-control/). After the threshold is met, the transaction commits get throttled. This threshold allows limiting RPO without incurring the latency impact on every transaction that comes with synchronous replication. | +| BDR | 4.1.0 | Feature | [Global sequences](/pgd/latest/sequences/#pgd-global-sequences) are automatically configured based on data type replacing the need to set up custom sequence handling configuration on every node. The new SnowflakeID algorithm replaces Timeshard, which had limitations. | | BDR | 4.1.0 | Feature | Add a new SQL-level interface for configuring synchronous replication durability and visibility options by group rather than by node. This approach allows you to configure all nodes consistently from a single place instead of using config files. | -| BDR | 4.1.0 | Feature | Add a new synchronous replication option, [Group Commit](/pgd/latest/bdr/group-commit/), which allows a quorum to be required before committing a transaction in a EDB Postgres Distributed group. | +| BDR | 4.1.0 | Feature | Add a new synchronous replication option, [Group Commit](/pgd/latest/durability/group-commit/), which allows a quorum to be required before committing a transaction in a EDB Postgres Distributed group. | | BDR | 4.1.0 | Feature | Allow a Raft request to be required for CAMO switching to Local Mode. Add a `require_raft` flag to the CAMO pairing configuration which controls the behavior of switching from CAMO protected to Local Mode, introducing the option to require a majority of nodes to be connected to allow to switch to Local Mode. (RT78928) | | BDR | 4.1.0 | Feature | Allow replication to continue on `ALTER TABLE ... DETACH PARTITION CONCURRENTLY` of already detached partition. Similarly to how BDR 4 handles `CREATE INDEX CONCURRENTLY` when same index already exists, we now allow replication to continue when `ALTER TABLE ... DETACH PARTITION CONCURRENTLY` is receiver for partition that has been already detached. (RT78362) | | BDR | 4.1.0 | Feature | Add additional filtering options to DDL filters. DDL filters allow for replication of different DDL statements to different replication sets. Similar to how table membership in replication set allows DML on different tables to be replicated via different replication sets. This release adds new controls that make it easier to use the DDL filters:
- query_match - if defined query must match this regex
- exclusive - if true, other matched filters are not taken into consideration (i.e. only the exclusive filter is applied), when multiple exclusive filters match, we throw error | diff --git a/product_docs/docs/pgd/4/rel_notes/pgd_4.1.1_rel_notes.mdx b/product_docs/docs/pgd/4/rel_notes/pgd_4.1.1_rel_notes.mdx index 6dc899f0061..ed6829c1e89 100644 --- a/product_docs/docs/pgd/4/rel_notes/pgd_4.1.1_rel_notes.mdx +++ b/product_docs/docs/pgd/4/rel_notes/pgd_4.1.1_rel_notes.mdx @@ -18,7 +18,7 @@ EDB Postgres Distributed version 4.1.1 includes bug fixes for BDR 4.1.1 and HARP | BDR | 4.1.1 | Bug fix | Prevent removing a `bdr.remove_commit_scope` if still referenced by any `bdr.node_group` as the default commit scope. | | BDR | 4.1.1 | Bug fix | Correct Raft based switching to Local Mode for CAMO pairs of nodes (RT78928) | | BDR | 4.1.1 | Bug fix | Prevent a potential segfault in bdr.drop_node for corner cases (RT81900) | -| BDR | 4.1.1 | Bug fix | Prevent use of CAMO or Eager All Node transactions in combination with transaction streaming. Transaction streaming turned out to be problematic in combination with CAMO and Eager All Node transactions. Until this is resolved, BDR now prevents its combined use. This may require CAMO deployments to adjust their configuration to disable transaction streaming, see [Transaction Streaming Configuration](/pgd/latest/bdr/transaction-streaming/#configuration). | +| BDR | 4.1.1 | Bug fix | Prevent use of CAMO or Eager All Node transactions in combination with transaction streaming. Transaction streaming turned out to be problematic in combination with CAMO and Eager All Node transactions. Until this is resolved, BDR now prevents its combined use. This may require CAMO deployments to adjust their configuration to disable transaction streaming, see [Transaction Streaming Configuration](/pgd/4/bdr/transaction-streaming/#configuration). | | HARP | 2.1.1 | Enhancement | Log a warning on loss of DCS connection | | HARP | 2.1.1 | Enhancement | Log a warning when metadata refresh is taking too long - usually due to high latency network | | HARP | 2.1.1 | Bug fix | Restart harp_proxy.service on a failure | diff --git a/product_docs/docs/pgd/4/upgrades/upgrade_paths.mdx b/product_docs/docs/pgd/4/upgrades/upgrade_paths.mdx index 7c450258570..4cdd374dc2e 100644 --- a/product_docs/docs/pgd/4/upgrades/upgrade_paths.mdx +++ b/product_docs/docs/pgd/4/upgrades/upgrade_paths.mdx @@ -28,5 +28,5 @@ following upgrade paths are possible. ## 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. +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-to-version-37) in the 3.7 documentation for more information. diff --git a/product_docs/docs/pgd/5/appusage/table-access-methods.mdx b/product_docs/docs/pgd/5/appusage/table-access-methods.mdx index d7139b06879..68c88f9269c 100644 --- a/product_docs/docs/pgd/5/appusage/table-access-methods.mdx +++ b/product_docs/docs/pgd/5/appusage/table-access-methods.mdx @@ -22,4 +22,4 @@ data TAM, on each node: 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;`. These commands replicate to all the PGD nodes. For more information on these table access -methods, see [`CREATE TABLE`](/epas/latest/epas_compat_sql/36_create_table/). +methods, see [`CREATE TABLE`](/epas/latest/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table/). diff --git a/product_docs/docs/pgd/5/consistency/conflicts.mdx b/product_docs/docs/pgd/5/consistency/conflicts.mdx index 36eb100deba..79994e3b50b 100644 --- a/product_docs/docs/pgd/5/consistency/conflicts.mdx +++ b/product_docs/docs/pgd/5/consistency/conflicts.mdx @@ -269,7 +269,7 @@ conflict. PGD could choose to make each `INSERT` into a check-for-recently deleted, as occurs with an `update_missing` conflict. However, the cost of doing this penalizes the majority of users, so at this time it instead logs `delete_missing`. -Future releases will automatically resolve `INSERT`/`DELETE` anomalies by way of rechecks using [LiveCompare](/latest/livecompare) when `delete_missing` conflicts occur. Applications can perform these manually by checking the `bdr.conflict_history_summary` view. +Future releases will automatically resolve `INSERT`/`DELETE` anomalies by way of rechecks using [LiveCompare](/livecompare/latest/) when `delete_missing` conflicts occur. Applications can perform these manually by checking the `bdr.conflict_history_summary` view. These conflicts can occur in two main problem use cases: diff --git a/product_docs/docs/pgd/5/deployments.mdx b/product_docs/docs/pgd/5/deployments.mdx index ca16d43536a..4437d7b20a2 100644 --- a/product_docs/docs/pgd/5/deployments.mdx +++ b/product_docs/docs/pgd/5/deployments.mdx @@ -8,7 +8,7 @@ You can deploy and install EDB Postgres Distributed products using the following - [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. TPA's flexibility allows deployments to virtual machines, AWS cloud instances or Linux host hardware. See [Deploying with TPA](tpa) for more information. -- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability support powered by EDB Postgres Distributed (PGD) enables single- and and multi-region Always On Gold clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) in the [BigAnimal documentation](/biganimal/latest) for more information. +- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability support powered by EDB Postgres Distributed (PGD) enables single- and and multi-region Always On Gold clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/distributed_highavailability/) in the [BigAnimal documentation](/biganimal/latest) for more information. - EDB Postgres Distributed for Kubernetes is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift. This offering is currently in preview. diff --git a/product_docs/docs/pgd/5/limitations.mdx b/product_docs/docs/pgd/5/limitations.mdx index 2c16b979914..08d283b6032 100644 --- a/product_docs/docs/pgd/5/limitations.mdx +++ b/product_docs/docs/pgd/5/limitations.mdx @@ -103,7 +103,7 @@ node itself. - CAMO isn't currently compatible with transaction streaming. 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). +[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: - Nonconcurrent `CREATE INDEX` diff --git a/product_docs/docs/pgd/5/quickstart/index.mdx b/product_docs/docs/pgd/5/quickstart/index.mdx index a3a691b0075..88d3ddd05f1 100644 --- a/product_docs/docs/pgd/5/quickstart/index.mdx +++ b/product_docs/docs/pgd/5/quickstart/index.mdx @@ -20,7 +20,7 @@ navigation: EDB Postgres Distributed (PGD) is a multi-master replicating implementation of Postgres designed for high performance and availability. You can create database clusters made up of many bidirectionally synchronizing database nodes. The clusters can have a number of proxy servers that direct your query traffic to the most available nodes, adding further resilience to your cluster configuration. !!! Note Fully managed BigAnimal - If you prefer to have a fully managed EDB Postgres Distributed experience, PGD is now available as an option on BigAnimal, EDB's cloud platform for Postgres. Read more about [BigAnimal distributed high-availability clusters](/biganimal/latest/overview/02_high_availability/#distributed-high-availability). + If you prefer to have a fully managed EDB Postgres Distributed experience, PGD is now available as an option on BigAnimal, EDB's cloud platform for Postgres. Read more about [BigAnimal distributed high-availability clusters](/biganimal/latest/overview/02_high_availability/distributed_highavailability/). PGD is very configurable. To quickly evaluate and deploy PGD, use this quick start. It'll get you up and running with a fully configured PGD cluster using the same tools that you'll use to deploy to production. This quick start includes: diff --git a/product_docs/docs/pgd/5/reference/functions-internal.mdx b/product_docs/docs/pgd/5/reference/functions-internal.mdx index ce324c15b73..c0ade72d069 100644 --- a/product_docs/docs/pgd/5/reference/functions-internal.mdx +++ b/product_docs/docs/pgd/5/reference/functions-internal.mdx @@ -100,7 +100,7 @@ consensus mechanism is working. Internal implementation of sequence increments. Use this function instead of standard `nextval` in queries that -interact with [PGD global sequences](../../sequences/#pgd-global-sequences). +interact with [PGD global sequences](../sequences/#pgd-global-sequences). #### Notes diff --git a/product_docs/docs/pgd/5/reference/sequences.mdx b/product_docs/docs/pgd/5/reference/sequences.mdx index 2245c57a6cd..a0e12b71ecf 100644 --- a/product_docs/docs/pgd/5/reference/sequences.mdx +++ b/product_docs/docs/pgd/5/reference/sequences.mdx @@ -225,7 +225,7 @@ This function executes only on the local node. ## KSUUID v2 Functions -Functions for working with `KSUUID` v2 data, K-Sortable UUID data. See also [KSUUID in the sequences documentation](/sequences/#ksuuids). +Functions for working with `KSUUID` v2 data, K-Sortable UUID data. See also [KSUUID in the sequences documentation](../sequences/#ksuuids). ### `bdr.gen_ksuuid_v2` @@ -287,7 +287,7 @@ This function executes only on the local node. ## KSUUID v1 functions -Functions for working with `KSUUID` v1 data, K-Sortable UUID data(v1). Deprecated - See [KSUUID in the sequences documentation](/sequences/#ksuuids) for details. +Functions for working with `KSUUID` v1 data, K-Sortable UUID data(v1). Deprecated - See [KSUUID in the sequences documentation](../sequences/#ksuuids) for details. ### `bdr.gen_ksuuid` diff --git a/product_docs/docs/pge/15/deploy_options.mdx b/product_docs/docs/pge/15/deploy_options.mdx index bbfabab763c..4449770f1f7 100644 --- a/product_docs/docs/pge/15/deploy_options.mdx +++ b/product_docs/docs/pge/15/deploy_options.mdx @@ -11,6 +11,6 @@ The deployment options include: - [Installing](installing) on a virtual machine or physical server using native packages -- Deploying it with [EDB Postgres Distributed](/pgd/latest/) using [Trusted Postgres Architect](/pgd/latest/deployments/tpaexec/) +- Deploying it with [EDB Postgres Distributed](/pgd/latest/) using [Trusted Postgres Architect](/pgd/latest/tpa/) - Deploying it on [BigAnimal](/biganimal/latest/) with extreme high availability cluster types \ No newline at end of file diff --git a/product_docs/docs/pge/16/deploy_options.mdx b/product_docs/docs/pge/16/deploy_options.mdx index 3356f4933dc..4e1e57159ed 100644 --- a/product_docs/docs/pge/16/deploy_options.mdx +++ b/product_docs/docs/pge/16/deploy_options.mdx @@ -11,6 +11,6 @@ The deployment options include: - [Installing](installing) on a virtual machine or physical server using native packages -- Deploying it with [EDB Postgres Distributed](/pgd/latest/) using [Trusted Postgres Architect](/pgd/latest/deployments/tpaexec/) +- Deploying it with [EDB Postgres Distributed](/pgd/latest/) using [Trusted Postgres Architect](/pgd/latest/tpa/) - Deploying it on [BigAnimal](/biganimal/latest/) with extreme-high-availability cluster types \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/1/addons.mdx b/product_docs/docs/postgres_for_kubernetes/1/addons.mdx index c093535befc..1df046ea7e4 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/addons.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/addons.mdx @@ -405,7 +405,7 @@ Kasten is a very popular data protection tool for Kubernetes, enabling backup and restore, disaster recovery, and application mobility for Kubernetes applications. For more information, see the [Kasten website](https://www.kasten.io/) and the [Kasten by Veeam Implementation -Guide](/docs/partner_docs/KastenbyVeeam/) +Guide](/partner_docs/KastenbyVeeam/) In brief, to enable transparent integration with Kasten on an EDB Postgres for Kubernetes Cluster, you just need to add the `kasten` value to the @@ -439,8 +439,8 @@ k8s.enterprisedb.io/snapshotAllowColdBackupOnPrimary: enabled !!! For further guidance on how to configure and use Kasten, see the Implementation Guide's -[Configuration](/docs/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten/) and -[Using](/docs/partner_docs/KastenbyVeeam/05-UsingVeeamKasten/) sections. +[Configuration](/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten/) and +[Using](/partner_docs/KastenbyVeeam/05-UsingVeeamKasten/) sections. ### Limitations diff --git a/product_docs/docs/postgres_for_kubernetes/1/interactive_demo.mdx b/product_docs/docs/postgres_for_kubernetes/1/interactive_demo.mdx index d833fef4bfb..ad1f860d26f 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/interactive_demo.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/interactive_demo.mdx @@ -358,7 +358,7 @@ status: By default, the operator will install the latest available minor version of the latest major version of PostgreSQL when the operator was released. You can override this by setting [the `imageName` key in the `spec` section of - the `Cluster` definition](cloudnative-pg.v1/#clusterspec). + the `Cluster` definition](pg4k.v1/#clusterspec). !!! Important The immutable infrastructure paradigm requires that you always diff --git a/product_docs/docs/postgres_for_kubernetes/1/wal_archiving.mdx b/product_docs/docs/postgres_for_kubernetes/1/wal_archiving.mdx index b75441ee1b2..26385fee0ef 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/wal_archiving.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/wal_archiving.mdx @@ -16,7 +16,7 @@ the ["Backup on object stores" section](backup_barmanobjectstore.md) to set up the WAL archive. !!! Info - Please refer to [`BarmanObjectStoreConfiguration`](pg4k.v1.md#postgresql-k8s-enterprisedb-io-v1-barmanobjectstoreconfiguration) + Please refer to [`BarmanObjectStoreConfiguration`](pg4k.v1.md#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) in the API reference for a full list of options. If required, you can choose to compress WAL files as soon as they diff --git a/product_docs/docs/slony/2.2.10/01_installation/index.mdx b/product_docs/docs/slony/2.2.10/01_installation/index.mdx index 2ba84dd4d8d..552e6c75ff6 100644 --- a/product_docs/docs/slony/2.2.10/01_installation/index.mdx +++ b/product_docs/docs/slony/2.2.10/01_installation/index.mdx @@ -22,7 +22,7 @@ The following table lists the latest Slony Replication versions and their corres | `Slony Replication 2.2` | EDB Postgres Advanced and PostgreSQL Server 10 | RHEL 7 - x86_64
RHEL 7 - ppc64le
Windows x86_64 and Linux graphical installer | !!! Note - Slony is not supported by EDB Postgres Advanced Server or PostgreSQL version 14 and later. EDB strongly recommends that you move to [BDR](/bdr/latest/) or [pglogical](/pglogical/latest/) as your logical replication solution. + Slony is not supported by EDB Postgres Advanced Server or PostgreSQL version 14 and later. EDB strongly recommends that you move to [PGD](/pgd/latest/) or [pglogical](/pgd/3.7/pglogical/) as your logical replication solution.
diff --git a/product_docs/docs/tpa/23/reference/bdr.mdx b/product_docs/docs/tpa/23/reference/bdr.mdx index 75dc29dbd51..a9980ca1609 100644 --- a/product_docs/docs/tpa/23/reference/bdr.mdx +++ b/product_docs/docs/tpa/23/reference/bdr.mdx @@ -144,7 +144,7 @@ is mentioned in `bdr_node_groups`), it will join that group instead of ### bdr_commit_scopes This is an optional list of -[commit scopes](https://www.enterprisedb.com/docs/pgd/latest/bdr/group-commit/) +[commit scopes](https://www.enterprisedb.com/docs/pgd/latest/durability/group-commit/) that must exist in the PGD database (available for PGD 4.1 and above). ```yaml diff --git a/product_docs/docs/tpa/23/reference/reconciling-local-changes.mdx b/product_docs/docs/tpa/23/reference/reconciling-local-changes.mdx index 73c9b6a63ea..af4b549860a 100644 --- a/product_docs/docs/tpa/23/reference/reconciling-local-changes.mdx +++ b/product_docs/docs/tpa/23/reference/reconciling-local-changes.mdx @@ -87,7 +87,7 @@ undone unless they are: 1. Made in the `conf.d/9999-override.conf` file reserved for manual edits; 2. Made using `ALTER SYSTEM` SQL; or -3. Made [natively in TPA](#postgres_conf_settings) by adding +3. Made [natively in TPA](postgresql.conf/#postgres_conf_settings) by adding `postgres_conf_settings`. Other than the fact that option 3 is self-documenting and portable,