); \
+ END;",
+ db);
+otlCur.set_commit(0);
+
+otl_refcur_stream
+ s1; // reference cursor streams for reading rows.
+otl_refcur_stream
+ s2; // reference cursor streams for reading rows.
+otl_refcur_stream
+ s3; // reference cursor streams for reading rows.
+
+otlCur >> s1;
+otlCur >> s2;
+otlCur >> s3;
+
+int e_no;
+char name[11];
+double sal;
+double comm;
+
+cout << "=====> Reading :cur1..." << endl;
+while (!s1.eof()) { // while not end-of-data
+ s1 >> e_no >> name;
+ cout << "e_no=" << e_no << "\tname: " << name << endl;
+}
+
+cout << "=====> Reading :cur2..." << endl;
+while (!s2.eof()) { // while not end-of-data
+ s2 >> name >> sal;
+ cout << "name=" << name << "\tsalary: " << sal << endl;
+}
+
+cout << "=====> Reading :cur3..." << endl;
+while (!s3.eof()) { // while not end-of-data
+ s3 >> name >> comm;
+ cout << "name=" << name << "\tcommission: " << comm
+ << endl;
+}
+
+s1.close();
+s2.close();
+s3.close();
+```
diff --git a/product_docs/docs/ocl_connector/17/04_open_client_library/index.mdx b/product_docs/docs/ocl_connector/17/04_open_client_library/index.mdx
new file mode 100644
index 00000000000..abbf377bc34
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/04_open_client_library/index.mdx
@@ -0,0 +1,20 @@
+---
+title: "Open Client Library"
+
+---
+
+
+
+The Open Client Library provides application interoperability with the Oracle Call Interface. An application that was formerly locked in can now work with either an EDB Postgres Advanced Server or an Oracle database with minimal to no changes to the application code.
+
+The following diagram compares the Open Client Library and Oracle Call Interface application stacks.
+
+
+
+The EDB implementation of the Open Client Library is written in C.
+
+
+
+installing_and_configuring_the_ocl_connector forming_a_connection_string compiling_and_linking_a_program ref_cursor_support ocl_function_reference ocl_error_codes_reference multithreading_support otl_support
+
+
diff --git a/product_docs/docs/ocl_connector/17/05_generating_the_ocl_trace.mdx b/product_docs/docs/ocl_connector/17/05_generating_the_ocl_trace.mdx
new file mode 100644
index 00000000000..b6ef4d4b8da
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/05_generating_the_ocl_trace.mdx
@@ -0,0 +1,23 @@
+---
+title: "Generating the OCL trace"
+
+---
+
+
+
+The OCL tracing option logs direct communication (queries, updates, and so on) with the backend in the specified `OCI_DEBUG_LOG file`. It also logs the functions/APIs that were invoked. The trace files are generated in the default working directory (`oci_log_file_name`). If you append the path with a file name (`directory path/oci_log_file_name`), then the trace files are generated at that specific location.
+
+A trace file is generated for each connection in text-file (readable) format.
+
+!!! Note
+ OCL tracing is disabled by default.
+
+To generate the OCL trace:
+
+1. Enable the EDB client-side tracing for OCL. You can enable the OCL tracing by setting these environment variables:
+
+ - `export OCI_DEBUG_LEVEL=4`
+
+ - `export OCI_DEBUG_LOG=oci_log_file`
+
+2. After you export the environment variables, run the application. The OCL trace files are generated in the specified directory.
diff --git a/product_docs/docs/ocl_connector/17/06_using_ssl.mdx b/product_docs/docs/ocl_connector/17/06_using_ssl.mdx
new file mode 100644
index 00000000000..24810e0bada
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/06_using_ssl.mdx
@@ -0,0 +1,41 @@
+---
+title: "Using SSL"
+legacyRedirects:
+ - "/edb-docs/d/edb-postgres-ocl-connector/user-guides/ocl-guide/13.1.4.2/security_and_encryption.html"
+
+---
+
+
+
+EDB Postgres Advanced Server provides native support for using SSL connections to encrypt client/server communications for increased security. In OCL, it's controlled by setting the `sslmode` parameter to `verify-full` or `verify-ca` and providing the system with a root certificate to verify against.
+
+## Steps of SSL configuration
+
+1. Configure the server and client-side certificates. For detailed information about configuring SSL client and server-side certificates, refer to the [PostgreSQL SSL documentation](https://www.postgresql.org/docs/12/libpq-ssl.html).
+
+2. Enable the SSL OCL connection. In an OCL client application, you can enable SSL mode by setting the `EDB_ATTR_SSL` attribute in `Session`:
+
+```c
+char* sslmode = "verify-full";
+retValue = OCIAttrSet((dvoid*)authp,
+ (ub4)OCI_HTYPE_SESSION,
+ (dvoid*)sslmode,
+ (ub4)strlen((char*)sslmode),
+ (ub4)EDB_ATTR_SSL,
+ errhp);
+```
+
+!!! Note
+ `EDB_ATTR_SSL` is defined in the `edboci.h` header file available in the installation directory.
+
+3. After setting the SSL attribute, you can use the `OCILogon` function to create a connection:
+
+```c
+OCILogon(pEnv,pError,&pSvc,(OraText*)pUsername,ub4)UsernameLen,
+ (OraText*)pPassword,(ub4)PasswordLen,
+ (OraText*)pDatabase,(ub4)DatabaseLen);
+```
+
+Once the server is authenticated, then the client is ready to pass sensitive data.
+
+For more information about the supported SSL mode options, see the [PostgreSQL SSL documentation](https://www.postgresql.org/docs/13/libpq-ssl.html#LIBPQ-SSL-SSLMODE-STATEMENTS).
diff --git a/product_docs/docs/ocl_connector/17/07_scram_compatibility.mdx b/product_docs/docs/ocl_connector/17/07_scram_compatibility.mdx
new file mode 100644
index 00000000000..76b6fb8ed5d
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/07_scram_compatibility.mdx
@@ -0,0 +1,8 @@
+---
+title: "Scram compatibility"
+
+---
+
+
+
+The EDB OCL driver provides SCRAM-SHA-256 support for EDB Postgres Advanced Server version 11 and later. This support is available in EDB OCL 11.0.1 release and later.
diff --git a/product_docs/docs/ocl_connector/17/images/ocl_installation_complete.png b/product_docs/docs/ocl_connector/17/images/ocl_installation_complete.png
new file mode 100755
index 00000000000..18d535b6613
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/images/ocl_installation_complete.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:67fbe6582167a1866bdc942f3fa4b236d317b9449ae379295a5ae4099cf9bc66
+size 271262
diff --git a/product_docs/docs/ocl_connector/17/images/ocl_installation_dialog.png b/product_docs/docs/ocl_connector/17/images/ocl_installation_dialog.png
new file mode 100755
index 00000000000..f2c1ae42a67
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/images/ocl_installation_dialog.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc1616ae47691ad7f62d9a83ff3a9d29e64764069f8f7fdb8c96519bdd32c0a3
+size 48180
diff --git a/product_docs/docs/ocl_connector/17/images/ocl_installation_wizard.png b/product_docs/docs/ocl_connector/17/images/ocl_installation_wizard.png
new file mode 100755
index 00000000000..ac0f8bf3021
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/images/ocl_installation_wizard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c58c59f17592bc5ecd2bb856b4d2ecb5bad19041902727531ed0eb39ae93e56
+size 280241
diff --git a/product_docs/docs/ocl_connector/17/images/oracle_call_interface.png b/product_docs/docs/ocl_connector/17/images/oracle_call_interface.png
new file mode 100755
index 00000000000..211ceda4b45
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/images/oracle_call_interface.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c18e51dcc8b9ce545d2aaeb93ebcf7e51f95898ee0d408b8502cffcc27cfa193
+size 103652
diff --git a/product_docs/docs/ocl_connector/17/images/ready_to_install.png b/product_docs/docs/ocl_connector/17/images/ready_to_install.png
new file mode 100755
index 00000000000..4d2ce00c860
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/images/ready_to_install.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:198309699882c30c62c23f0889a2fc4299350803c6bbde38c34a62be67e878aa
+size 43327
diff --git a/product_docs/docs/ocl_connector/17/images/selecting_the_connectors_installer.png b/product_docs/docs/ocl_connector/17/images/selecting_the_connectors_installer.png
new file mode 100644
index 00000000000..67355eb32a8
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/images/selecting_the_connectors_installer.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d4dc68af55433c0c695eed059160505b3ee6c7d25c7d5426f4228109d84042a
+size 135650
diff --git a/product_docs/docs/ocl_connector/17/images/starting_stackbuilder_plus.png b/product_docs/docs/ocl_connector/17/images/starting_stackbuilder_plus.png
new file mode 100644
index 00000000000..11665300652
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/images/starting_stackbuilder_plus.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce6bcefb865ca14239fb7e0e2ac5149ed56251cfbc5153869070d039f70857c6
+size 91989
diff --git a/product_docs/docs/ocl_connector/17/index.mdx b/product_docs/docs/ocl_connector/17/index.mdx
new file mode 100644
index 00000000000..320791a4102
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/index.mdx
@@ -0,0 +1,21 @@
+---
+title: "EDB OCL Connector"
+directoryDefaults:
+ description: "EDB OCL Connector Version 17.1.0.1 Documentation and release notes."
+navigation:
+- ocl_rel_notes
+- 02_supported_platforms
+- 03_libpq_compatibility
+- installing
+- 04_open_client_library
+- 05_generating_the_ocl_trace
+- 06_using_ssl
+- 07_scram_compatibility
+---
+
+The EDB OCL Connector provides an API similar to the Oracle Call Interface. You can use EDB's OCL Connector to compile applications that are written to use the Oracle Call Interface to interact with an EDB Postgres Advanced Server database server.
+
+!!! Note
+ EDB doesn't support the use of the Open Client Library with Oracle Real Application Clusters (RAC) and Oracle Exadata. These Oracle products aren't evaluated or certified with this EDB product.
+
+
diff --git a/product_docs/docs/ocl_connector/17/installing/index.mdx b/product_docs/docs/ocl_connector/17/installing/index.mdx
new file mode 100644
index 00000000000..78a2585180f
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/index.mdx
@@ -0,0 +1,66 @@
+---
+navTitle: Installing
+title: Installing EDB OCL Connector
+# 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/edb-ocl-connector/index.njk
+
+redirects:
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/11_updating_rpm_install/
+ - /ocl_connector/17/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/17/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_ppc64le
+ - linux_x86_64
+ - linux_arm64
+ - windows
+ - upgrading
+---
+
+Select a link to access the applicable installation instructions:
+
+## Linux [x86-64 (amd64)](linux_x86_64)
+
+### Red Hat Enterprise Linux (RHEL) and derivatives
+
+- [RHEL 9](linux_x86_64/ocl_rhel_9), [RHEL 8](linux_x86_64/ocl_rhel_8)
+
+- [Oracle Linux (OL) 9](linux_x86_64/ocl_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/ocl_rhel_8)
+
+- [Rocky Linux 9](linux_x86_64/ocl_other_linux_9), [Rocky Linux 8](linux_x86_64/ocl_other_linux_8)
+
+- [AlmaLinux 9](linux_x86_64/ocl_other_linux_9), [AlmaLinux 8](linux_x86_64/ocl_other_linux_8)
+
+### SUSE Linux Enterprise (SLES)
+
+- [SLES 15](linux_x86_64/ocl_sles_15)
+
+### Debian and derivatives
+
+- [Ubuntu 22.04](linux_x86_64/ocl_ubuntu_22), [Ubuntu 20.04](linux_x86_64/ocl_ubuntu_20)
+
+- [Debian 12](linux_x86_64/ocl_debian_12), [Debian 11](linux_x86_64/ocl_debian_11)
+
+## Linux [IBM Power (ppc64le)](linux_ppc64le)
+
+### Red Hat Enterprise Linux (RHEL) and derivatives
+
+- [RHEL 9](linux_ppc64le/ocl_rhel_9), [RHEL 8](linux_ppc64le/ocl_rhel_8)
+
+### SUSE Linux Enterprise (SLES)
+
+- [SLES 15](linux_ppc64le/ocl_sles_15)
+
+## Linux [AArch64 (ARM64)](linux_arm64)
+
+### Debian and derivatives
+
+- [Debian 12](linux_arm64/ocl_debian_12)
+
+## Windows
+
+- [Windows Server 2019](windows)
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_arm64/index.mdx b/product_docs/docs/ocl_connector/17/installing/linux_arm64/index.mdx
new file mode 100644
index 00000000000..15061e86556
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_arm64/index.mdx
@@ -0,0 +1,13 @@
+---
+title: "Installing EDB OCL Connector on Linux AArch64 (ARM64)"
+navTitle: "On Linux ARM64"
+
+navigation:
+ - ocl_debian_12
+---
+
+Operating system-specific install instructions are described in the corresponding documentation:
+
+### Debian and derivatives
+
+- [Debian 12](ocl_debian_12)
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_debian_12.mdx b/product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_debian_12.mdx
new file mode 100644
index 00000000000..dad1e12ad53
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_debian_12.mdx
@@ -0,0 +1,47 @@
+---
+navTitle: Debian 12
+title: Installing EDB OCL Connector on Debian 12 arm64
+# 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.
+
+redirects:
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/arm64/ocl_deb12_arm
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
+
+ - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
+
+ - [Installing PostgreSQL](https://www.postgresql.org/download/)
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `apt-cache search enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+## Install the package
+
+```shell
+sudo apt-get -y install edb-oci
+sudo apt-get -y install edb-oci-dev
+```
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/index.mdx b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/index.mdx
new file mode 100644
index 00000000000..f11f64e7e38
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/index.mdx
@@ -0,0 +1,28 @@
+---
+title: "Installing EDB OCL Connector on Linux IBM Power (ppc64le)"
+navTitle: "On Linux ppc64le"
+# 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/edb-ocl-connector/ppc64le_index.njk
+
+redirects:
+ - /ocl_connector/latest/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/
+
+navigation:
+ - ocl_rhel_9
+ - ocl_rhel_8
+ - ocl_sles_15
+---
+
+Operating system-specific install instructions are described in the corresponding documentation:
+
+### Red Hat Enterprise Linux (RHEL)
+
+- [RHEL 9](ocl_rhel_9)
+
+- [RHEL 8](ocl_rhel_8)
+
+### SUSE Linux Enterprise (SLES)
+
+- [SLES 15](ocl_sles_15)
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_8.mdx
new file mode 100644
index 00000000000..b3e02a2e354
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_8.mdx
@@ -0,0 +1,56 @@
+---
+navTitle: RHEL 8
+title: Installing EDB OCL Connector on RHEL 8 ppc64le
+# 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.
+
+redirects:
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_rhel8_ppcle
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
+
+ - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
+
+ - [Installing PostgreSQL](https://www.postgresql.org/download/)
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `dnf repolist | grep enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+- Install the EPEL repository:
+ ```shell
+ sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
+ ```
+- Refresh the cache:
+ ```shell
+ sudo dnf makecache
+ ```
+
+## Install the package
+
+```shell
+sudo dnf -y install edb-oci
+sudo dnf -y install edb-oci-devel
+```
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_9.mdx
new file mode 100644
index 00000000000..82880a3afa4
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_9.mdx
@@ -0,0 +1,56 @@
+---
+navTitle: RHEL 9
+title: Installing EDB OCL Connector on RHEL 9 ppc64le
+# 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.
+
+redirects:
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_rhel9_ppcle
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
+
+ - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
+
+ - [Installing PostgreSQL](https://www.postgresql.org/download/)
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `dnf repolist | grep enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+- Install the EPEL repository:
+ ```shell
+ sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
+ ```
+- Refresh the cache:
+ ```shell
+ sudo dnf makecache
+ ```
+
+## Install the package
+
+```shell
+sudo dnf -y install edb-oci
+sudo dnf -y install edb-oci-devel
+```
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_sles_15.mdx
new file mode 100644
index 00000000000..ad6565f4165
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_sles_15.mdx
@@ -0,0 +1,57 @@
+---
+navTitle: SLES 15
+title: Installing EDB OCL Connector on SLES 15 ppc64le
+# 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.
+
+redirects:
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_sles15_ppcle
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
+
+ - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
+
+ - [Installing PostgreSQL](https://www.postgresql.org/download/)
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `zypper lr -E | grep enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+- Activate the required SUSE module:
+ ```shell
+ sudo SUSEConnect -p PackageHub/15.4/ppc64le
+
+ ```
+- Refresh the metadata:
+ ```shell
+ sudo zypper refresh
+ ```
+
+## Install the package
+
+```shell
+sudo zypper -n install edb-oci
+sudo zypper -n install edb-oci-devel
+```
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/index.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/index.mdx
new file mode 100644
index 00000000000..a4cba53524f
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/index.mdx
@@ -0,0 +1,56 @@
+---
+title: "Installing EDB OCL Connector on Linux x86 (amd64)"
+navTitle: "On Linux x86"
+# 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/edb-ocl-connector/x86_64_index.njk
+
+redirects:
+ - /ocl_connector/latest/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/
+
+navigation:
+ - ocl_rhel_9
+ - ocl_rhel_8
+ - ocl_other_linux_9
+ - ocl_other_linux_8
+ - ocl_sles_15
+ - ocl_ubuntu_22
+ - ocl_ubuntu_20
+ - ocl_debian_12
+ - ocl_debian_11
+---
+
+Operating system-specific install instructions are described in the corresponding documentation:
+
+### Red Hat Enterprise Linux (RHEL) and derivatives
+
+- [RHEL 9](ocl_rhel_9)
+
+- [RHEL 8](ocl_rhel_8)
+
+- [Oracle Linux (OL) 9](ocl_rhel_9)
+
+- [Oracle Linux (OL) 8](ocl_rhel_8)
+
+- [Rocky Linux 9](ocl_other_linux_9)
+
+- [Rocky Linux 8](ocl_other_linux_8)
+
+- [AlmaLinux 9](ocl_other_linux_9)
+
+- [AlmaLinux 8](ocl_other_linux_8)
+
+### SUSE Linux Enterprise (SLES)
+
+- [SLES 15](ocl_sles_15)
+
+### Debian and derivatives
+
+- [Ubuntu 22.04](ocl_ubuntu_22)
+
+- [Ubuntu 20.04](ocl_ubuntu_20)
+
+- [Debian 12](ocl_debian_12)
+
+- [Debian 11](ocl_debian_11)
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_11.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_11.mdx
new file mode 100644
index 00000000000..7a23b2ce96e
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_11.mdx
@@ -0,0 +1,47 @@
+---
+navTitle: Debian 11
+title: Installing EDB OCL Connector on Debian 11 x86_64
+# 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.
+
+redirects:
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb11_x86
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
+
+ - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
+
+ - [Installing PostgreSQL](https://www.postgresql.org/download/)
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `apt-cache search enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+## Install the package
+
+```shell
+sudo apt-get -y install edb-oci
+sudo apt-get -y install edb-oci-dev
+```
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_12.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_12.mdx
new file mode 100644
index 00000000000..698c410fc60
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_12.mdx
@@ -0,0 +1,47 @@
+---
+navTitle: Debian 12
+title: Installing EDB OCL Connector on Debian 12 x86_64
+# 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.
+
+redirects:
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb12_x86
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
+
+ - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
+
+ - [Installing PostgreSQL](https://www.postgresql.org/download/)
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `apt-cache search enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+## Install the package
+
+```shell
+sudo apt-get -y install edb-oci
+sudo apt-get -y install edb-oci-dev
+```
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_8.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_8.mdx
new file mode 100644
index 00000000000..6030c853780
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_8.mdx
@@ -0,0 +1,58 @@
+---
+navTitle: AlmaLinux 8 or Rocky Linux 8
+title: Installing EDB OCL Connector on AlmaLinux 8 or Rocky Linux 8 x86_64
+# 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.
+
+redirects:
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_other_linux8_x86
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
+
+ - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
+
+ - [Installing PostgreSQL](https://www.postgresql.org/download/)
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `dnf repolist | grep enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+- Install the EPEL repository:
+
+ ```shell
+ sudo dnf -y install epel-release
+ ```
+
+- Enable additional repositories to resolve dependencies:
+ ```shell
+ sudo dnf config-manager --set-enabled powertools
+ ```
+
+## Install the package
+
+```shell
+sudo dnf -y install edb-oci
+sudo dnf -y install edb-oci-devel
+```
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_9.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_9.mdx
new file mode 100644
index 00000000000..55fc257ca65
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_9.mdx
@@ -0,0 +1,58 @@
+---
+navTitle: AlmaLinux 9 or Rocky Linux 9
+title: Installing EDB OCL Connector on AlmaLinux 9 or Rocky Linux 9 x86_64
+# 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.
+
+redirects:
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_other_linux9_x86
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
+
+ - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
+
+ - [Installing PostgreSQL](https://www.postgresql.org/download/)
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `dnf repolist | grep enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+- Install the EPEL repository:
+
+ ```shell
+ sudo dnf -y install epel-release
+ ```
+
+- Enable additional repositories to resolve dependencies:
+ ```shell
+ sudo dnf config-manager --set-enabled crb
+ ```
+
+## Install the package
+
+```shell
+sudo dnf -y install edb-oci
+sudo dnf -y install edb-oci-devel
+```
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_8.mdx
new file mode 100644
index 00000000000..0d1ed3654f5
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_8.mdx
@@ -0,0 +1,52 @@
+---
+navTitle: RHEL 8 or OL 8
+title: Installing EDB OCL Connector on RHEL 8 or OL 8 x86_64
+# 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.
+
+redirects:
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel8_x86
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
+
+ - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
+
+ - [Installing PostgreSQL](https://www.postgresql.org/download/)
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `dnf repolist | grep enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+- Install the EPEL repository:
+ ```shell
+ sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
+ ```
+
+## Install the package
+
+```shell
+sudo dnf -y install edb-oci
+sudo dnf -y install edb-oci-devel
+```
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_9.mdx
new file mode 100644
index 00000000000..446f10ef6bb
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_9.mdx
@@ -0,0 +1,52 @@
+---
+navTitle: RHEL 9 or OL 9
+title: Installing EDB OCL Connector on RHEL 9 or OL 9 x86_64
+# 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.
+
+redirects:
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel9_x86
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
+
+ - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
+
+ - [Installing PostgreSQL](https://www.postgresql.org/download/)
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `dnf repolist | grep enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+- Install the EPEL repository:
+ ```shell
+ sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
+ ```
+
+## Install the package
+
+```shell
+sudo dnf -y install edb-oci
+sudo dnf -y install edb-oci-devel
+```
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_sles_15.mdx
new file mode 100644
index 00000000000..5f53b6e77a5
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_sles_15.mdx
@@ -0,0 +1,57 @@
+---
+navTitle: SLES 15
+title: Installing EDB OCL Connector on SLES 15 x86_64
+# 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.
+
+redirects:
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_sles15_x86
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
+
+ - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
+
+ - [Installing PostgreSQL](https://www.postgresql.org/download/)
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `zypper lr -E | grep enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+- Activate the required SUSE module:
+ ```shell
+ sudo SUSEConnect -p PackageHub/15.4/x86_64
+
+ ```
+- Refresh the metadata:
+ ```shell
+ sudo zypper refresh
+ ```
+
+## Install the package
+
+```shell
+sudo zypper -n install edb-oci
+sudo zypper -n install edb-oci-devel
+```
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_20.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_20.mdx
new file mode 100644
index 00000000000..5adec88882d
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_20.mdx
@@ -0,0 +1,47 @@
+---
+navTitle: Ubuntu 20.04
+title: Installing EDB OCL Connector on Ubuntu 20.04 x86_64
+# 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.
+
+redirects:
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_ubuntu20_x86
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
+
+ - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
+
+ - [Installing PostgreSQL](https://www.postgresql.org/download/)
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `apt-cache search enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+## Install the package
+
+```shell
+sudo apt-get -y install edb-oci
+sudo apt-get -y install edb-oci-dev
+```
diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_22.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_22.mdx
new file mode 100644
index 00000000000..044572e9b13
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_22.mdx
@@ -0,0 +1,47 @@
+---
+navTitle: Ubuntu 22.04
+title: Installing EDB OCL Connector on Ubuntu 22.04 x86_64
+# 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.
+
+redirects:
+ - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_ubuntu22_x86
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
+
+ - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
+
+ - [Installing PostgreSQL](https://www.postgresql.org/download/)
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `apt-cache search enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+## Install the package
+
+```shell
+sudo apt-get -y install edb-oci
+sudo apt-get -y install edb-oci-dev
+```
diff --git a/product_docs/docs/ocl_connector/17/installing/upgrading.mdx b/product_docs/docs/ocl_connector/17/installing/upgrading.mdx
new file mode 100644
index 00000000000..26b0bdbaa23
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/upgrading.mdx
@@ -0,0 +1,32 @@
+---
+title: "Upgrading a Linux installation"
+navTitle: "Upgrading"
+redirects:
+ - /ocl_connector/latest/04_open_client_library/01_installing_and_configuring_the_ocl_connector/11_updating_rpm_install/
+---
+
+
+If you have an existing OCL Connector installation on a Linux platform, you can upgrade your repository configuration file, which enables access to the current EDB repository. Then you can upgrade to a more recent version of OCL Connector.
+
+To update the `edb.repo` file:
+
+```shell
+# Update your repository configuration file
+sudo upgrade edb-repo
+
+# Upgrade the installed product
+sudo upgrade edb-oci
+
+sudo upgrade edb-oci-devel
+```
+
+Where `` is the package manager used with your operating system:
+
+ | Package manager | Operating system |
+ | --------------- | -------------------------------- |
+ | dnf | RHEL 8/9 and derivatives |
+ | zypper | SLES |
+ | apt-get | Debian and Ubuntu |
+
+
+
diff --git a/product_docs/docs/ocl_connector/17/installing/windows.mdx b/product_docs/docs/ocl_connector/17/installing/windows.mdx
new file mode 100644
index 00000000000..3492cb8a10a
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/installing/windows.mdx
@@ -0,0 +1,50 @@
+---
+title: "Installing on Windows"
+navTitle: "On Windows"
+redirects:
+ - /ocl_connector/latest/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_windows/
+---
+
+EDB provides a graphical interactive installer for Windows. You can access it in two ways:
+
+- Download the graphical installer from the [Downloads page](https://www.enterprisedb.com/software-downloads-postgres#connectors), and invoke the installer directly. See [Installing directly](#installing-directly).
+
+- Use StackBuilder Plus with EDB Postgres Advanced Server to download the EDB installer package and invoke the graphical installer. See [Using StackBuilder Plus](#using-stackbuilder-plus).
+
+
+## Installing directly
+
+After downloading the graphical installer, to start the installation wizard, assume sufficient privileges (superuser or administrator) and double-click the installer icon. If prompted, provide a password.
+
+In some versions of Windows, to invoke the installer with administrator privileges, you need to right-click the installer icon and select **Run as Administrator** from the context menu.
+
+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/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.
+
+ On the Welcome page, from the list of available servers, select the target server installation. If your network requires you to use a proxy server to access the internet, select **Proxy servers** and specify a server. Select **Next**.
+
+1. Expand the **Database Drivers** node, and select **EnterpriseDB OCI Connector**.
+
+1. Proceed to [Using the graphical installer](#using-the-graphical-installer).
+
+
+## Using the graphical installer
+
+1. Select the installation language and select **OK**.
+
+1. On the Setup OCI page, select **Next**.
+
+1. Browse to a directory where you want to install OCI, or leave the directory set to the default location. Select **Next**.
+
+1. On the Ready to Install page, select **Next**.
+
+ An information box shows the installation progress of the selected components.
+
+1. When the installation is complete, select **Finish**.
+
diff --git a/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx
new file mode 100644
index 00000000000..daf9c4ea6b7
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx
@@ -0,0 +1,14 @@
+---
+title: "EDB OCL Connector 17.2.0.1 release notes"
+navTitle: Version 17.2.0.1
+---
+
+Released: 22 Nov 2024
+
+The EDB OCL Connector provides an API similar to the Oracle Call Interface.
+
+New features, enhancements, bug fixes, and other changes in the EDB OCL Connector 17.2.0.1 include:
+
+| Type | Description |
+| ----------- | ----------------------------------------------------------- |
+| Enhancement | Added support for EDB Postgres Advanced Server version 17.2. |
diff --git a/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx b/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx
new file mode 100644
index 00000000000..383171cfb8e
--- /dev/null
+++ b/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx
@@ -0,0 +1,14 @@
+---
+title: "EDB OCL Connector release notes"
+navTitle: Release Notes
+navigation:
+ - 17.2.0.1_ocl_release_notes
+---
+
+The EDB OCL connector documentation describes the latest version of the EDB OCL connector.
+
+Release notes describe what's new in a release. When a minor or patch release introduces new functionality, indicators in the content identify the version that introduced the new feature.
+
+| Version | Release date |
+| -------------------------------------- | ------------ |
+| [17.2.0.1](17.2.0.1_ocl_release_notes) | 22 Nov 2024 |
diff --git a/product_docs/docs/pge/17/administration/01_setting_configuration_parameters.mdx b/product_docs/docs/pge/17/administration/01_setting_configuration_parameters.mdx
new file mode 100644
index 00000000000..6a0cd8e19c1
--- /dev/null
+++ b/product_docs/docs/pge/17/administration/01_setting_configuration_parameters.mdx
@@ -0,0 +1,95 @@
+---
+title: "Setting configuration parameters"
+navTitle: "Setting configuration parameters"
+description: "Describes how to set the configuration parameters for EDB Postgres Extended Server."
+---
+
+Set each configuration parameter using a name/value pair. Parameter names aren't case sensitive. The parameter name is typically separated from its value by an optional equals sign (`=`).
+
+This example shows some configuration parameter settings in the `postgresql.conf` file:
+
+```ini
+# This is a comment
+log_connections = yes
+log_destination = 'syslog'
+search_path = '"$user", public'
+shared_buffers = 128MB
+```
+
+## Types of parameter values
+
+Parameter values are specified as one of five types:
+
+- **Boolean** — Acceptable values are `on`, `off`, `true`, `false`, `yes`, `no`, `1`, `0`, or any unambiguous prefix of these.
+- **Integer** — Number without a fractional part.
+- **Floating point** — Number with an optional fractional part separated by a decimal point.
+- **String** — Text value enclosed in single quotes if the value isn't a simple identifier or number, that is, the value contains special characters such as spaces or other punctuation marks.
+- **Enum** — Specific set of string values. The allowed values can be found in the system view `pg_settings.enumvals`. Enum values are not case sensitive.
+
+Some settings specify a memory or time value. Each of these has an implicit unit, which is kilobytes, blocks (typically 8 kilobytes), milliseconds, seconds, or minutes. You can find default units by referencing the system view `pg_settings.unit`. You can specify a different unit explicitly.
+
+Valid memory units are:
+- `kB` (kilobytes)
+- `MB` (megabytes)
+- `GB` (gigabytes).
+
+Valid time units are:
+- `ms` (milliseconds)
+- `s` (seconds)
+- `min` (minutes)
+- `h` (hours)
+- `d` (days).
+
+The multiplier for memory units is 1024.
+
+## Specifying configuration parameter settings
+
+A number of parameter settings are set when the EDB Postgres Extended Server database product is built. These are read-only parameters, and you can't change their values. A couple of parameters are also permanently set for each database when the database is created. These parameters are read-only and you can't later change them for the database. However, there are a number of ways to specify the configuration parameter settings:
+
+- The initial settings for almost all configurable parameters across the entire database cluster are listed in the `postgresql.conf` configuration file. These settings are put into effect upon database server start or restart. You can override some of these initial parameter settings. All configuration parameters have built-in default settings that are in effect unless you explicitly override them.
+
+- Configuration parameters in the `postgresql.conf` file are overridden when the same parameters are included in the `postgresql.auto.conf` file. Use the `ALTER SYSTEM` command to manage the configuration parameters in the `postgresql.auto.conf` file.
+
+- You can modify parameter settings in the configuration file while the database server is running. If the configuration file is then reloaded (meaning a SIGHUP signal is issued), for certain parameter types, the changed parameters settings immediately take effect. For some of these parameter types, the new settings are available in a currently running session immediately after the reload. For others, you must start a new session to use the new settings. And for some others, modified settings don't take effect until the database server is stopped and restarted. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/config-setting.html) for information on how to reload the configuration file.
+
+- You can use the SQL commands `ALTER DATABASE`, `ALTER ROLE`, or `ALTER ROLE IN DATABASE` to modify certain parameter settings. The modified parameter settings take effect for new sessions after you execute the command. `ALTER DATABASE` affects new sessions connecting to the specified database. `ALTER ROLE` affects new sessions started by the specified role. `ALTER ROLE IN DATABASE` affects new sessions started by the specified role connecting to the specified database. Parameter settings established by these SQL commands remain in effect indefinitely, across database server restarts, overriding settings established by the other methods. You can change parameter settings established using the `ALTER DATABASE`, `ALTER ROLE`, or `ALTER ROLE IN DATABASE` commands by either:
+
+ - Reissuing these commands with a different parameter value.
+
+ - Issuing these commands using the `SET parameter TO DEFAULT` clause or the `RESET parameter` clause. These clauses change the parameter back to using the setting set by the other methods. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/sql-commands.html) for the syntax of these SQL commands.
+
+- You can make changes for certain parameter settings for the duration of individual sessions using the `PGOPTIONS` environment variable or by using the `SET` command in the EDB-PSQL or PSQL command-line programs. Parameter settings made this way override settings established using any of the methods discussed earlier, but only during that session.
+
+## Modifying the postgresql.conf file
+
+The configuration parameters in the `postgresql.conf` file specify server behavior with regard to auditing, authentication, encryption, and other behaviors. On Linux and Windows hosts, the `postgresql.conf` file resides in the `data` directory under your EDB Postgres Extended Server installation.
+
+Parameters that are preceded by a pound sign (#) are set to their default value. To change a parameter value, remove the pound sign and enter a new value. After setting or changing a parameter, you must either `reload` or `restart` the server for the new parameter value to take effect.
+
+In the `postgresql.conf` file, some parameters contain comments that indicate `change requires restart`. To view a list of the parameters that require a server restart, use the following query at the psql command line:
+
+```sql
+SELECT name FROM pg_settings WHERE context = 'postmaster';
+```
+
+
+
+## Modifying the pg_hba.conf file
+
+Appropriate authentication methods provide protection and security. Entries in the `pg_hba.conf` file specify the authentication methods that the server uses with connecting clients. Before connecting to the server, you might need to modify the authentication properties specified in the `pg_hba.conf` file.
+
+When you invoke the initdb utility to create a cluster, the utility creates a `pg_hba.conf` file for that cluster that specifies the type of authentication required from connecting clients. You can modify this file. After modifying the authentication settings in the `pg_hba.conf` file, restart the server and apply the changes. For more information about authentication and modifying the `pg_hba.conf` file, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html).
+
+When the server receives a connection request, it verifies the credentials provided against the authentication settings in the `pg_hba.conf` file before allowing a connection to a database. To log the `pg_hba.conf` file entry to authenticate a connection to the server, set the `log_connections` parameter to `ON` in the `postgresql.conf` file.
+
+A record specifies a connection type, database name, user name, client IP address, and the authentication method to authorize a connection upon matching these parameters in the `pg_hba.conf` file. Once the connection to a server is authorized, you can see the matched line number and the authentication record from the `pg_hba.conf` file.
+
+This example shows a log detail for a valid `pg_hba.conf` entry after successful authentication:
+
+```shell
+2020-05-08 10:42:17 IST LOG: connection received: host=[local]
+2020-05-08 10:42:17 IST LOG: connection authorized: user=u1 database=edb
+application_name=psql
+2020-05-08 10:42:17 IST DETAIL: Connection matched pg_hba.conf line 84:
+"local all all md5"
+```
diff --git a/product_docs/docs/pge/17/administration/index.mdx b/product_docs/docs/pge/17/administration/index.mdx
new file mode 100644
index 00000000000..08b4255196f
--- /dev/null
+++ b/product_docs/docs/pge/17/administration/index.mdx
@@ -0,0 +1,16 @@
+---
+title: "Database configuration"
+description: "How to configure EDB Postgres Extended Server databases."
+navigation:
+- 01_configuration_parameters
+---
+
+EDB Postgres Extended Server includes features to help you to maintain, secure, and operate EDB Postgres Extended Server databases.
+
+You can configure grand unified configuration (GUC) parameters at runtime by modifying the `postgresql.conf` and `pg_hba.conf` files.
+
+- The `postgresql.conf` file allows you to make persistent changes to your database configuration.
+- The `pg_hba.conf` file allows you to change access and authentication settings.
+
+See [Setting configuration parameters](01_setting_configuration_parameters) for more information.
+
diff --git a/product_docs/docs/pge/17/deploy_options.mdx b/product_docs/docs/pge/17/deploy_options.mdx
new file mode 100644
index 00000000000..7499961f6ff
--- /dev/null
+++ b/product_docs/docs/pge/17/deploy_options.mdx
@@ -0,0 +1,14 @@
+---
+
+title: Deployment options
+originalFilePath: index.md
+description: Deployment options available for EDB Postgres Extended Server.
+---
+
+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/deploy-config/deploy-tpa/)
+
+- Deploying it on [EDB Postgres AI Cloud Service](/edb-postgres-ai/cloud-service/) with extreme-high-availability cluster types
diff --git a/product_docs/docs/pge/17/extensions.mdx b/product_docs/docs/pge/17/extensions.mdx
new file mode 100644
index 00000000000..86bf83bce1d
--- /dev/null
+++ b/product_docs/docs/pge/17/extensions.mdx
@@ -0,0 +1,13 @@
+---
+navTitle: Extensions
+title: Postgres extensions supported in EDB Postgres Extended Server
+description: Postgres extensions supported in EDB Postgres Extended Server.
+---
+
+EDB provides support for several Postgres extensions on EDB Postgres Extended Server:
+
+- Open-source extensions
+- EDB supported open-source extensions
+- EDB-developed extensions
+
+See [Postgres extensions available by deployment](/pg_extensions/) for an overview of all supported extensions and links to their documentation sites.
\ No newline at end of file
diff --git a/product_docs/docs/pge/17/index.mdx b/product_docs/docs/pge/17/index.mdx
new file mode 100644
index 00000000000..daaeaa72cb7
--- /dev/null
+++ b/product_docs/docs/pge/17/index.mdx
@@ -0,0 +1,34 @@
+---
+title: EDB Postgres Extended Server
+originalFilePath: index.md
+navigation:
+ - release_notes
+ - "#Get Started"
+ - deploy_options
+ - installing
+ - administration
+ - "#Features"
+ - tde
+ - replication
+ - extensions
+ - "#Upgrade"
+ - upgrading
+ - "#Reference"
+ - parameters
+ - sql_features
+ - operation
+indexCards: simple
+---
+
+EDB Postgres Extended Server is a Postgres database server distribution built on open-source, community PostgreSQL. It's fully compatible with PostgreSQL. If you have applications written and tested to work with PostgreSQL, they will behave the same with EDB Postgres Extended Server. We will support and fix any functionality or behavior differences between community PostgreSQL and EDB Postgres Extended Server.
+
+EDB Postgres Extended Server's primary purpose is to extend PostgreSQL with a limited number of features that can't be implemented as extensions, such as [enhanced replication optimization](replication) used by [EDB Postgres Distributed](/pgd/latest/) and [Transparent Data Encryption](/tde/latest/), while maintaining parity in other respects.
+
+Additional value-add enterprise features include:
+- Security though [Transparent Data Encryption](/tde/latest/)
+
+- Optional [SQL superset](sql_features) to community PostgreSQL
+- [WAL pacing delays to avoid flooding transaction logs](./operation/#avoid-flooding-transaction-logs)
+- [Additional tracing and diagnostics options](./operation/#additional-tracing-and-diagnostics-options)
+
+---
diff --git a/product_docs/docs/pge/17/installing/component_locations.mdx b/product_docs/docs/pge/17/installing/component_locations.mdx
new file mode 100644
index 00000000000..90d1525fda4
--- /dev/null
+++ b/product_docs/docs/pge/17/installing/component_locations.mdx
@@ -0,0 +1,43 @@
+---
+title: Default component locations
+navTitle: Component locations
+description: "Provides information about accessing EDB Postgres Extended Server components after installation."
+---
+
+The package managers for the various Linux variations install EDB Postgres Extended Server components in different locations. If you need to access the components after installation, see:
+
+- [RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES locations](#rhelolrocky-linuxalmalinuxcentossles-locations)
+- [Debian/Ubuntu locations](#debianubuntu-locations)
+
+## RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Locations
+
+The RPM installers place EDB Postgres Extended Server components in the directories listed in the table.
+
+| Component | Location |
+|-----------------------------|--------------------------------|
+| Executables | `/usr/edb/pge16/bin` |
+| Libraries | `/usr/edb/pge16/lib` |
+| Cluster configuration files | `/var/lib/edb-pge/16` |
+| Documentation | `/usr/edb/pge16/share/man` |
+| Contrib | `/usr/edb/pge16/share/contrib` |
+| Data | `/var/lib/edb-pge/16/data` |
+| Logs | `/var/log/edb/pge16` |
+| Lock files | `/var/lock/edb/pge16` |
+| Backup area | `/var/lib/edb-pge/16/backups` |
+| Templates | `/usr/edb/pge16/share` |
+| Procedural Languages | `/usr/edb/pge16/lib` |
+| Development Headers | `/usr/edb/pge16/include` |
+| Shared data | `/usr/edb/pge16/share` |
+
+## Debian/Ubuntu Locations
+
+The Debian package manager places EDB Postgres Extended Server components in the directories listed in the table.
+
+| Component | Location |
+|-----------------------------|------------------------------------|
+| Executables | `/usr/lib/edb-pge/16/bin` |
+| Libraries | `/usr/lib/edb-pge/16/lib` |
+| Cluster configuration files | `/var/lib/edb-pge/16/main` |
+| Data | `/var/lib/edb-pge/16/main` |
+| Logs | `/var/log/edb-pge/` |
+| Lock files | `/var/lock/edb/pge16` |
diff --git a/product_docs/docs/pge/17/installing/index.mdx b/product_docs/docs/pge/17/installing/index.mdx
new file mode 100644
index 00000000000..0cc88e55d5e
--- /dev/null
+++ b/product_docs/docs/pge/17/installing/index.mdx
@@ -0,0 +1,36 @@
+---
+navTitle: Installing
+title: Installing EDB Postgres Extended Server on Linux
+
+description: Installation instructions for EDB Postgres Extended Server on Linux.
+
+navigation:
+ - linux_x86_64
+ - linux_arm64
+---
+
+Select a link to access the applicable installation instructions:
+
+## Linux [x86-64 (amd64)](linux_x86_64)
+
+### Red Hat Enterprise Linux (RHEL) and derivatives
+
+- [RHEL 9](linux_x86_64/pge_rhel_9), [RHEL 8](linux_x86_64/pge_rhel_8)
+
+- [Oracle Linux (OL) 9](linux_x86_64/pge_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pge_rhel_8)
+
+- [Rocky Linux 9](linux_x86_64/pge_other_linux_9), [Rocky Linux 8](linux_x86_64/pge_other_linux_8)
+
+- [AlmaLinux 9](linux_x86_64/pge_other_linux_9), [AlmaLinux 8](linux_x86_64/pge_other_linux_8)
+
+### Debian and derivatives
+
+- [Ubuntu 22.04](linux_x86_64/pge_ubuntu_22), [Ubuntu 20.04](linux_x86_64/pge_ubuntu_20)
+
+- [Debian 12](linux_x86_64/pge_debian_12), [Debian 11](linux_x86_64/pge_debian_11)
+
+## Linux [AArch64 (ARM64)](linux_arm64)
+
+### Debian and derivatives
+
+- [Debian 12](linux_arm64/pge_debian_12)
diff --git a/product_docs/docs/pge/17/installing/linux_arm64/index.mdx b/product_docs/docs/pge/17/installing/linux_arm64/index.mdx
new file mode 100644
index 00000000000..230f6000758
--- /dev/null
+++ b/product_docs/docs/pge/17/installing/linux_arm64/index.mdx
@@ -0,0 +1,13 @@
+---
+title: "Installing EDB Postgres Extended Server on Linux AArch64 (ARM64)"
+navTitle: "On Linux ARM64"
+
+navigation:
+ - pge_debian_12
+---
+
+Operating system-specific install instructions are described in the corresponding documentation:
+
+### Debian and derivatives
+
+- [Debian 12](pge_debian_12)
diff --git a/product_docs/docs/pge/17/installing/linux_arm64/pge_debian_12.mdx b/product_docs/docs/pge/17/installing/linux_arm64/pge_debian_12.mdx
new file mode 100644
index 00000000000..c3832d6fa55
--- /dev/null
+++ b/product_docs/docs/pge/17/installing/linux_arm64/pge_debian_12.mdx
@@ -0,0 +1,124 @@
+---
+navTitle: Debian 12
+title: Installing EDB Postgres Extended Server on Debian 12 arm64
+# 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.
+
+redirects:
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `apt-cache search enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+## Install the package
+
+```shell
+sudo apt-get -y install edb-postgresextended-17
+```
+
+## Initial configuration
+
+This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password.
+
+First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster.
+
+```shell
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/17/bin/edb-pge-17-setup initdb
+
+sudo systemctl start edb-pge-17
+```
+
+To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
+
+```shell
+sudo -iu postgres
+
+psql postgres
+```
+
+The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
+
+Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
+
+```sql
+ALTER ROLE postgres with PASSWORD 'password';
+```
+
+## Experiment
+
+Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
+
+First, use psql to create a database named `hr` to hold human resource information.
+
+```sql
+# running in psql
+CREATE DATABASE hr;
+__OUTPUT__
+CREATE DATABASE
+```
+
+Connect to the `hr` database inside psql:
+
+```
+\c hr
+__OUTPUT__
+You are now connected to database "hr" as user "postgres".
+```
+
+Create columns to hold department numbers, unique department names, and locations:
+
+```
+CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
+PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
+varchar(13));
+__OUTPUT__
+CREATE TABLE
+```
+
+Insert values into the `dept` table:
+
+```
+INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
+__OUTPUT__
+INSERT 0 1
+```
+
+```
+INSERT into dept VALUES (20,'RESEARCH','DALLAS');
+__OUTPUT__
+INSERT 0 1
+```
+
+View the table data by selecting the values from the table:
+
+```
+SELECT * FROM dept;
+__OUTPUT__
+deptno | dname | loc
+--------+------------+----------
+10 | ACCOUNTING | NEW YORK
+20 | RESEARCH | DALLAS
+(2 rows)
+```
diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/index.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/index.mdx
new file mode 100644
index 00000000000..0ec9f379e21
--- /dev/null
+++ b/product_docs/docs/pge/17/installing/linux_x86_64/index.mdx
@@ -0,0 +1,44 @@
+---
+title: "Installing EDB Postgres Extended Server on Linux x86 (amd64)"
+navTitle: "On Linux x86"
+
+navigation:
+ - pge_rhel_9
+ - pge_rhel_8
+ - pge_other_linux_9
+ - pge_other_linux_8
+ - pge_ubuntu_22
+ - pge_ubuntu_20
+ - pge_debian_12
+ - pge_debian_11
+---
+
+Operating system-specific install instructions are described in the corresponding documentation:
+
+### Red Hat Enterprise Linux (RHEL) and derivatives
+
+- [RHEL 9](pge_rhel_9)
+
+- [RHEL 8](pge_rhel_8)
+
+- [Oracle Linux (OL) 9](pge_rhel_9)
+
+- [Oracle Linux (OL) 8](pge_rhel_8)
+
+- [Rocky Linux 9](pge_other_linux_9)
+
+- [Rocky Linux 8](pge_other_linux_8)
+
+- [AlmaLinux 9](pge_other_linux_9)
+
+- [AlmaLinux 8](pge_other_linux_8)
+
+### Debian and derivatives
+
+- [Ubuntu 22.04](pge_ubuntu_22)
+
+- [Ubuntu 20.04](pge_ubuntu_20)
+
+- [Debian 12](pge_debian_12)
+
+- [Debian 11](pge_debian_11)
diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_11.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_11.mdx
new file mode 100644
index 00000000000..15ead90f66e
--- /dev/null
+++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_11.mdx
@@ -0,0 +1,124 @@
+---
+navTitle: Debian 11
+title: Installing EDB Postgres Extended Server on Debian 11 x86_64
+# 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.
+
+redirects:
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `apt-cache search enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+## Install the package
+
+```shell
+sudo apt-get -y install edb-postgresextended-17
+```
+
+## Initial configuration
+
+This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password.
+
+First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster.
+
+```shell
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/17/bin/edb-pge-17-setup initdb
+
+sudo systemctl start edb-pge-17
+```
+
+To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
+
+```shell
+sudo -iu postgres
+
+psql postgres
+```
+
+The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
+
+Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
+
+```sql
+ALTER ROLE postgres with PASSWORD 'password';
+```
+
+## Experiment
+
+Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
+
+First, use psql to create a database named `hr` to hold human resource information.
+
+```sql
+# running in psql
+CREATE DATABASE hr;
+__OUTPUT__
+CREATE DATABASE
+```
+
+Connect to the `hr` database inside psql:
+
+```
+\c hr
+__OUTPUT__
+You are now connected to database "hr" as user "postgres".
+```
+
+Create columns to hold department numbers, unique department names, and locations:
+
+```
+CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
+PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
+varchar(13));
+__OUTPUT__
+CREATE TABLE
+```
+
+Insert values into the `dept` table:
+
+```
+INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
+__OUTPUT__
+INSERT 0 1
+```
+
+```
+INSERT into dept VALUES (20,'RESEARCH','DALLAS');
+__OUTPUT__
+INSERT 0 1
+```
+
+View the table data by selecting the values from the table:
+
+```
+SELECT * FROM dept;
+__OUTPUT__
+deptno | dname | loc
+--------+------------+----------
+10 | ACCOUNTING | NEW YORK
+20 | RESEARCH | DALLAS
+(2 rows)
+```
diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_12.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_12.mdx
new file mode 100644
index 00000000000..9f268a516ff
--- /dev/null
+++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_12.mdx
@@ -0,0 +1,124 @@
+---
+navTitle: Debian 12
+title: Installing EDB Postgres Extended Server on Debian 12 x86_64
+# 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.
+
+redirects:
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `apt-cache search enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+## Install the package
+
+```shell
+sudo apt-get -y install edb-postgresextended-17
+```
+
+## Initial configuration
+
+This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password.
+
+First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster.
+
+```shell
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/17/bin/edb-pge-17-setup initdb
+
+sudo systemctl start edb-pge-17
+```
+
+To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
+
+```shell
+sudo -iu postgres
+
+psql postgres
+```
+
+The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
+
+Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
+
+```sql
+ALTER ROLE postgres with PASSWORD 'password';
+```
+
+## Experiment
+
+Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
+
+First, use psql to create a database named `hr` to hold human resource information.
+
+```sql
+# running in psql
+CREATE DATABASE hr;
+__OUTPUT__
+CREATE DATABASE
+```
+
+Connect to the `hr` database inside psql:
+
+```
+\c hr
+__OUTPUT__
+You are now connected to database "hr" as user "postgres".
+```
+
+Create columns to hold department numbers, unique department names, and locations:
+
+```
+CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
+PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
+varchar(13));
+__OUTPUT__
+CREATE TABLE
+```
+
+Insert values into the `dept` table:
+
+```
+INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
+__OUTPUT__
+INSERT 0 1
+```
+
+```
+INSERT into dept VALUES (20,'RESEARCH','DALLAS');
+__OUTPUT__
+INSERT 0 1
+```
+
+View the table data by selecting the values from the table:
+
+```
+SELECT * FROM dept;
+__OUTPUT__
+deptno | dname | loc
+--------+------------+----------
+10 | ACCOUNTING | NEW YORK
+20 | RESEARCH | DALLAS
+(2 rows)
+```
diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_8.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_8.mdx
new file mode 100644
index 00000000000..7747051e4fd
--- /dev/null
+++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_8.mdx
@@ -0,0 +1,135 @@
+---
+navTitle: AlmaLinux 8 or Rocky Linux 8
+title: Installing EDB Postgres Extended Server on AlmaLinux 8 or Rocky Linux 8 x86_64
+# 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.
+
+redirects:
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `dnf repolist | grep enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+- Install the EPEL repository:
+
+ ```shell
+ sudo dnf -y install epel-release
+ ```
+
+- Enable additional repositories to resolve dependencies:
+ ```shell
+ sudo dnf config-manager --set-enabled powertools
+ ```
+
+## Install the package
+
+```shell
+sudo dnf -y install edb-postgresextended17-server edb-postgresextended17-contrib
+```
+
+## Initial configuration
+
+Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
+
+First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster.
+
+```shell
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge17/bin/edb-pge-17-setup initdb
+
+sudo systemctl start edb-pge-17
+```
+
+To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
+
+```shell
+sudo -iu postgres
+
+psql postgres
+```
+
+The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
+
+Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
+
+```sql
+ALTER ROLE postgres with PASSWORD 'password';
+```
+
+## Experiment
+
+Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
+
+First, use psql to create a database named `hr` to hold human resource information.
+
+```sql
+# running in psql
+CREATE DATABASE hr;
+__OUTPUT__
+CREATE DATABASE
+```
+
+Connect to the `hr` database inside psql:
+
+```
+\c hr
+__OUTPUT__
+You are now connected to database "hr" as user "postgres".
+```
+
+Create columns to hold department numbers, unique department names, and locations:
+
+```
+CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
+PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
+varchar(13));
+__OUTPUT__
+CREATE TABLE
+```
+
+Insert values into the `dept` table:
+
+```
+INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
+__OUTPUT__
+INSERT 0 1
+```
+
+```
+INSERT into dept VALUES (20,'RESEARCH','DALLAS');
+__OUTPUT__
+INSERT 0 1
+```
+
+View the table data by selecting the values from the table:
+
+```
+SELECT * FROM dept;
+__OUTPUT__
+deptno | dname | loc
+--------+------------+----------
+10 | ACCOUNTING | NEW YORK
+20 | RESEARCH | DALLAS
+(2 rows)
+```
diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_9.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_9.mdx
new file mode 100644
index 00000000000..fb16eea337d
--- /dev/null
+++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_9.mdx
@@ -0,0 +1,135 @@
+---
+navTitle: AlmaLinux 9 or Rocky Linux 9
+title: Installing EDB Postgres Extended Server on AlmaLinux 9 or Rocky Linux 9 x86_64
+# 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.
+
+redirects:
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `dnf repolist | grep enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+- Install the EPEL repository:
+
+ ```shell
+ sudo dnf -y install epel-release
+ ```
+
+- Enable additional repositories to resolve dependencies:
+ ```shell
+ sudo dnf config-manager --set-enabled crb
+ ```
+
+## Install the package
+
+```shell
+sudo dnf -y install edb-postgresextended17-server edb-postgresextended17-contrib
+```
+
+## Initial configuration
+
+Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
+
+First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster.
+
+```shell
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge17/bin/edb-pge-17-setup initdb
+
+sudo systemctl start edb-pge-17
+```
+
+To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
+
+```shell
+sudo -iu postgres
+
+psql postgres
+```
+
+The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
+
+Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
+
+```sql
+ALTER ROLE postgres with PASSWORD 'password';
+```
+
+## Experiment
+
+Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
+
+First, use psql to create a database named `hr` to hold human resource information.
+
+```sql
+# running in psql
+CREATE DATABASE hr;
+__OUTPUT__
+CREATE DATABASE
+```
+
+Connect to the `hr` database inside psql:
+
+```
+\c hr
+__OUTPUT__
+You are now connected to database "hr" as user "postgres".
+```
+
+Create columns to hold department numbers, unique department names, and locations:
+
+```
+CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
+PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
+varchar(13));
+__OUTPUT__
+CREATE TABLE
+```
+
+Insert values into the `dept` table:
+
+```
+INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
+__OUTPUT__
+INSERT 0 1
+```
+
+```
+INSERT into dept VALUES (20,'RESEARCH','DALLAS');
+__OUTPUT__
+INSERT 0 1
+```
+
+View the table data by selecting the values from the table:
+
+```
+SELECT * FROM dept;
+__OUTPUT__
+deptno | dname | loc
+--------+------------+----------
+10 | ACCOUNTING | NEW YORK
+20 | RESEARCH | DALLAS
+(2 rows)
+```
diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_8.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_8.mdx
new file mode 100644
index 00000000000..8f82e772f13
--- /dev/null
+++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_8.mdx
@@ -0,0 +1,129 @@
+---
+navTitle: RHEL 8 or OL 8
+title: Installing EDB Postgres Extended Server on RHEL 8 or OL 8 x86_64
+# 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.
+
+redirects:
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `dnf repolist | grep enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+- Install the EPEL repository:
+ ```shell
+ sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
+ ```
+
+## Install the package
+
+```shell
+sudo dnf -y install edb-postgresextended17-server edb-postgresextended17-contrib
+```
+
+## Initial configuration
+
+Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
+
+First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster.
+
+```shell
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge17/bin/edb-pge-17-setup initdb
+
+sudo systemctl start edb-pge-17
+```
+
+To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
+
+```shell
+sudo -iu postgres
+
+psql postgres
+```
+
+The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
+
+Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
+
+```sql
+ALTER ROLE postgres with PASSWORD 'password';
+```
+
+## Experiment
+
+Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
+
+First, use psql to create a database named `hr` to hold human resource information.
+
+```sql
+# running in psql
+CREATE DATABASE hr;
+__OUTPUT__
+CREATE DATABASE
+```
+
+Connect to the `hr` database inside psql:
+
+```
+\c hr
+__OUTPUT__
+You are now connected to database "hr" as user "postgres".
+```
+
+Create columns to hold department numbers, unique department names, and locations:
+
+```
+CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
+PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
+varchar(13));
+__OUTPUT__
+CREATE TABLE
+```
+
+Insert values into the `dept` table:
+
+```
+INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
+__OUTPUT__
+INSERT 0 1
+```
+
+```
+INSERT into dept VALUES (20,'RESEARCH','DALLAS');
+__OUTPUT__
+INSERT 0 1
+```
+
+View the table data by selecting the values from the table:
+
+```
+SELECT * FROM dept;
+__OUTPUT__
+deptno | dname | loc
+--------+------------+----------
+10 | ACCOUNTING | NEW YORK
+20 | RESEARCH | DALLAS
+(2 rows)
+```
diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_9.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_9.mdx
new file mode 100644
index 00000000000..d7ca1bdc9b8
--- /dev/null
+++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_9.mdx
@@ -0,0 +1,129 @@
+---
+navTitle: RHEL 9 or OL 9
+title: Installing EDB Postgres Extended Server on RHEL 9 or OL 9 x86_64
+# 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.
+
+redirects:
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `dnf repolist | grep enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+- Install the EPEL repository:
+ ```shell
+ sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
+ ```
+
+## Install the package
+
+```shell
+sudo dnf -y install edb-postgresextended17-server edb-postgresextended17-contrib
+```
+
+## Initial configuration
+
+Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
+
+First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster.
+
+```shell
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge17/bin/edb-pge-17-setup initdb
+
+sudo systemctl start edb-pge-17
+```
+
+To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
+
+```shell
+sudo -iu postgres
+
+psql postgres
+```
+
+The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
+
+Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
+
+```sql
+ALTER ROLE postgres with PASSWORD 'password';
+```
+
+## Experiment
+
+Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
+
+First, use psql to create a database named `hr` to hold human resource information.
+
+```sql
+# running in psql
+CREATE DATABASE hr;
+__OUTPUT__
+CREATE DATABASE
+```
+
+Connect to the `hr` database inside psql:
+
+```
+\c hr
+__OUTPUT__
+You are now connected to database "hr" as user "postgres".
+```
+
+Create columns to hold department numbers, unique department names, and locations:
+
+```
+CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
+PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
+varchar(13));
+__OUTPUT__
+CREATE TABLE
+```
+
+Insert values into the `dept` table:
+
+```
+INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
+__OUTPUT__
+INSERT 0 1
+```
+
+```
+INSERT into dept VALUES (20,'RESEARCH','DALLAS');
+__OUTPUT__
+INSERT 0 1
+```
+
+View the table data by selecting the values from the table:
+
+```
+SELECT * FROM dept;
+__OUTPUT__
+deptno | dname | loc
+--------+------------+----------
+10 | ACCOUNTING | NEW YORK
+20 | RESEARCH | DALLAS
+(2 rows)
+```
diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx
new file mode 100644
index 00000000000..e396a6b58b7
--- /dev/null
+++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx
@@ -0,0 +1,124 @@
+---
+navTitle: Ubuntu 20.04
+title: Installing EDB Postgres Extended Server on Ubuntu 20.04 x86_64
+# 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.
+
+redirects:
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `apt-cache search enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+## Install the package
+
+```shell
+sudo apt-get -y install edb-postgresextended-17
+```
+
+## Initial configuration
+
+This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password.
+
+First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster.
+
+```shell
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/17/bin/edb-pge-17-setup initdb
+
+sudo systemctl start edb-pge-17
+```
+
+To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
+
+```shell
+sudo -iu postgres
+
+psql postgres
+```
+
+The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
+
+Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
+
+```sql
+ALTER ROLE postgres with PASSWORD 'password';
+```
+
+## Experiment
+
+Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
+
+First, use psql to create a database named `hr` to hold human resource information.
+
+```sql
+# running in psql
+CREATE DATABASE hr;
+__OUTPUT__
+CREATE DATABASE
+```
+
+Connect to the `hr` database inside psql:
+
+```
+\c hr
+__OUTPUT__
+You are now connected to database "hr" as user "postgres".
+```
+
+Create columns to hold department numbers, unique department names, and locations:
+
+```
+CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
+PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
+varchar(13));
+__OUTPUT__
+CREATE TABLE
+```
+
+Insert values into the `dept` table:
+
+```
+INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
+__OUTPUT__
+INSERT 0 1
+```
+
+```
+INSERT into dept VALUES (20,'RESEARCH','DALLAS');
+__OUTPUT__
+INSERT 0 1
+```
+
+View the table data by selecting the values from the table:
+
+```
+SELECT * FROM dept;
+__OUTPUT__
+deptno | dname | loc
+--------+------------+----------
+10 | ACCOUNTING | NEW YORK
+20 | RESEARCH | DALLAS
+(2 rows)
+```
diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_22.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_22.mdx
new file mode 100644
index 00000000000..4f68a0b917a
--- /dev/null
+++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_22.mdx
@@ -0,0 +1,124 @@
+---
+navTitle: Ubuntu 22.04
+title: Installing EDB Postgres Extended Server on Ubuntu 22.04 x86_64
+# 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.
+
+redirects:
+---
+
+## Prerequisites
+
+Before you begin the installation process:
+
+- Set up the EDB repository.
+
+ Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
+
+ To determine if your repository exists, enter this command:
+
+ `apt-cache search enterprisedb`
+
+ If no output is generated, the repository isn't installed.
+
+ To set up the EDB repository:
+
+ 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
+
+ 1. Select the button that provides access to the EDB repository.
+
+ 1. Select the platform and software that you want to download.
+
+ 1. Follow the instructions for setting up the EDB repository.
+
+## Install the package
+
+```shell
+sudo apt-get -y install edb-postgresextended-17
+```
+
+## Initial configuration
+
+This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password.
+
+First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster.
+
+```shell
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/17/bin/edb-pge-17-setup initdb
+
+sudo systemctl start edb-pge-17
+```
+
+To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
+
+```shell
+sudo -iu postgres
+
+psql postgres
+```
+
+The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
+
+Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
+
+```sql
+ALTER ROLE postgres with PASSWORD 'password';
+```
+
+## Experiment
+
+Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
+
+First, use psql to create a database named `hr` to hold human resource information.
+
+```sql
+# running in psql
+CREATE DATABASE hr;
+__OUTPUT__
+CREATE DATABASE
+```
+
+Connect to the `hr` database inside psql:
+
+```
+\c hr
+__OUTPUT__
+You are now connected to database "hr" as user "postgres".
+```
+
+Create columns to hold department numbers, unique department names, and locations:
+
+```
+CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
+PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
+varchar(13));
+__OUTPUT__
+CREATE TABLE
+```
+
+Insert values into the `dept` table:
+
+```
+INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
+__OUTPUT__
+INSERT 0 1
+```
+
+```
+INSERT into dept VALUES (20,'RESEARCH','DALLAS');
+__OUTPUT__
+INSERT 0 1
+```
+
+View the table data by selecting the values from the table:
+
+```
+SELECT * FROM dept;
+__OUTPUT__
+deptno | dname | loc
+--------+------------+----------
+10 | ACCOUNTING | NEW YORK
+20 | RESEARCH | DALLAS
+(2 rows)
+```
diff --git a/product_docs/docs/pge/17/operation.mdx b/product_docs/docs/pge/17/operation.mdx
new file mode 100644
index 00000000000..2fbcc4aef69
--- /dev/null
+++ b/product_docs/docs/pge/17/operation.mdx
@@ -0,0 +1,42 @@
+---
+title: Operations
+originalFilePath: operation.md
+description: Operational features of EDB Postgres Extended Server including WAL pacing delays, additional tracing and diagnostics options.
+---
+
+EDB Postgres Extended Server has a number of features that relate to operations.
+
+## Avoid flooding transaction logs
+
+EDB Postgres Extended Server provides WAL pacing delays to avoid flooding transaction logs. The WAL pacing configuration parameters are:
+ - `wal_insert_delay_enabled`
+ - `wal_insert_delay`
+ - `wal_insert_delay_size`
+
+When `wal_insert_delay_enabled` is enabled, a session sleeps based on the value of `wal_insert_delay` after WAL data of at least the value of `wal_insert_delay_size` is generated. The default is off.
+
+## Additional tracing and diagnostics options
+
+EDB Postgres Extended Server allows you to enable timeouts based on logging trace messages in specific code
+paths. Use the `tracelog_timeout` configuration parameter to allow logging of trace messages after a timeout of
+the specified time occurs.
+
+## Selective physical base backup and subsequent selective recovery/restore
+
+By default, backups are always taken of the entire database cluster. You can also back up individual databases or database objects by specifying
+the `-L` option with the `pg_basebackup` utility multiple times for multiple databases.
+
+Template databases are backed up by default. WAL data for excluded
+databases is still part of the WAL archives.
+
+The backup activity stores the list of database objects specified using this option
+in the backup label file. The presence of these objects in the backup label file causes selective recovery of these databases. Recovery of template
+databases and of global metadata related to users, languages, and so on is also carried
+out as usual. WAL data belonging to excluded databases is ignored during the
+recovery process. Attempts to connect to excluded databases cause errors after regular
+operations start following the recovery.
+
+
+## Additional operations feature
+
+- Reduced locking of `ALTER TABLE ... REPLICA IDENTITY`
diff --git a/product_docs/docs/pge/17/parameters.mdx b/product_docs/docs/pge/17/parameters.mdx
new file mode 100644
index 00000000000..7b4f140bb2d
--- /dev/null
+++ b/product_docs/docs/pge/17/parameters.mdx
@@ -0,0 +1,147 @@
+---
+navTitle: Configuration parameters
+title: Configuration parameters (GUCs)
+originalFilePath: parameters.md
+description: Configuration parameters available with EDB Postgres Extended Server.
+---
+
+These Grand Unified Configuration (GUC) configuration parameters are available with EDB Postgres Extended Server.
+
+## Backend parameters
+
+Backend parameters introduce a test probe point infrastructure for injecting sleeps or errors into PostgreSQL and extensions.
+
+Any `PROBE_POINT` defined throughout the Postgres code code marks important code paths. These probe points might be activated to signal the current backend or to elog(...) a `LOG`/`ERROR`/`FATAL`/`PANIC`. They might also, or instead, add a delay at that point in the code.
+
+Unless explicitly activated, probe points have no effect and add only a single optimizer-hinted branch, so they're safe on hot paths.
+
+When an active probe point is hit and the counter is satisfied, after any specified sleep interval, a log message is always emitted at `DEBUG1` or higher.
+
+### `pg2q.probe_point`
+
+The name of a `PROBE_POINT` in the code of 2ndQPostgres or in an extension that defines a `PROBE_POINT`. This parameter isn't validated. If a nonexistent probe point is named, it's never hit.
+
+Only one probe point can be active. This isn't a list, and attempting to supply a list means nothing matches.
+
+Probe points generally have a unique name, given as the argument to the `PROBE_POINT` macro in the code where it's defined. It's also possible to use the same `PROBE_POINT` name where multiple code paths trigger the same action of interest. A probe fires when either path is taken.
+
+### `pg2q.probe_counter`
+
+You might need to act on a probe only after a loop is run for the number of times specified with this parameter. In such cases, set this GUC to the number of iterations at which point the probe point fires, and reset the counter.
+
+The default value is `1`, meaning the probe points always fire when the name matches.
+
+### `pg2q.probe_sleep`
+
+Sleep for `pg2q.probe_sleep` milliseconds after hitting the probe point. Then fire the action in `pg2q.probe_action`.
+
+### `pg2q.probe_action`
+
+Action to take when the named `pg2q.probe_point` is hit. Available actions are:
+
+- `sleep` — Emit a `DEBUG` message with the probe name.
+- `log` — Emit a `LOG` message with the probe name.
+- `error` — `elog(ERROR, ...)` to raise an `ERROR` condition.
+- `fatal`— `elog(FATAL, ...)`.
+- `panic` — `elog(PANIC, ...)`, which generally then calls `abort()` and delivers a `SIGABRT` (signal 6) to cause the backend to core dump. The probe point tries to set the core file limit to enable core dumps if the hard ulimit permits.
+- `sigint`, `sigterm`, `sigquit`, `sigkill` — Deliver the named signal to the backend that hit the probe point.
+
+### `pg2q.probe_backend_pid`
+
+If nonzero, the probe sleep and action are skipped for backends other than the backend with this ID.
+
+## `server_2q_version_num` and `server_2q_version`
+
+The `server_2q_version_num` and `server_2q_version` configuration parameters allow the 2ndQuadrant-specific version number and version substring, respectively, to be accessible to external modules.
+
+## Table-level compression control option
+
+You can set the table-level option `compress_tuple_target` to decide when to trigger compression on a tuple. Previously, you used the `toast_tuple_target` (or the compile time default) to decide whether to compress a tuple. However, this was detrimental when a tuple is large enough and has a good compression ratio but not large enough to cross the toast threshold.
+
+
+
+## `pg2q.max_tuple_field_size`
+
+Restricts the maximum uncompressed size of the internal representation of any one field that can be written to a table, in bytes.
+
+The default `pg2q.max_tuple_field_size` is 1073740799 bytes, which is 1024 bytes less than 1 GiB. This value is slightly less than the 1 GiB maximum field size usually imposed by PostgreSQL. This margin helps prevent cases where tuples are committed to disk but can't then be processed by logical decoding output plugins and sent to downstream servers.
+
+Set `pg2q.max_tuple_field_size` to `1GB` or `11073741823` to disable the feature.
+
+If your application doesn't rely on inserting large fields, consider setting `pg2q.max_tuple_field_size` to a much smaller value, such as 100MB or even less. Among other issues, large fields can:
+
+- Cause surprising application behavior
+- Increase memory consumption for the database engine during queries and replication
+- Slow down logical replication
+
+While this parameter is enabled, oversized fields cause queries that `INSERT` or `UPDATE` an oversized field to fail with an `ERROR` such as:
+
+```
+ERROR: field big_binary_field_name in row is larger than pg2q.max_tuple_field_size
+DETAIL: New or updated row in relation some_table has field big_binary_field_name
+ (attno=2) with size 8161 bytes which exceeds limit 1073740799B configured
+ in pg2q.max_tuple_field_size
+SQLSTATE: 53400 configuration_limit_exceeded
+```
+
+Only the superuser can set `pg2q.max_tuple_field_size`. You can use a `SECURITY DEFINER` function wrapper if you want to allow a non-superuser to set it.
+
+If you change `pg2q.max_tuple_field_size`, fields larger than the current `pg2q.max_tuple_field_size` that are already on disk don't change. You can `SELECT` them as usual. Any `UPDATE` that affects tuples with oversized fields fails, even if the oversized field isn't modified, unless the new tuple created by the update operation satisfies the currently active size limits.
+
+A `DELETE` operation doesn't check the field-size limit.
+
+The limit isn't enforced on the text-representation size for I/O of fields because doing so also prevents PostgreSQL from creating and processing temporary in-memory json objects larger than the limit.
+
+The limit isn't enforced for temporary tuples in tuplestores, such as set-returning functions, CTEs, and views. Size checks are deliberately not enforced for any `MATERIALIZED VIEW` either.
+
+!!! WARNING
+ `pg2q.max_tuple_field_size` is enforced for `pg_restore`. If a
+ database contains oversized tuples, it does a `pg_dump` as usual. However, a
+ subsequent `pg_restore` fails with the error shown previously. To work around
+ this issue, restore the dump with `pg2q.max_tuple_field_size` overridden in
+ connection options using `PGOPTIONS` or the `options` connection-parameter
+ string. For example:
+
+ ```
+ PGOPTIONS='-c pg2q.max_tuple_field_size=11073741823' pg_restore ...
+ ```
+
+Data type specifics:
+
+- For a `bytea` field, the size used is the decoded binary size. It isn't the text-representation size in hex or octal escape form, that is, the `octet_length()` of the field.
+
+ Assuming `bytea_output = 'hex'`, the maximum size of the I/O representation is `2 * pg2q.max_tuple_field_size + 2` bytes.
+
+- For a `text`, `json`, or `xml` field, the measured size is the number of bytes of text in the current database encoding (the `octet_length()` of the field), not the number of characters. In UTF-8 encodings, one character usually consumes one byte but might consume six or more bytes for some languages and scripts.
+
+- For a `jsonb` field, the measured size is that of the PostgreSQL internal jsonb-encoded datatype representation, the text representation of the json document. In some cases the `jsonb` representation for larger json documents is smaller than the text representation. This means that it's possible to insert json documents with text representations larger than any given `pg2q.max_tuple_field_size`, although it's uncommon.
+
+- Extension-defined data type behavior depends on the implementation of the data type.
+
+ The field size used for this limit is the size reported by them `pg_column_size()` function, minus the 4 bytes of header PostgreSQL adds to variable-length data types, when used on a literal of the target data type. For example:
+
+ ```
+ demo=> SELECT pg_column_size(BYTEA '\x00010203040506070809') - 4;
+ 14
+ ```
+
+ For example, to see the computed size of the jsonb field, use:
+
+ ```
+ SELECT pg_column_size(JSONB '{"my_json_document": "yes"}') - 4;
+ ```
+
+ Due to TOAST compression ,`pg_column_size()` often reports smaller
+ values when called on existing on-disk fields. Also, the header for
+ shorter values on disk might be 1 byte instead of 4.
+
+## `pg2q.max_tuple_size`
+
+Restricts the maximum size of a single tuple that can be written to a table. This value is the total row width, including the uncompressed width of all potentially compressible or external-storage-capable field values. Field headers count against the size, but fixed row headers don't.
+
+Many PostgreSQL operations, such as logical replication, work on whole rows, as do many applications. You can use this setting to impose a limit on the maximum row size you consider reasonable for your application to prevent inadvertent creation of oversized rows that might pose operational issues.
+
+When applied to an `UPDATE` of existing tuples, `pg2q.max_tuple_size` isn't enforced as strictly as `pg2q.max_tuple_field_size`. It doesn't count the full size of unmodified values in columns with storage other than `PLAIN`.
+
+!!! WARNING
+ `pg2q.max_tuple_size` is enforced for `pg_restore`. See the caveat for `pg2q.max_tuple_field_size`.
diff --git a/product_docs/docs/pge/17/release_notes/index.mdx b/product_docs/docs/pge/17/release_notes/index.mdx
new file mode 100644
index 00000000000..1b96b3cd1b5
--- /dev/null
+++ b/product_docs/docs/pge/17/release_notes/index.mdx
@@ -0,0 +1,15 @@
+---
+title: "Release notes"
+description: "Release notes for EDB Postgres Extended Server 17."
+navigation:
+ - rel_notes17.2
+---
+The EDB Postgres Extended Server documentation describes the latest version of EDB Postgres Extended Server 17, including minor releases and patches. These release notes cover what was new in each release.
+
+| Version | Release date |
+|---------------------------|--------------|
+| [17.2](rel_notes17.2) | 22 Nov 2024 |
+
+
+
+
diff --git a/product_docs/docs/pge/17/release_notes/rel_notes17.2.mdx b/product_docs/docs/pge/17/release_notes/rel_notes17.2.mdx
new file mode 100644
index 00000000000..90883c2a010
--- /dev/null
+++ b/product_docs/docs/pge/17/release_notes/rel_notes17.2.mdx
@@ -0,0 +1,12 @@
+---
+title: EDB Postgres Extended Server 17.2 release notes
+navTitle: "Version 17.2"
+---
+
+Released: 22 Nov 2024
+
+EDB Postgres Extended Server 17.2 includes the following enhancements and bug fixes:
+
+| Type | Description | Addresses |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| Upstream merge | Merged with community PostgreSQL 17.2. See the [PostgreSQL 17.2 Release Notes](https://www.postgresql.org/docs/17/release-17-2.html) for more information. | |
diff --git a/product_docs/docs/pge/17/replication.mdx b/product_docs/docs/pge/17/replication.mdx
new file mode 100644
index 00000000000..c7557bc05b4
--- /dev/null
+++ b/product_docs/docs/pge/17/replication.mdx
@@ -0,0 +1,33 @@
+---
+navTitle: Replication
+title: Replication
+originalFilePath: replication.md
+description: EDB Postgres Extended Server provides the core functionality to support replication and high-availability features in EDB Postgres Distributed.
+---
+
+
+EDB Postgres Extended Server provides the core functionality to support the following replication and high availability features in [EDB Postgres Distributed](/pgd/latest):
+
+- Commit At Most Once (CAMO)
+- Group commit
+- Eager replication
+- Decoding worker
+- Assessment tooling
+- Lag tracker
+- Lag control
+- Timestamp snapshots
+- Transaction streaming
+- Missing partition conflict
+- No need for UPDATE trigger on tables with TOAST
+- Automatically hold back FREEZE
+
+## Asynchronous processing
+
+EDB Postgres Extended Server includes a `synchronous_replication_availability` parameter.
+A value of `async` for this parameter enables asynchronous
+processing when not enough standby
+servers are available (when compared with the values as per
+`synchronous_standby_names`). The behavior reverts
+to synchronous replication when the required number of synchronous
+standby servers reappear.
+
diff --git a/product_docs/docs/pge/17/sql_features/index.mdx b/product_docs/docs/pge/17/sql_features/index.mdx
new file mode 100644
index 00000000000..adec227d769
--- /dev/null
+++ b/product_docs/docs/pge/17/sql_features/index.mdx
@@ -0,0 +1,57 @@
+---
+title: SQL enhancements
+originalFilePath: compat.md
+description: EDB Postgres Extended Server includes a number of SQL enhancements including rollback options, cursors with prepared statements, and PL/pgSQL compatibility.
+navigation:
+ - txnrollback
+ - jdbctxnroolback
+---
+EDB Postgres Extended Server includes a number of SQL enhancements.
+
+## Rollback options
+
+In PostgreSQL, any error in a transaction rolls back all actions
+by that transaction. This behavior is different from other DBMS, such
+as Oracle and SQL Server, where an error causes rollback of only the last
+statement. This difference in transaction handling semantics
+doesn't cause a problem in all cases, but it does make implementing business logic
+in PostgreSQL difficult for Oracle Database and Microsoft SQL Server developers.
+
+One workaround is to manually introduce a savepoint, internally known as
+subtransactions, into the application code. This is time consuming and
+difficult to test. A savepoint is an additional statement and therefore increases
+transaction latency. Given the overhead of additional development work
+and slower performance, this approach isn't viable in most cases.
+
+EDB Postgres Extended Server allows you to roll back just the current statement.
+The statement-level rollback feature provides an
+optional mode to choose whether to allow rollback of the whole transaction
+or just the current statement. No manual recoding is required. There's some added overhead, but it's lower than for a savepoint.
+
+See [`transaction_rollback_scope`](txnrollback) for information on setting the transaction rollback scope inside the database and [JDBC properties for rollback scope](jdbctxnrollback) for information on continuing past an error on a JDBC batch job.
+
+
+
+## Cursors with prepared statements
+
+EDB Postgres Extended Server allows declaring a cursor over a previously created prepared statement.
+
+For example:
+
+ ```
+ PREPARE foo AS ...; DECLARE c1 CURSOR FOR foo;
+ ```
+
+## PL/pgSQL compatibility
+
+EDB Postgres Extended Server integrates with other migration tools with a number of PL/pgSQL compatibility features.
+
+For general simplicity, EDB Postgres Extended Server allows calling functions using plpqsl without the PERFORM keyword.
+
+For example,
+
+```
+BEGIN somefunc(); END
+```
+
+Where `somefunc` is not a keyword.
diff --git a/product_docs/docs/pge/17/sql_features/jdbctxnrollback.mdx b/product_docs/docs/pge/17/sql_features/jdbctxnrollback.mdx
new file mode 100644
index 00000000000..f2269a4ec46
--- /dev/null
+++ b/product_docs/docs/pge/17/sql_features/jdbctxnrollback.mdx
@@ -0,0 +1,111 @@
+---
+title: JDBC properties for setting rollback scope
+originalFilePath: jdbctxnrollback.md
+
+---
+
+If you're using a JDBC connector to connect to a client application, you use the `autosave` and `transaction_rollback_scope` properties together to specify the transaction rollback scope.
+
+You can specify these properties in either the connection URL or as an
+additional properties object parameter to `DriverManager.getConnection`.
+
+## autosave
+
+The `autosave` parameter is a string that specifies what the driver does if a query containing
+multiple statements fails. The possible values are: `server`, `always`, `never`, and `conservative`.
+
+- In `autosave=server` mode, JDBC relies on the server-side parameter `transaction_rollback_scope`
+to save each statement by way of internal server savepoints before
+executing the next. The server rolls back to the previous
+statement if any statement in the query fails. If this parameter
+isn't supported on the server side, JDBC rejects the connection.
+
+- In `autosave=always` mode, the JDBC driver first tries to use the server-side `transaction_rollback_scope` property. If it isn't supported,
+then JDBC driver sets a savepoint before each query
+statement and rolls back to that savepoint in case of failure.
+
+- In `autosave=never` mode (default), no savepoint activity is ever
+carried out. In `autosave=conservative` mode, savepoint is set for
+each query. However, the rollback is done only for rare cases like
+'cached statement cannot change return type' or 'statement XXX is
+not valid', so JDBC driver rolls back and retries.
+
+The default value for this property is `never`.
+
+This `autosave=server` property is useful only
+with the PostgreSQL server providing `transaction_rollback_scope`
+functionality.
+
+## transaction_rollback_scope
+
+The `autosave` parameter is a string that determines the range of
+operations that roll back when an SQL statement fails.
+
+The default value is `TRANSACTION`, which causes the entire transaction or
+current subtransaction to roll back. This is the only mode
+that you can select with the `SET TRANSACTION` command.
+
+You can specify the other possible mode, `STATEMENT`, only during connection establishment, `ALTER USER`, or `ALTER DATABASE`. In that mode, only
+the failed `SQL` statement is rolled back, and the transaction is put back in normal mode.
+
+## `autosave` test cases
+Test cases for trying out values of the `autosave` property
+are available in the `BatchAutoSaveTest.java` file. The following
+SQL code shows the behavior that's expected when the
+server provides `transaction_rollback_scope` functionality and
+`autosave=server` is used on the JDBC side.
+
+With `autosave=server`, the following query inserts values `(1)`, `(3)`, and
+`(4)` and disregards the `duplicate key violation` error:
+
+```sql
+CREATE TABLE test (id INT PRIMARY KEY);
+INSERT INTO test VALUES (2);
+BEGIN;
+INSERT INTO test VALUES (1);
+INSERT INTO test VALUES (2);
+INSERT INTO test VALUES (3);
+INSERT INTO test VALUES (4);
+COMMIT;
+```
+
+
+The `artifacts` directory contains the `pgjdbc` jar file
+`postgresql-REL2Q.42.2.3.180601.jar`. This file needs to
+be added to the CLASSPATH as usual. It also contains the
+`postgresql-REL2Q.42.2.3.180601-tests.jar` jar that can be used to test
+the latest `autosave` functionality.
+
+You can test the `BatchAutoSaveTest.java` file provided in the `artifacts` as follows:
+
+1. Export CLASSPATH to build and run the test case:
+
+ ```sh
+ cd artifacts
+ export CLASSPATH=$PWD:$PWD/postgresql-REL2Q.42.2.3.180601-tests.jar:$PWD/postgresql-REL2Q.42.2.3.180601.jar:$PWD/junit-4.12.jar:$PWD/hamcrest-core-1.3.jar
+ ```
+
+1. Compile the supplied test file:
+
+ ```sh
+ javac -d . BatchAutoSaveTest.java
+ ```
+
+1. Run the test (assuming user as `test` and running on localhost):
+
+ ```shell
+ java -Dusername=test -Dport=5432 -Dhost=localhost -Ddatabase=postgres org.junit.runner.JUnitCore org.postgresql.test.jdbc2.BatchAutoSaveTest
+ __OUTPUT__
+ JUnit version 4.12
+ .Configuration file /Users/altaf/pg/artifacts/../build.properties does not exist. Consider adding it to specify test db host and login
+ Configuration file /Users/altaf/pg/artifacts/../build.local.properties does not exist. Consider adding it to specify test db host and login
+ Configuration file /Users/altaf/pg/artifacts/../build.properties does not exist. Consider adding it to specify test db host and login
+ Configuration file /Users/altaf/pg/artifacts/../build.local.properties does not exist. Consider adding it to specify test db host and login
+ .........
+ Time: 0.556
+
+ OK (10 tests)
+ ```
+
+To modify the test cases, you can modify the `BatchAutoSaveTest.java` file
+in the `artifacts` directory. Then compile and run the test cases.
diff --git a/product_docs/docs/pge/17/sql_features/txnrollback.mdx b/product_docs/docs/pge/17/sql_features/txnrollback.mdx
new file mode 100644
index 00000000000..c4c8feb5f79
--- /dev/null
+++ b/product_docs/docs/pge/17/sql_features/txnrollback.mdx
@@ -0,0 +1,55 @@
+---
+title: "transaction_rollback_scope parameter"
+originalFilePath: txnrollback.md
+
+---
+
+To set the transaction rollback scope inside the database, use the `transaction_rollback_scope` parameter.
+The `transaction_rollback_scope` parameter has two possible values:
+
+- `transaction` — Standard Postgres behavior, where each error
+aborts the whole transaction.
+
+- `statement`— An error while executing one statement affects only
+that statement and not the status of the transaction as a whole.
+
+## Setting the parameter
+
+You can set the parameter as a user-level property, a connection option, or the mode for specific functions or procedures.
+
+### Set the parameter as a user-level property
+
+```sql
+ALTER USER somebody SET transaction_rollback_scope TO statement;
+```
+
+### Set the parameter as a connection option
+
+```sh-session
+PGOPTIONS="-c transaction_rollback_scope=statement" psql
+```
+
+### Set the mode for specific functions or procedures
+
+If using PL/pgSQL, you can set the mode for specific functions or procedures:
+
+```sql
+ALTER FUNCTION myfunc SET transaction_rollback_scope TO statement;
+```
+
+## How subtransactions are handled
+
+If you select the `statement` value, then a subtransaction is opened just before each SQL
+command. If the command is successful, the subtransaction is *committed*. If the command causes an error, the subtransaction is
+rolled back, and the parent transaction can continue normally. The
+effect is that an error during execution of one statement affects only
+that statement and not the status of the transaction as a whole.
+
+Committing a subtransaction assigns the
+resources it holds only to its parent transaction, which might be the top-level
+transaction. Or it might be some other subtransaction if there are user-defined
+savepoints involved. So this is not an "autonomous transaction."
+Rolling back a subtransaction releases all the
+resources it holds, such as any locks it acquired.
+
+
diff --git a/product_docs/docs/pge/17/tde.mdx b/product_docs/docs/pge/17/tde.mdx
new file mode 100644
index 00000000000..e5c33231759
--- /dev/null
+++ b/product_docs/docs/pge/17/tde.mdx
@@ -0,0 +1,8 @@
+---
+title: Transparent data encryption
+description: Transparent data encryption (TDE) encrypts any user data stored in the database system.
+---
+
+Transparent data encryption (TDE) encrypts any user data stored in the database system. This encryption is transparent to the user. User data includes the actual data stored in tables and other objects as well as system catalog data such as the names of objects.
+
+See [Transparent data encryption](/tde/latest) for more information.
\ No newline at end of file
diff --git a/product_docs/docs/pge/17/upgrading/index.mdx b/product_docs/docs/pge/17/upgrading/index.mdx
new file mode 100644
index 00000000000..094ca214b6c
--- /dev/null
+++ b/product_docs/docs/pge/17/upgrading/index.mdx
@@ -0,0 +1,11 @@
+---
+navTitle: Upgrading
+title: Upgrading EDB Postgres Extended Server
+description: How to upgrade EDB Postgres Extended Server to a more recent version.
+---
+
+You can upgrade EDB Postgres Extended Server installations to a more recent version.
+
+- See [Upgrading a major version of EDB Postgres Extended Server](major_upgrade) for a major upgrade example.
+
+- See [Upgrading a minor version of EDB Postgres Extended Server](minor_upgrade) for minor upgrade examples according to your package format.
diff --git a/product_docs/docs/pge/17/upgrading/major_upgrade.mdx b/product_docs/docs/pge/17/upgrading/major_upgrade.mdx
new file mode 100644
index 00000000000..c8845a87db4
--- /dev/null
+++ b/product_docs/docs/pge/17/upgrading/major_upgrade.mdx
@@ -0,0 +1,155 @@
+---
+navTitle: "Major upgrades"
+title: "Major version upgrade of EDB Postgres Extended Server"
+description: Perform a major version upgrade of EDB Postgres Extended Server.
+deepToc: true
+---
+
+To perform a major version upgrade, install the new version of EDB Postgres Extended Server, initialize an empty cluster and use pg_upgrade to migrate all data.
+
+If a problem occurs during the upgrade process, you can [revert to the previous version](/epas/latest/upgrading/major_upgrade/06_reverting_to_the_old_cluster/#reverting_to_the_old_cluster).
+
+## Overview
+
+1. [Prepare your upgrade](#preparing-your-upgrade) by performing a backup of the existing instance.
+1. [Install the EDB Postgres Extended Server version](#installing-the-target-edb-postgres-extended-server-version) you're upgrading toward.
+1. [Create a new database server](#creating-a-target-server):
+ 1. Create an empty directory for the new server and ensure postgres owns it.
+ 1. Initialize a server on a different port from the source server.
+ 1. Start the database server.
+ 1. Connect to the database server and ensure it's functioning.
+1. [Upgrade to the target server](#upgrading-to-the-target-server):
+ 1. Stop both the source and the new server.
+ 1. Use pg_upgrade by specifying the source and target bin and data directories.
+ 1. Start the new database server.
+ 1. Connect to the encrypted database server and ensure the data was transferred.
+1. [Clean up and delete the source server](#cleaning-up-after-upgrade):
+ 1. Clean up the database and its statistics.
+ 1. Remove the source EDB Postgres Extended Server cluster with the script provided by pg_upgrade.
+
+## Worked example
+
+This worked example upgrades an EDB Postgres Extended Server 15 database to EDB Postgres Extended Server 16.
+
+!!!note
+ You can perform major upgrades of EDB Postgres Extended Server instances in the same way you upgrade an EDB Postgres Advanced Server installation. If you need more information about the pg_upgrade utility, command line options, troubleshooting, and more, see [Upgrading an installation with pg_upgrade](/epas/latest/upgrading/major_upgrade/).
+
+### Preparing your upgrade
+
+Use [pg_dumpall](https://www.postgresql.org/docs/current/app-pg-dumpall.html), [pgBackRest](/supported-open-source/pgbackrest/), or [Barman](/supported-open-source/barman/) to create a backup of your source server.
+
+### Installing the target EDB Postgres Extended Server version
+
+[Install EDB Postgres Extended Server](../installing/) version 16. Only install the packages. Don't perform any other configurations.
+
+### Creating a target server
+
+If you don't want to create a new target instance but want to reuse an existing server with the target EDB Postgres Extended Server version, skip these steps and [ensure the target server is empty](/epas/latest/upgrading/major_upgrade/03_upgrading_to_advanced_server/#step-2---empty-the-target-database).
+
+1. As postgres, create an empty directory for the new server:
+
+ ```
+ mkdir /var/lib/edb-pge/16/upgrade_target
+ ```
+
+1. As root, ensure the postgres user owns the directory:
+
+ ```
+ sudo chown postgres /var/lib/edb-pge/16/upgrade_target
+ sudo chgrp postgres /var/lib/edb-pge/16/upgrade_target
+ ```
+
+1. As postgres, initialize the new server:
+
+ ```
+ /usr/lib/edb-pge/16/bin/initdb -D /var/lib/edb-pge/16/upgrade_target
+ ```
+
+ This command initializes a CONFIG directory with all configuration files for the encrypted server.
+
+1. Before you start the cluster, ensure the new database runs on a different port from the source server. To alter the port, edit `postgresql.conf` by uncommenting the line with `#port` and changing the port number, for example, to 5432.
+
+1. Start the target server:
+
+ ```
+ /usr/lib/edb-pge/16/bin/pg_ctl -D /var/lib/edb-pge/16/upgrade_target start
+ ```
+
+ !!!note
+ You can also start the server with the `logfile` option enabled to print errors into a logfile:
+ `/usr/lib/edb-pge/16/bin/pg_ctl -D /var/lib/edb-pge/16/upgrade_target -l logfile start`
+
+ In this case, ensure the postgres user has rights to write to the log directory.
+
+1. Connect to the server:
+
+ ```
+ /usr/lib/edb-pge/16/bin/psql -p 5432
+ ```
+
+ !!!note
+ If you're using two different Postgres versions, use the psql utility of the target server. Otherwise, the system will attempt to use psql from the previous instance.
+
+### Upgrading to the target server
+
+1. If you have any extensions or component services running in the source cluster, stop them before starting the upgrade. See [Stop all component services and servers](/epas/latest/upgrading/major_upgrade/03_upgrading_to_advanced_server/#step-4---stop-all-component-services-and-servers) for more information
+
+1. Stop both the source and target servers:
+
+ ```
+ /usr/lib/edb-pge/15/bin/pg_ctl -D /var/lib/edb-pge/15/upgrade-source stop
+ /usr/lib/edb-pge/16/bin/pg_ctl -D /var/lib/edb-pge/16/upgrade-target stop
+ ```
+
+1. To test for incompatibilities, run the `pg_upgrade` command in check mode.
+
+ With `-b` and `-B`, specify the source and target BIN directories. With `-d` and `-D`, specify the source and target CONFIG directories:
+
+ ```
+ /usr/lib/edb-pge/16/bin/pg_upgrade -b /usr/lib/edb-pge/15/bin -B /usr/lib/edb-pge/16/bin -d /var/lib/edb-pge/15/upgrade-source -D /var/lib/edb-pge/16/upgrade-target --check
+ ```
+
+ !!!note
+ The `--check` mode performs preliminary checks without executing the command.
+
+1. To copy data from the source server to the target server, run the `pg_upgrade` command in normal mode:
+
+ ```
+ /usr/lib/edb-pge/16/bin/pg_upgrade -b /usr/lib/edb-pge/15/bin -B /usr/lib/edb-pge/16/bin -d /var/lib/edb-pge/15/upgrade-source -D /var/lib/edb-pge/16/upgrade-target
+ ```
+
+1. Start the target server:
+
+ ```
+ /usr/lib/edb-pge/16/bin/pg_ctl -D /var/lib/edb-pge/16/upgrade-target start
+ ```
+
+1. Connect to the target database server:
+
+ ```
+ /usr/lib/edb-as/16/bin/psql -p 5432
+ ```
+
+1. Perform a spot check to ensure the databases, tables, schemas, and resources you had in the unencrypted server are available in the new server. For example, list all databases, explore the database objects, views, and so on.
+
+1. Restart the extensions or component services you disabled in the source cluster but in the target cluster.
+
+### Cleaning up after upgrade
+
+After you verify that pg_upgrade migrated the data successfully, and the services are running as expected, perform a cleanup.
+
+1. Clean up the database and its statistics:
+
+ ```
+ /usr/lib/edb-pge/16/bin/vacuumdb --all --analyze-in-stages
+ ```
+
+1. Remove all data files of the unencrypted server with the script generated by `pg_upgrade`:
+
+ ```
+ ./delete_old_cluster.sh
+ ```
+
+## More information
+
+Review [Upgrading an installation with pg_upgrade](/epas/latest/upgrading/major_upgrade/) for more information on pg_upgrade options, troubleshooting, and other considerations.
diff --git a/product_docs/docs/pge/17/upgrading/minor_upgrade/apt_upgrade.mdx b/product_docs/docs/pge/17/upgrading/minor_upgrade/apt_upgrade.mdx
new file mode 100644
index 00000000000..18cc18753e7
--- /dev/null
+++ b/product_docs/docs/pge/17/upgrading/minor_upgrade/apt_upgrade.mdx
@@ -0,0 +1,65 @@
+---
+title: "Minor EDB Postgres Extended Server upgrade of Debian packages"
+navTitle: "Minor upgrades on Debian environments"
+description: "Perform a minor version upgrade of EDB Postgres Extended Server with the apt-get package manager"
+---
+
+If you used `apt-get` to install a Debian package of EDB Postgres Extended Server (on Ubuntu, Debian), use `apt-get` to perform a minor version upgrade of the packages.
+
+## Overview
+
+1. Upgrade the EDB Postgres Extended Server packages with `apt-get install`.
+
+1. Restart the server with `pg_ctl`.
+
+1. Verify the server version with psql.
+
+## Worked example
+
+1. To upgrade the existing packages, open a command line, assume root privileges, and enter the command:
+
+ ```shell
+ sudo apt-get install
+ ```
+
+ For example, if you want to upgrade to the latest minor version of EDB Postgres Extended Server 16, run:
+
+ ```shell
+ sudo apt-get install edb-postgresextended-16
+ ```
+
+ !!!Note
+ You can perform a search of the packages to ensure you update the right package beforehand. For example, to browse through all EDB Packages, you can run `sudo apt-cache edb`. For more information about using `apt-get` commands and options, enter `apt-get --help` at the command line.
+
+1. Confirm with `Y`.
+
+ The output displays an overview of all performed processes, where you can see the packages that were upgraded.
+
+1. To finalize the upgrade, restart the server. Replace `` with the path to the data directory of the server or servers you're upgrading:
+
+ ```shell
+ /usr/lib/edb-pge/16/bin/pg_ctl -D restart
+ ```
+
+ For example:
+
+ ```shell
+ /usr/lib/edb-pge/16/bin/pg_ctl -D /var/lib/edb-pge/16/upgrade restart
+ ```
+
+1. Verify the expected database version is running by connecting to psql:
+
+ ```shell
+ /usr/lib/edb-pge/16/bin/psql
+ ```
+
+ Check the server version:
+
+ ```psql
+ SHOW server_version;
+ __OUTPUT__
+ server_version
+ --------------------------------------------------------------------
+ 16.3 (EDB Postgres Extended Server 16.3.0) (Ubuntu 0:16.3-1.jammy)
+ (1 row)
+ ```
diff --git a/product_docs/docs/pge/17/upgrading/minor_upgrade/dnf_upgrade.mdx b/product_docs/docs/pge/17/upgrading/minor_upgrade/dnf_upgrade.mdx
new file mode 100644
index 00000000000..c5b91cb3063
--- /dev/null
+++ b/product_docs/docs/pge/17/upgrading/minor_upgrade/dnf_upgrade.mdx
@@ -0,0 +1,96 @@
+---
+title: "Minor EDB Postgres Extended Server upgrade of RPM packages"
+navTitle: "Minor upgrades on RPM environments"
+description: "Perform a minor version upgrade of EDB Postgres Extended Server with the dnf package manager"
+---
+
+If you used `dnf` to install an RPM package of EDB Postgres Extended Server (on RHEL, AlmaLinux, Rocky Linux), use `dnf` to perform a minor version upgrade of the packages.
+
+## Overview
+
+1. Check for available updates with `dnf check-update`.
+
+1. Upgrade the EDB Postgres Extended Server packages with `dnf update`.
+
+1. Restart the server with `pg_ctl`.
+
+1. Verify the server version with psql.
+
+## Worked example
+
+1. To list the package updates available for your system, open a command line, assume root privileges, and enter the command:
+
+ ```shell
+ sudo dnf check-update
+ ```
+
+ For example, if you want to upgrade to the latest minor version of EDB Postgres Extended Server 16, run:
+
+ ```shell
+ sudo dnf check-update edb-postgresextended16
+ ```
+
+ !!!Note
+ You can include wildcard values in the search term. For example, if you're looking for EDB Packages, you can run `sudo dnf check-update edb-*`. For more information about using `dnf` commands and options, enter `dnf --help` at the command line.
+
+1. Once you've figured the name and version of the package you want to install, use `dnf update` to install the package:
+
+ ```shell
+ sudo dnf update edb-postgresextended16
+ __OUTPUT__
+ ================================================================================
+ Package Arch Version Repository Size
+ ================================================================================
+ Upgrading:
+ edb-postgresextended16 x86_64 16.3-2.el9 enterprisedb-enterprise 1.7 M
+ edb-postgresextended16-contrib x86_64 16.3-2.el9 enterprisedb-enterprise 724 k
+ edb-postgresextended16-libs x86_64 16.3-2.el9 enterprisedb-enterprise 330 k
+ edb-postgresextended16-server x86_64 16.3-2.el9 enterprisedb-enterprise 6.8 M
+
+ Transaction Summary
+ ================================================================================
+ Upgrade 4 Packages
+
+ Total download size: 9.5 M
+ Is this ok [y/N]
+ ```
+
+1. Confirm with `y`. The output displays an overview of all performed processes, where you can see the packages that were upgraded:
+
+ ```shell
+ y
+ __OUTPUT__
+ edb-postgresextended16-16.3-2.el9.x86_64
+ edb-postgresextended16-contrib-16.3-2.el9.x86_64
+ edb-postgresextended16-libs-16.3-2.el9.x86_64
+ edb-postgresextended16-server-16.3-2.el9.x86_64
+ ```
+
+1. To finalize the upgrade, restart the server. Replace `` with the path to the data directory of the server or servers you're upgrading:
+
+ ```shell
+ /usr/edb/pge16/bin/pg_ctl -D restart
+ ```
+
+ For example:
+
+ ```shell
+ /usr/edb/pge16/bin/pg_ctl -D /var/lib/edb-pge/16/upgrade restart
+ ```
+
+1. Verify the expected database version is running by connecting to psql:
+
+ ```shell
+ /usr/edb/pge16/bin/psql
+ ```
+
+ Check the server version:
+
+ ```psql
+ SHOW server_version;
+ __OUTPUT__
+ server_version
+ --------------------------------------------
+ 16.3 (EDB Postgres Extended Server 16.3.0)
+ ```
+
\ No newline at end of file
diff --git a/product_docs/docs/pge/17/upgrading/minor_upgrade/index.mdx b/product_docs/docs/pge/17/upgrading/minor_upgrade/index.mdx
new file mode 100644
index 00000000000..613945baedc
--- /dev/null
+++ b/product_docs/docs/pge/17/upgrading/minor_upgrade/index.mdx
@@ -0,0 +1,15 @@
+---
+title: "Minor EDB Postgres Extended Server upgrade"
+navTitle: "Minor upgrades"
+description: "Minor version upgrade of EDB Postgres Extended Server"
+---
+
+To perform a minor upgrade of your EDB Postgres Extended Server you only need to update your packages and restart the server.
+
+To update your packages, ensure you use the correct package manager for your operating system.
+
+- If you installed an RPM package of EDB Postgres Extended Server (on RHEL, AlmaLinux, Rocky Linux) with `dnf`, see [Minor EDB Postgres Extended Server upgrade of RPM packages](dnf_upgrade).
+
+- If you installed a Debian package of EDB Postgres Extended Server (on Ubuntu, Debian) with `apt-get`, see [Minor EDB Postgres Extended Server upgrade of Debian packages ](apt_upgrade).
+
+When you upgrade the packages, the packager manager installs the latest available minor version. For example, if you're running an xy.1 minor version, and the latest available minor version is xy.5, the package manager will install xy.5, skipping xy.2 to xy.4.
diff --git a/static/_redirects b/static/_redirects
index 0e22ae6ded5..540a03bffff 100644
--- a/static/_redirects
+++ b/static/_redirects
@@ -121,6 +121,7 @@
/docs/jdbc_connector/42.5.1.1/* /docs/jdbc_connector/latest/:splat 301
/docs/jdbc_connector/42.5.1.2/* /docs/jdbc_connector/latest/:splat 301
/docs/jdbc_connector/42.5.4.1/* /docs/jdbc_connector/latest/:splat 301
+/docs/jdbc_connector/42.7.3.1/* /docs/jdbc_connector/latest/:splat 301
# ODBC Connector
# collapsed versions