Merge pull request #5899 from EnterpriseDB/release-2024-08-01a

Release 2024-08-01a

.github/workflows/check-links.yml

@@ -11,12 +11,27 @@ jobs:
         with:
           lfs: true
           ref: ${{ github.event.pull_request.head.sha }}
+          path: content
+          sparse-checkout: |
+            advocacy_docs
+            product_docs
+
+      - name: Checkout sync tool
+        uses: actions/checkout@v4
+        with:
+          lfs: true
+          ref: develop
+          path: tools
+          sparse-checkout: |
+            tools
       
       - name: setup node
         uses: actions/setup-node@v4
 
       - name: install dependencies
-        run: npm --prefix ./tools/automation/actions/link-check ci
+        run: npm --prefix ./tools/tools/automation/actions/link-check ci
 
       - name: check links
-        uses: ./tools/automation/actions/link-check
+        uses: ./tools/tools/automation/actions/link-check
+        with:
+          content-path: ./content

advocacy_docs/security/advisories/cve20244545.mdx

@@ -8,7 +8,7 @@ First Published: 2024/05/09
 
 Last Updated: 2024/05/09
 
-## Summary 
+## Summary
 
 All versions of EnterpriseDB Postgres Advanced Server (EPAS) from 15.0 and prior to 15.7.0 and from 16.0 and prior to 16.3.0 may allow users using `edbldr` to bypass role permissions from `pg_read_server_files`. This could allow low privilege users to read files to which they would not otherwise have access.
 
@@ -27,8 +27,8 @@ CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
 ## Affected products and versions
 
 * EnterpriseDB Postgres Advanced Server (EPAS)
-  * All versions from 15.0 and prior to 15.7.0 
-  * All versions from 16.0 and prior to 16.3.0
+    * All versions from 15.0 and prior to 15.7.0 
+    * All versions from 16.0 and prior to 16.3.0
 
 ## Remediation
 
@@ -37,7 +37,7 @@ Impacted users must upgrade to a fixed version of EPAS. For questions about upda
 | Product | VRMF | Remediation/First Fix |
 |---------|------|-----------------------|
 | EPAS | All versions from 15.0 and prior to 15.7.0 | [Upgrade EPAS 15 to Minor release](https://www.enterprisedb.com/docs/epas/15/upgrading/04_upgrading_an_installation_with_pg_upgrade/01_performing_an_upgrade/) |
-| EPAS | All versions from 16.0 and prior to 16.7.0 | [Upgrade EPAS 16 to Minor release](https://www.enterprisedb.com/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/01_performing_an_upgrade/) |
+| EPAS | All versions from 16.0 and prior to 16.7.0 | [Upgrade EPAS 16 to Minor release](https://www.enterprisedb.com/docs/epas/16/upgrading/minor_upgrade/) |
 
 !!! Warning
 If impacted users are currently relying on non-superusers to run edbldr and read data from the server filesystem without any special permissions, the fixed versions of EPAS could break these workflows. It is recommended that users do one of the following:
@@ -68,4 +68,4 @@ None
 
 ## Disclaimer
 
-This document is provided on an "as is" basis and does not imply any kind of guarantee or warranty, including the warranties of merchantability or fitness for a particular use. Your use of the information on the document is at your own risk. EDB reserves the right to change or update this document at any time. Customers are therefore recommended to always view the latest version of this document.
+This document is provided on an "as is" basis and does not imply any kind of guarantee or warranty, including the warranties of merchantability or fitness for a particular use. Your use of the information on the document is at your own risk. EDB reserves the right to change or update this document at any time. Customers are therefore recommended to always view the latest version of this document.

product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx

@@ -258,7 +258,7 @@ biganimal cluster delete \
   --region "eastus"
 ```
 
-You can list all deleted clusters using the `show-deleted-clusters` command and restore them from their history backups as needed.
+You can list all deleted clusters using the `biganimal cluster show --deleted` command and restore them from their history backups as needed.
 
 
 ### Restore a cluster

product_docs/docs/biganimal/release/release_notes/2024_07_jul_rel_notes.mdx

@@ -0,0 +1,9 @@
+---
+title: BigAnimal July 2024 release notes
+navTitle: July 2024
+---
+
+No updates were released for BigAnimal in July 2024.
+
+
+

product_docs/docs/biganimal/release/release_notes/index.mdx

@@ -2,6 +2,7 @@
 title: BigAnimal release notes
 navTitle: Release notes
 navigation:
+- 2024_07_jul_rel_notes
 - 2024_06_jun_rel_notes
 - 2024_05_may_rel_notes
 - 2024_04_apr_rel_notes
@@ -24,14 +25,15 @@ navigation:
 
 The BigAnimal documentation describes the latest version of BigAnimal, including minor releases and patches. These release notes provide information on what was new in each release. For new functionality introduced in a minor or patch release, the content also indicates the release that introduced the feature.
 
-| 2024                                |
-|--------------------------------------|
+| 2024                                   |
+|----------------------------------------|
+| [July 2024](2024_07_jul_rel_notes)    |
 | [June 2024](2024_06_jun_rel_notes)     |
-| [May 2024](2024_05_may_rel_notes)     |
-| [April 2024](2024_04_apr_rel_notes)     |
-| [March 2024](2024_03_mar_rel_notes)     |
-| [February 2024](2024_02_feb_rel_notes)  |
-| [January 2024](2024_01_jan_rel_notes)   |
+| [May 2024](2024_05_may_rel_notes)      |
+| [April 2024](2024_04_apr_rel_notes)    |
+| [March 2024](2024_03_mar_rel_notes)    |
+| [February 2024](2024_02_feb_rel_notes) |
+| [January 2024](2024_01_jan_rel_notes)  |
 
 | 2023                                |
 |--------------------------------------|

product_docs/docs/epas/16/upgrading/index.mdx

@@ -6,8 +6,8 @@ redirects:
 - /epas/latest/epas_upgrade_guide/
 ---
 
-Upgrading EDB Postgres Advanced Server involves:
+Upgrading an EDB Postgres Advanced Server installation varies depending on whether you want to perform a major or minor version upgrade. 
+
+-   Use `pg_upgrade` to perform upgrades between major versions of EDB Postgres Advanced Server. 
+-   Use `dnf`, `apt-get` or StackBuilder Plus to perform upgrades between minor versions of EDB Postgres Advanced Server. The method you use depends on the underlying operating system. 
 
--   `pg_upgrade` to upgrade from an earlier version of EDB Postgres Advanced Server to the latest version.
--   `yum` to perform a minor version upgrade on a Linux host.
--   `StackBuilder Plus` to perform a minor version upgrade on a Windows host.

product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/01_performing_an_upgrade/index.mdx → product_docs/docs/epas/16/upgrading/major_upgrade/01_performing_an_upgrade/index.mdx

@@ -1,8 +1,9 @@
 ---
 title: "Performing an upgrade"
-description: "Describes how to upgrade an earlier version of EDB Postgres Advanced Server to the current version"
+description: "Describes how to upgrade an earlier version of EDB Postgres Advanced Server to the current version."
 redirects:
 - /epas/latest/epas_upgrade_guide/04_upgrading_an_installation_with_pg_upgrade/01_performing_an_upgrade/
+- /epas/latest/upgrading/04_upgrading_an_installation_with_pg_upgrade/01_performing_an_upgrade
 ---
 
 To upgrade an earlier version of EDB Postgres Advanced Server to the current version:

product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/index.mdx → product_docs/docs/epas/16/upgrading/major_upgrade/index.mdx

@@ -1,8 +1,9 @@
 ---
-title: "Upgrading an installation with pg_upgrade"
-description: "Describes using pg_upgrade to migrate from an earlier version of EDB Postgres Advanced Server to the newest version"
+title: "Major version upgrade with pg_upgrade"
+description: "Describes using pg_upgrade to migrate from an earlier major version of EDB Postgres Advanced Server to the most recent version."
 indexCards: simple
 navigation:
+- 03_limitations
 - how_pg_upgrade_works
 - 01_performing_an_upgrade
 - 02_invoking_pg_upgrade
@@ -12,12 +13,13 @@ navigation:
 - 06_reverting_to_the_old_cluster
 redirects:
 - /epas/latest/epas_upgrade_guide/04_upgrading_an_installation_with_pg_upgrade/
+- /epas/latest/upgrading/04_upgrading_an_installation_with_pg_upgrade
 ---
 
 <div id="upgrading_an_installation_with_pg_upgrade" class="registered_link"></div>
 
 !!! Note
-    Review the [upgrade considerations](../03_limitations/) prior to performing an upgrade with the `pg_upgrade` utility.
+    Review the [upgrade considerations](03_limitations) prior to performing an upgrade with the `pg_upgrade` utility.
 
 While minor upgrades between versions are fairly simple and require only installing new executables, past major version upgrades were both expensive and time consuming. `pg_upgrade` eases migration between any version of EDB Postgres Advanced Server (version 9.0 or later) and any later release of EDB Postgres Advanced Server that's supported on the same platform.
 

product_docs/docs/epas/16/upgrading/05_performing_a_minor_version_update_of_an_rpm_installation.mdx → product_docs/docs/epas/16/upgrading/minor_upgrade/05_performing_a_minor_version_update_of_an_rpm_installation.mdx

@@ -1,14 +1,14 @@
 ---
-title: "Performing a minor version update of an RPM installation"
-description: "For RPM package installs, how to perform a minor version upgrade to a more recent version"
+title: "Performing a minor version upgrade on an RPM installation"
+description: "For RPM package installs, how to perform a minor version upgrade to a more recent version."
 redirects:
 - /epas/latest/epas_upgrade_guide/05_performing_a_minor_version_update_of_an_rpm_installation/
 ---
 
 If you are upgrading a Red Hat Enterprise Linux-based system (or a compatible system such as Rocky Linux, Alma Linux, Oracle Linux), then you used an RPM package to install EDB Postgres Advanced Server. To perform a minor upgrade on these systems, use the `dnf` package manager.
 
 !!! Note
-    This procedure only performs an update between minor EPAS releases. To upgrade to a later major release, use the [`pg_upgrade` procedure](04_upgrading_an_installation_with_pg_upgrade).
+    This procedure only performs an upgrade between minor EPAS releases. To upgrade to a later major release, use the [`pg_upgrade` procedure](../major_upgrade/).
 
 1.  To list the package updates that are available for your system, open a command line, assume root privileges, and run:
 
@@ -34,6 +34,8 @@ If you are upgrading a Red Hat Enterprise Linux-based system (or a compatible sy
     dnf update edb*
     ```
 
+1.  Restart your server to complete the upgrade. 
+
 For more information about using `dnf` commands and options, enter `dnf --help` at the command line.
 
 !!! Important

product_docs/docs/epas/16/upgrading/06_using_stackbuilder_plus_to_perform_a_minor_version_update.mdx → product_docs/docs/epas/16/upgrading/minor_upgrade/06_using_stackbuilder_plus_to_perform_a_minor_version_update.mdx

@@ -1,6 +1,6 @@
 ---
-title: "Using StackBuilder Plus to perform a minor version update"
-description: "How to use the StackBuilder Plus utility to install supporting modules "
+title: "Using StackBuilder Plus to perform a minor version upgrade"
+description: "How to use the StackBuilder Plus utility to install supporting modules."
 redirects:
 - /epas/latest/epas_upgrade_guide/06_using_stackbuilder_plus_to_perform_a_minor_version_update/
 ---

product_docs/docs/epas/16/upgrading/minor_upgrade/index.mdx

@@ -0,0 +1,18 @@
+---
+title: "Minor version upgrade with package manager"
+description: "Describes using a package manager to perfom a minor version upgrade of EDB Postgres Advanced Server."
+navigation:
+- 05_performing_a_minor_version_update_of_an_rpm_installation
+- performing_a_minor_version_update_of_Deb_installation
+- 06_using_stackbuilder_plus_to_perform_a_minor_version_update
+---
+
+Minor version upgrades are fairly simple and only require updating existing executables and restarting the database server. 
+
+Select the minor upgrade method according to the underlying operating system of your database server:
+
+- If you installed an RPM package of EDB Postgres Advanced Server (on RHEL, AlmaLinux, Rocky Linux) with `dnf`, see [Performing a minor version upgrade of an RPM installation](05_performing_a_minor_version_update_of_an_rpm_installation).
+
+- If you installed a Debian package of EDB Postgres Advanced Server (on Ubuntu, Debian) with `apt-get`, see [Performing a minor version upgrade of a Debian installation](performing_a_minor_version_update_of_Deb_installation).
+
+- If you installed EDB Postgres Advanced Server with StackBuilder Plus, see [Using StackBuilder Plus to perform a minor version upgrade](06_using_stackbuilder_plus_to_perform_a_minor_version_update).

product_docs/docs/epas/16/upgrading/minor_upgrade/performing_a_minor_version_update_of_Deb_installation.mdx

@@ -0,0 +1,70 @@
+---
+title: "Performing a minor version upgrade on a Debian installation"
+description: "For Debian package installs, how to perform a minor version upgrade to a more recent version."
+---
+
+If you are upgrading a Debian-based system (or a compatible system such as Ubuntu), then you used a Debian package to install EDB Postgres Advanced Server. To perform a minor upgrade on these systems, use the `apt-get` package manager.
+
+!!! Note
+    This procedure only performs an upgrade between minor EPAS releases. To upgrade to a later major release, use the [`pg_upgrade` procedure](../major_upgrade/).
+
+1.  To list the package updates that are available for your system, open a command line, assume root privileges, and run:
+
+    ```shell
+    apt-get install --simulate <package_name>
+    ```
+
+    Where `package_name` is the search term for which you want to list available updates. You can include wildcard values in the search to list multiple related packages with a single command. For example, use the following command to list all packages with names that start with `edb`:
+
+    ```shell
+    apt-get install --simulate edb*
+    ```
+
+1.  After you identify the package(s), update them:
+
+    ```shell
+    apt-get install <package_name>
+    ```
+
+    Where `package_name` is the name of the package you want to update. You can include wildcard values to update multiple related packages with a single command. For example, use the following command to update all packages with names that start with `edb`:
+
+    ```shell
+    apt-get update edb*
+    ```
+
+1.  The output asks for confirmation to install the packages: 
+
+    ```console
+    After this operation, <number> kB of additional disk space will be used.
+    Do you want to continue? [Y/n] Y
+    ```
+
+1.  Confirm by entring the letter `Y` and pressing **Enter**. 
+
+1.  Restart your server to complete the upgrade. 
+
+For more information about using `apt-get` commands and options, enter `apt-get --help` at the command line.
+
+!!! Important
+
+If upgrading to version 15.4  or later, run `edb_sqlpatch`.
+
+The command might respond that it has a number of patches needing to be applied, for example:
+
+```console
+* database edb
+0 patches were previously applied to this database.
+58 patches need to be applied to this database.
+```
+
+In this case, you need to run edb_sqlpatch to patch the system catalog:
+
+```shell
+edb_sqlpatch -af
+```
+
+For more information about using edb_sqlpatch commands and options, see [edb_sqlpatch](/tools/edb_sqlpatch/).
+
+!!!
+
+

product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.3.2.mdx

@@ -10,7 +10,7 @@ Enhancements, bug fixes, and other changes in Hadoop Foreign Data Wrapper 2.3.2
 | Type        | Description                                                                                |
 |-------------|--------------------------------------------------------------------------------------------|
 | Enhancement | Added support for PostgreSQL 17 and upcoming EDB Postgres Advanced Server 17.              |
-| Feature     | Added `enable_limit_pushdown` GUC to control LIMIT/OFFSET push-down, at the session level. |
+| Feature     | Added `enable_limit_pushdown` GUC to control LIMIT/OFFSET pushdown at the session level. |
 | Deprecation | Removed support for EDB Postgres Advanced Server 11 and PostgreSQL 11.                     |
 
 

product_docs/docs/mysql_data_adapter/2/06_features_of_mysql_fdw.mdx

@@ -105,11 +105,11 @@ OPERATOR pg_catalog.=(numeric,numeric)
 
 ## Using a connection file
 
-MySQL Foreign Data Wrapper 2.9.2 and later provides the `MYSQL_DEFAULT_FILE` option to read the connection details from the default file. You can provide the filename using this option with connection details like username, password, etc. Set the `MYSQL_DEFAULT_FILE` option at a server level to the default connection file name. If this option is set to a wrong filename or the file contents are not in the required format, then an error is raised.
+MySQL Foreign Data Wrapper 2.9.2 and later provides the `MYSQL_DEFAULT_FILE` option to read the connection details from the default file. You can provide the filename using this option with connection details like username, password, and so on. Set the `MYSQL_DEFAULT_FILE` option at a server level to the default connection filename. If this option is set to a wrong filename or the file contents aren't in the required format, then an error is raised.
 
-If `MYSQL_DEFAULT_FILE` and the other connection details both are provided in the CREATE SERVER/USER MAPPING command, then `MYSQL_DEFAULT_FILE` option takes the precedence.
+If both `MYSQL_DEFAULT_FILE` and the other connection details are provided in the `CREATE SERVER/USER MAPPING` command, then the `MYSQL_DEFAULT_FILE` option takes precedence.
 
-For more information, see [Example: Using a connection file ](example_connection_file)
+For more information, see [Example: Using a connection file ](example_connection_file).
 
 ## IS [NOT] DISTINCT FROM operator
 

product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.9.2_rel_notes.mdx

@@ -14,6 +14,6 @@ Enhancements, bug fixes, and other changes in MySQL Foreign Data Wrapper 2.9.2 i
 | Enhancement  | Mapped TIMESTAMP to TIMESTAMPTZ in IMPORT SCHEMA processing.                                      |
 | Bug fix | Fixed an issue for server crash in left join with the whole row reference.                        |
 | Bug fix | Fixed an issue for MySQL connection by setting timezone to UTC.                                   |
-| Bug fix | Fixed an issue related to push-down of `ScalarArrayOpExpr` (ANY and ALL).                         |
+| Bug fix | Fixed an issue related to pushdown of `ScalarArrayOpExpr` (ANY and ALL).                          |
 | Bug fix | Fixed an issue while de-parsing the multi-dimensional array in `ScalarArrayOpExpr` (ANY and ALL). |
 | Deprecation  | Removed support for EDB Postgres Advanced Server 11 and PostgreSQL 11.                            |

product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/09_11610_rel_notes.mdx

@@ -1,6 +1,6 @@
 ---
-title: "EDB PgBouncer 1.16.0.0 release notes"
-navTitle: Version 1.16.0.0
+title: "EDB PgBouncer 1.16.1.0 release notes"
+navTitle: Version 1.16.1.0
 ---
 
 Released: 11 Dec 2021

product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/12300_rel_notes.mdx

@@ -0,0 +1,12 @@
+---
+title: "EDB PgBouncer 1.23.0.0 release notes"
+navTitle: Version 1.23.0.0
+---
+
+Released: 1 Aug 2024
+
+EDB PgBouncer 1.23.0.0 includes the following upstream merge and security fix:
+
+|      Type      |                                                                    Description                                                                    |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Upstream merge | Merged with community PgBouncer 1.23.0.0. See the community [Release Notes](https://www.pgbouncer.org/changelog.html#pgbouncer-123x) for details. |

product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/index.mdx

@@ -2,12 +2,24 @@
 title: "Release notes"
 redirects:
   - ../01_whats_new/
+navigation:
+  - 12300_rel_notes
+  - 02_12210_rel_notes
+  - 03_12200_rel_notes
+  - 04_12100_rel_notes
+  - 05_12000_rel_notes
+  - 06_11900_rel_notes
+  - 07_11800_rel_notes
+  - 08_11700_rel_notes
+  - 09_11610_rel_notes
+  - 10_11601_rel_notes
 ---
 
 The EDB PgBouncer documentation describes the latest version of EDB PgBouncer 1, including minor releases and patches. The release notes provide information on what was new in each release. For new functionality introduced in a minor or patch release, the content also indicates the release that introduced the feature.
 
 |            Version             | Release date |                               Upstream merges                                |
 | ------------------------------ | ------------ | ---------------------------------------------------------------------------- |
+| [1.23.0.0](12300_rel_notes)    | 01 Aug 2024  | Upstream [1.23.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-123x) |
 | [1.22.1.0](02_12210_rel_notes) | 16 Apr 2024  | Upstream [1.22.1.0](https://www.pgbouncer.org/changelog.html#pgbouncer-122x) |
 | [1.22.0.0](03_12200_rel_notes) | 29 Feb 2024  | Upstream [1.22.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-122x) |
 | [1.21.0.0](04_12100_rel_notes) | 16 Oct 2023  | Upstream [1.21.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-121x) |