diff --git a/.github/workflows/check-links.yml b/.github/workflows/check-links.yml
index c099a184ae5..7f650d27090 100644
--- a/.github/workflows/check-links.yml
+++ b/.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
diff --git a/advocacy_docs/edb-postgres-ai/analytics/images/level-100-architecture.png b/advocacy_docs/edb-postgres-ai/analytics/images/level-100-architecture.png
deleted file mode 100644
index f38ceb9aa30..00000000000
--- a/advocacy_docs/edb-postgres-ai/analytics/images/level-100-architecture.png
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4aef8790c4aa13f37492cf6acb1c1376a7db86bde75d5fa403446280594b70c2
-size 309502
diff --git a/advocacy_docs/edb-postgres-ai/analytics/images/level-200-marketecture.png b/advocacy_docs/edb-postgres-ai/analytics/images/level-200-marketecture.png
deleted file mode 100644
index 65d48afbe42..00000000000
--- a/advocacy_docs/edb-postgres-ai/analytics/images/level-200-marketecture.png
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:39a0b65fac78b1314645cb31cc0b1ab7357e55f9338e97b76e5cf6a20a9f94dd
-size 453185
diff --git a/advocacy_docs/edb-postgres-ai/analytics/images/level-300-architecture.png b/advocacy_docs/edb-postgres-ai/analytics/images/level-300-architecture.png
deleted file mode 100644
index ea69945d1ff..00000000000
--- a/advocacy_docs/edb-postgres-ai/analytics/images/level-300-architecture.png
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:92662f8a9ba963b7d5a590583f4751e65738e8ac69ca70067b1d47e0b09f6dd2
-size 458380
diff --git a/advocacy_docs/edb-postgres-ai/analytics/images/level-300.svg b/advocacy_docs/edb-postgres-ai/analytics/images/level-300.svg
index 6b59fc43e2a..7d32a161587 100644
--- a/advocacy_docs/edb-postgres-ai/analytics/images/level-300.svg
+++ b/advocacy_docs/edb-postgres-ai/analytics/images/level-300.svg
@@ -1 +1 @@
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/advocacy_docs/edb-postgres-ai/analytics/images/level-50-architecture.png b/advocacy_docs/edb-postgres-ai/analytics/images/level-50-architecture.png
deleted file mode 100644
index fb983b28acd..00000000000
--- a/advocacy_docs/edb-postgres-ai/analytics/images/level-50-architecture.png
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:079cecc1a546705681e2a0a302680172726195aead9d6f63e49ecf702326a0e9
-size 436789
diff --git a/advocacy_docs/edb-postgres-ai/analytics/images/level-50.svg b/advocacy_docs/edb-postgres-ai/analytics/images/level-50.svg
deleted file mode 100644
index 1fd5c5b12d2..00000000000
--- a/advocacy_docs/edb-postgres-ai/analytics/images/level-50.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/advocacy_docs/edb-postgres-ai/analytics/images/old-level-300.svg b/advocacy_docs/edb-postgres-ai/analytics/images/old-level-300.svg
new file mode 100644
index 00000000000..6b59fc43e2a
--- /dev/null
+++ b/advocacy_docs/edb-postgres-ai/analytics/images/old-level-300.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/advocacy_docs/security/advisories/cve20244545.mdx b/advocacy_docs/security/advisories/cve20244545.mdx
index 5f73256e654..753b434c0d6 100644
--- a/advocacy_docs/security/advisories/cve20244545.mdx
+++ b/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.
\ No newline at end of file
+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.
diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx
index 956ce50e7cc..4e6cc927bd0 100644
--- a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx
+++ b/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
diff --git a/product_docs/docs/biganimal/release/release_notes/2024_07_jul_rel_notes.mdx b/product_docs/docs/biganimal/release/release_notes/2024_07_jul_rel_notes.mdx
new file mode 100644
index 00000000000..a47225dd5f5
--- /dev/null
+++ b/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.
+
+
+
diff --git a/product_docs/docs/biganimal/release/release_notes/index.mdx b/product_docs/docs/biganimal/release/release_notes/index.mdx
index d793fbe9f52..10af724b2fb 100644
--- a/product_docs/docs/biganimal/release/release_notes/index.mdx
+++ b/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 |
|--------------------------------------|
diff --git a/product_docs/docs/epas/16/upgrading/index.mdx b/product_docs/docs/epas/16/upgrading/index.mdx
index 097888a1cff..b2196724d75 100644
--- a/product_docs/docs/epas/16/upgrading/index.mdx
+++ b/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.
diff --git a/product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/01_performing_an_upgrade/01_linking_versus_copying.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/01_performing_an_upgrade/01_linking_versus_copying.mdx
similarity index 100%
rename from product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/01_performing_an_upgrade/01_linking_versus_copying.mdx
rename to product_docs/docs/epas/16/upgrading/major_upgrade/01_performing_an_upgrade/01_linking_versus_copying.mdx
diff --git a/product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/01_performing_an_upgrade/index.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/01_performing_an_upgrade/index.mdx
similarity index 94%
rename from product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/01_performing_an_upgrade/index.mdx
rename to product_docs/docs/epas/16/upgrading/major_upgrade/01_performing_an_upgrade/index.mdx
index 345b2ab8efd..d34de70e7a0 100644
--- a/product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/01_performing_an_upgrade/index.mdx
+++ b/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:
diff --git a/product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/02_invoking_pg_upgrade/01_command_line_options_reference.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/02_invoking_pg_upgrade/01_command_line_options_reference.mdx
similarity index 100%
rename from product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/02_invoking_pg_upgrade/01_command_line_options_reference.mdx
rename to product_docs/docs/epas/16/upgrading/major_upgrade/02_invoking_pg_upgrade/01_command_line_options_reference.mdx
diff --git a/product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/02_invoking_pg_upgrade/index.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/02_invoking_pg_upgrade/index.mdx
similarity index 100%
rename from product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/02_invoking_pg_upgrade/index.mdx
rename to product_docs/docs/epas/16/upgrading/major_upgrade/02_invoking_pg_upgrade/index.mdx
diff --git a/product_docs/docs/epas/16/upgrading/03_limitations.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/03_limitations.mdx
similarity index 100%
rename from product_docs/docs/epas/16/upgrading/03_limitations.mdx
rename to product_docs/docs/epas/16/upgrading/major_upgrade/03_limitations.mdx
diff --git a/product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/03_upgrading_to_advanced_server.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/03_upgrading_to_advanced_server.mdx
similarity index 100%
rename from product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/03_upgrading_to_advanced_server.mdx
rename to product_docs/docs/epas/16/upgrading/major_upgrade/03_upgrading_to_advanced_server.mdx
diff --git a/product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/04_upgrading_a_pgAgent_installation.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/04_upgrading_a_pgAgent_installation.mdx
similarity index 100%
rename from product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/04_upgrading_a_pgAgent_installation.mdx
rename to product_docs/docs/epas/16/upgrading/major_upgrade/04_upgrading_a_pgAgent_installation.mdx
diff --git a/product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/05_pg_upgrade_troubleshooting.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/05_pg_upgrade_troubleshooting.mdx
similarity index 100%
rename from product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/05_pg_upgrade_troubleshooting.mdx
rename to product_docs/docs/epas/16/upgrading/major_upgrade/05_pg_upgrade_troubleshooting.mdx
diff --git a/product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/06_reverting_to_the_old_cluster.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/06_reverting_to_the_old_cluster.mdx
similarity index 100%
rename from product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/06_reverting_to_the_old_cluster.mdx
rename to product_docs/docs/epas/16/upgrading/major_upgrade/06_reverting_to_the_old_cluster.mdx
diff --git a/product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/how_pg_upgrade_works.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/how_pg_upgrade_works.mdx
similarity index 100%
rename from product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/how_pg_upgrade_works.mdx
rename to product_docs/docs/epas/16/upgrading/major_upgrade/how_pg_upgrade_works.mdx
diff --git a/product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/index.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/index.mdx
similarity index 78%
rename from product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/index.mdx
rename to product_docs/docs/epas/16/upgrading/major_upgrade/index.mdx
index a5b62c7711e..8875082a540 100644
--- a/product_docs/docs/epas/16/upgrading/04_upgrading_an_installation_with_pg_upgrade/index.mdx
+++ b/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
---
!!! 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.
diff --git a/product_docs/docs/epas/16/upgrading/05_performing_a_minor_version_update_of_an_rpm_installation.mdx b/product_docs/docs/epas/16/upgrading/minor_upgrade/05_performing_a_minor_version_update_of_an_rpm_installation.mdx
similarity index 86%
rename from product_docs/docs/epas/16/upgrading/05_performing_a_minor_version_update_of_an_rpm_installation.mdx
rename to product_docs/docs/epas/16/upgrading/minor_upgrade/05_performing_a_minor_version_update_of_an_rpm_installation.mdx
index c2b25b5b955..a2fc0cf1330 100644
--- a/product_docs/docs/epas/16/upgrading/05_performing_a_minor_version_update_of_an_rpm_installation.mdx
+++ b/product_docs/docs/epas/16/upgrading/minor_upgrade/05_performing_a_minor_version_update_of_an_rpm_installation.mdx
@@ -1,6 +1,6 @@
---
-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/
---
@@ -8,7 +8,7 @@ redirects:
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
diff --git a/product_docs/docs/epas/16/upgrading/06_using_stackbuilder_plus_to_perform_a_minor_version_update.mdx b/product_docs/docs/epas/16/upgrading/minor_upgrade/06_using_stackbuilder_plus_to_perform_a_minor_version_update.mdx
similarity index 97%
rename from product_docs/docs/epas/16/upgrading/06_using_stackbuilder_plus_to_perform_a_minor_version_update.mdx
rename to product_docs/docs/epas/16/upgrading/minor_upgrade/06_using_stackbuilder_plus_to_perform_a_minor_version_update.mdx
index 228bff0b40c..cdb58a158c3 100644
--- a/product_docs/docs/epas/16/upgrading/06_using_stackbuilder_plus_to_perform_a_minor_version_update.mdx
+++ b/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/
---
diff --git a/product_docs/docs/epas/16/upgrading/minor_upgrade/index.mdx b/product_docs/docs/epas/16/upgrading/minor_upgrade/index.mdx
new file mode 100644
index 00000000000..2054f650900
--- /dev/null
+++ b/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).
diff --git a/product_docs/docs/epas/16/upgrading/minor_upgrade/performing_a_minor_version_update_of_Deb_installation.mdx b/product_docs/docs/epas/16/upgrading/minor_upgrade/performing_a_minor_version_update_of_Deb_installation.mdx
new file mode 100644
index 00000000000..32022878670
--- /dev/null
+++ b/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
+ ```
+
+ 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
+ ```
+
+ 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, 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/).
+
+!!!
+
+
diff --git a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.3.2.mdx b/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.3.2.mdx
index d6a1d484d33..49201f6f542 100644
--- a/product_docs/docs/hadoop_data_adapter/2/hadoop_rel_notes/hadoop_rel_notes_2.3.2.mdx
+++ b/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. |
diff --git a/product_docs/docs/mysql_data_adapter/2/06_features_of_mysql_fdw.mdx b/product_docs/docs/mysql_data_adapter/2/06_features_of_mysql_fdw.mdx
index 6f5756df295..1a9c9e4a442 100644
--- a/product_docs/docs/mysql_data_adapter/2/06_features_of_mysql_fdw.mdx
+++ b/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
diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.9.2_rel_notes.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.9.2_rel_notes.mdx
index 87e6353c8b1..86e31eb38be 100644
--- a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.9.2_rel_notes.mdx
+++ b/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. |
diff --git a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/09_11610_rel_notes.mdx b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/09_11610_rel_notes.mdx
index 06340cff94e..0f873dfa2c6 100644
--- a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/09_11610_rel_notes.mdx
+++ b/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
diff --git a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/12300_rel_notes.mdx b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/12300_rel_notes.mdx
new file mode 100644
index 00000000000..4676c4020a0
--- /dev/null
+++ b/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. |
diff --git a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/index.mdx b/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/index.mdx
index 70da5aeaa18..b238727c7de 100644
--- a/product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/index.mdx
+++ b/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) |
diff --git a/product_docs/docs/pgbouncer/1/supported_platforms.mdx b/product_docs/docs/pgbouncer/1/supported_platforms.mdx
index dbbc0186e2c..ae8be95e4b7 100644
--- a/product_docs/docs/pgbouncer/1/supported_platforms.mdx
+++ b/product_docs/docs/pgbouncer/1/supported_platforms.mdx
@@ -8,21 +8,22 @@ The EDB PgBouncer is supported on the same platforms as EDB Postgres Advanced Se
This table lists the latest EDB PgBouncer versions and their supported corresponding EDB Postgres Advanced Server (EPAS) versions.
-| EDB PgBouncer | EPAS 16 | EPAS 15 | EPAS 14 | EPAS 13 | EPAS 12 |
-| ------------- | ------- | ------- | ------- | ------- | ------- |
-| 1.22 | Y | Y | Y | Y | Y |
-| 1.21 | Y | Y | Y | Y | Y |
-| 1.20 | Y | Y | Y | Y | Y |
-| 1.19 | Y | Y | Y | Y | Y |
-| 1.18 | Y | Y | Y | Y | Y |
-| 1.17 | N | N | Y | Y | Y |
-| 1.16 | N | N | Y | Y | Y |
-| 1.15 | N | N | N | Y | Y |
-| 1.14 | N | N | N | Y | Y |
-| 1.13 | N | N | N | N | Y |
-| 1.12 | N | N | N | N | Y |
-| 1.9 | N | N | N | N | N |
-| 1.7 | N | N | N | N | N |
+| EDB PgBouncer | EPAS 16 | EPAS 15 | EPAS 14 | EPAS 13 | EPAS 12 |
+|---------------|---------|---------|---------|---------|---------|
+| 1.23 | Y | Y | Y | Y | Y |
+| 1.22 | Y | Y | Y | Y | Y |
+| 1.21 | Y | Y | Y | Y | Y |
+| 1.20 | Y | Y | Y | Y | Y |
+| 1.19 | Y | Y | Y | Y | Y |
+| 1.18 | Y | Y | Y | Y | Y |
+| 1.17 | N | N | Y | Y | Y |
+| 1.16 | N | N | Y | Y | Y |
+| 1.15 | N | N | N | Y | Y |
+| 1.14 | N | N | N | Y | Y |
+| 1.13 | N | N | N | N | Y |
+| 1.12 | N | N | N | N | Y |
+| 1.9 | N | N | N | N | N |
+| 1.7 | N | N | N | N | N |
The documented and supported functionality of each version of EDB PgBouncer is the same. The information in this documentation applies to all supported versions of EDB PgBouncer.
diff --git a/product_docs/docs/pgd/5/reference/functions-internal.mdx b/product_docs/docs/pgd/5/reference/functions-internal.mdx
index 19cb1d9acd3..82018aca12f 100644
--- a/product_docs/docs/pgd/5/reference/functions-internal.mdx
+++ b/product_docs/docs/pgd/5/reference/functions-internal.mdx
@@ -3,6 +3,7 @@ navTitle: Internal system functions
title: Internal system functions
indexdepth: 3
rootisheading: true
+deepToC: true
---
Listed below are internal system functions. Many are used in the creation of various views and we recommend that you do not use the functions directly, but rather use the views that they serve.
diff --git a/product_docs/docs/pgd/5/reference/pgd-settings.mdx b/product_docs/docs/pgd/5/reference/pgd-settings.mdx
index a6927e2afc6..9080ae0b5ee 100644
--- a/product_docs/docs/pgd/5/reference/pgd-settings.mdx
+++ b/product_docs/docs/pgd/5/reference/pgd-settings.mdx
@@ -61,12 +61,12 @@ Setting the replica identity of tables to `full` increases the volume of
WAL written and the amount of data replicated on the wire for the table.
!!! warning On setting bdr.default_replica_identity to default
-When setting `bdr.default_replica_identity` to `default` using `ALTER SYSTEM`
+When setting `bdr.default_replica_identity` to `default` using `ALTER SYSTEM`,
always quote the value, like this:
```sql
ALTER SYSTEM SET bdr.default_replica_identity="default";
```
-This is because default, unquoted, is a special value to the [ALTER SYSTEM](https://www.postgresql.org/docs/current/sql-altersystem.html) command which triggers the removal of the setting from the configuration file. This results in the system using the PGD default setting which is `auto`.
+You need to include the quotes because default, unquoted, is a special value to the [ALTER SYSTEM](https://www.postgresql.org/docs/current/sql-altersystem.html) command that triggers the removal of the setting from the configuration file. When the setting is removed, the system uses the PGD default setting, which is `auto`.
!!!
### `bdr.ddl_replication`
diff --git a/product_docs/docs/pge/16/upgrading/major_upgrade.mdx b/product_docs/docs/pge/16/upgrading/major_upgrade.mdx
index 3064745af4f..c8845a87db4 100644
--- a/product_docs/docs/pge/16/upgrading/major_upgrade.mdx
+++ b/product_docs/docs/pge/16/upgrading/major_upgrade.mdx
@@ -7,9 +7,9 @@ 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/04_upgrading_an_installation_with_pg_upgrade/06_reverting_to_the_old_cluster/#reverting_to_the_old_cluster).
+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
+## 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.
@@ -31,10 +31,10 @@ If a problem occurs during the upgrade process, you can [revert to the previous
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/04_upgrading_an_installation_with_pg_upgrade/).
+!!!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
+### 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.
@@ -42,12 +42,12 @@ Use [pg_dumpall](https://www.postgresql.org/docs/current/app-pg-dumpall.html), [
[Install EDB Postgres Extended Server](../installing/) version 16. Only install the packages. Don't perform any other configurations.
-### Creating a target server
+### 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/04_upgrading_an_installation_with_pg_upgrade/03_upgrading_to_advanced_server/#step-2---empty-the-target-database).
+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
```
@@ -60,7 +60,7 @@ If you don't want to create a new target instance but want to reuse an existing
```
1. As postgres, initialize the new server:
-
+
```
/usr/lib/edb-pge/16/bin/initdb -D /var/lib/edb-pge/16/upgrade_target
```
@@ -75,7 +75,7 @@ If you don't want to create a new target instance but want to reuse an existing
/usr/lib/edb-pge/16/bin/pg_ctl -D /var/lib/edb-pge/16/upgrade_target start
```
- !!!note
+ !!!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`
@@ -92,20 +92,20 @@ If you don't want to create a new target instance but want to reuse an existing
### 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/04_upgrading_an_installation_with_pg_upgrade/03_upgrading_to_advanced_server/#step-4---stop-all-component-services-and-servers) for more information
+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:
-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
```
@@ -134,7 +134,7 @@ If you don't want to create a new target instance but want to reuse an existing
1. Restart the extensions or component services you disabled in the source cluster but in the target cluster.
-### Cleaning up after upgrade
+### Cleaning up after upgrade
After you verify that pg_upgrade migrated the data successfully, and the services are running as expected, perform a cleanup.
@@ -150,6 +150,6 @@ After you verify that pg_upgrade migrated the data successfully, and the service
./delete_old_cluster.sh
```
-## More information
+## More information
-Review [Upgrading an installation with pg_upgrade](/epas/latest/upgrading/04_upgrading_an_installation_with_pg_upgrade/) for more information on pg_upgrade options, troubleshooting, and other considerations.
+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/src/pages/index.js b/src/pages/index.js
index daa7f6cda9d..a16c5c03e9d 100644
--- a/src/pages/index.js
+++ b/src/pages/index.js
@@ -29,7 +29,7 @@ const IndexCard = ({ iconName, headingText, children }) => (
);
const BannerCard = ({ iconName, headingText, children }) => (
-
+
@@ -48,7 +48,7 @@ const BannerCard = ({ iconName, headingText, children }) => (
);
const BannerSubCard = ({ iconName, headingText, to, children }) => (
-
+
@@ -71,7 +71,7 @@ const BannerSubCard = ({ iconName, headingText, to, children }) => (
);
const BannerWideCard = ({ iconName, headingText, to, children }) => (
-
+
{children}
@@ -79,7 +79,11 @@ const BannerWideCard = ({ iconName, headingText, to, children }) => (
);
const BannerWideCardLink = ({ to, className, children }) => (
-
+
{children}
);
@@ -271,7 +275,11 @@ const Page = () => {
-
+
Downloads and Repositories
diff --git a/tools/automation/actions/link-check/action.yml b/tools/automation/actions/link-check/action.yml
index 7d8c3526cad..684aa13d563 100644
--- a/tools/automation/actions/link-check/action.yml
+++ b/tools/automation/actions/link-check/action.yml
@@ -7,4 +7,7 @@ inputs:
update-links:
description: "Set to true/1 causes the action to update links where possible to avoid redirects"
required: false
+ content-path:
+ description: "The base path for docs content. Path should contain product_docs and/or advocacy_docs subdirectories"
+ required: false
diff --git a/tools/automation/actions/link-check/index.js b/tools/automation/actions/link-check/index.js
index 5e3ad664fb3..4610a0e5c11 100644
--- a/tools/automation/actions/link-check/index.js
+++ b/tools/automation/actions/link-check/index.js
@@ -22,9 +22,11 @@ const noWarnPaths = [
"/playground/1/01_examples/link-tests",
"/playground/1/01_examples/link-test",
];
+
const args = process.argv.slice(2);
const basePath =
args[0] ||
+ core?.getInput("content-path") ||
path.resolve(path.dirname(new URL(import.meta.url).pathname), "../../../..");
let ghCore = core;