Merge branch 'develop' into DOCS-1247-PGD-6.0-Docs

Author: djw-m

.github/workflows/deploy-main.yml

@@ -41,6 +41,18 @@ jobs:
     if: ${{ !cancelled() }}
     runs-on: ubuntu-22.04
     steps:
+      - name: publish release notes
+        if: success()
+        continue-on-error: true
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}      
+        run: |
+          draft_tag=`gh release list --repo EnterpriseDB/docs --limit 1 --json "isDraft,tagName" --jq '.[] | select(.isDraft) | .tagName'`
+          if [[ -n "$draft_tag" ]]; then
+            echo "Publishing draft release for: $draft_tag"
+            gh release edit "$draft_tag" --repo EnterpriseDB/docs --draft=false
+          fi
+
       - uses: act10ns/slack@v2
         with:
           status: ${{ needs.deploy-to-netlify.result }}

.github/workflows/tools-events.yml

@@ -35,11 +35,19 @@ jobs:
                 "deleted": ${{ github.event.deleted || false }}
               },
               "action": "${{ github.event.action }}",
-              "number": "${{ github.event.number }}",
+              "pull_request": {
+                "url": "${{ github.event.pull_request && github.event.pull_request.url || '' }}",
+                "number": "${{ github.event.pull_request && github.event.number || '' }}",
+                "state": "${{ github.event.pull_request && github.event.pull_request.state || '' }}",
+                "title": ${{ github.event.pull_request && toJSON(github.event.pull_request.title) || '""' }},
+                "body": ${{ github.event.pull_request && toJSON(github.event.pull_request.body) || '""' }},
+                "draft": ${{ github.event.pull_request && github.event.pull_request.draft || false }},
+                "merged": ${{ github.event.pull_request && github.event.pull_request.merged || false }},
+                "labels": ${{ github.event.pull_request && toJSON(github.event.pull_request.labels) || '[]' }}
+              },
               "release": {
                 "tag_name": ${{ github.event.release && toJSON(github.event.release.tag_name) || '""' }},
                 "id": "${{ github.event.release && github.event.release.id || '' }}",
-                "tag": ${{ github.event.release && toJSON(github.event.release.tag_name) || '""' }},
                 "name": ${{ github.event.release && toJSON(github.event.release.name) || '""' }},
                 "body": ${{ github.event.release && toJSON(github.event.release.body) || '""' }},
                 "draft": ${{ github.event.release && github.event.release.draft || false }}

advocacy_docs/pg_extensions/otel/installing.mdx

@@ -26,6 +26,11 @@ Before you begin the installation process:
 
   To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads) and follow the instructions provided there.
 
+  If you are using RHEL 9, you also need to install the EPEL repository:
+  ```shell
+  sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
+  ```
+
 
 ### Install the package
 

advocacy_docs/pg_extensions/pg_tuner/configuring.mdx

@@ -43,6 +43,8 @@ The following custom GUCs control the EDB Postgres Tuner `work_mem` tuning behav
 
 - `edb_pg_tuner.buffer_size` — Maximum query count for tracking statistics. The default is 5000.
 
+- `edb_pg_tuner.container_memory_limit_file_path` — Specifies the path to the file that contains the memory limit set by the container runtime, such as Docker or Kubernetes. This file is read by `edb_pg_tuner` to determine the maximum amount of memory available to the database process when running inside a container. Based on this limit, the tuner can generate optimised PostgreSQL configuration recommendations that are container-aware. The file is at `/sys/fs/cgroup/memory/memory.limit_in_bytes` by default.
+
 ## Recommended GUCs
 
 EDB Postgres Tuner can recommend the following GUCs. The `static` category provides fixed recommendation settings. The `dynamic` category uses specific algorithms to suggest a better setting according to your workload or hardware resources.

advocacy_docs/supported-open-source/cloud_native_pg/index.mdx

@@ -1,28 +1,27 @@
 ---
-title: CloudNativePG
+title: CloudNativePG™
 navTitle: CloudNativePG
 navRootedTo: /edb-postgres-ai/platforms-and-tools/kubernetes
-description: EDB supports CloudNativePG.
+description: EDB supports CloudNativePG™.
 directoryDefaults:
   iconName: logos/KubernetesMono
   product: CloudNativePG
 
 ---
 
-CloudNativePG is the Kubernetes operator that covers the full lifecycle of a highly available Postgres database cluster with a primary/standby architecture, using native streaming replication.
+CloudNativePG™ is the Kubernetes operator that covers the full lifecycle of a highly available Postgres database cluster with a primary/standby architecture, using native streaming replication.
 
 !!! Note
-    Looking for CloudNativePG documentation? Head over to [cloudnative-pg.io/docs/](https://cloudnative-pg.io/docs/).
+    Looking for CloudNativePG™ documentation? Head over to [cloudnative-pg.io/docs/](https://cloudnative-pg.io/docs/).
 
-CloudNativePG was originally built by EDB, then released open source under Apache License 2.0 and submitted for CNCF Sandbox in April 2022. The source code repository is in [Github](https://github.com/cloudnative-pg/cloudnative-pg).
+CloudNativePG™ was originally built by EDB, then released open source under Apache License 2.0 and submitted for CNCF Sandbox in April 2022. The source code repository is in [Github](https://github.com/cloudnative-pg/cloudnative-pg).
 
 Key features available include:
+
 - Kubernetes API integration for high availability
 - Self-healing through failover and automated recreation of replicas
 - Capacity management with scale up/down capabilities
 - Planned switchovers for scheduled maintenance
 - Read-only and read-write Kubernetes services definitions
 - Rolling updates for Postgres minor versions and operator upgrades
 - Continuous backup and point-in-time recovery
-
-

package-lock.json

@@ -18,6 +18,6 @@ redirects:
 
 **Required authorization to activate:** EDB Postgres Advanced Server service account
 
-`max_wal_size` specifies the maximum size for the WAL to reach between automatic WAL checkpoints. This is a soft limit. WAL size can exceed `max_wal_size` under special circumstances, such as when under a heavy load, with a failing archive_command, or with a high `wal_keep_segments` setting.
+`max_wal_size` specifies the maximum size for the WAL to reach between automatic WAL checkpoints. This is a soft limit. WAL size can exceed `max_wal_size` under special circumstances, such as when under a heavy load, with a failing archive_command, or with a high `wal_keep_size` setting.
 
 Increasing this parameter can increase the amount of time needed for crash recovery. You can set this parameter in the `postgresql.conf` file or on the server command line.

product_docs/docs/epas/17/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/08_max_wal_size.mdx

@@ -4,8 +4,8 @@ navTitle: Release notes
 description: Release notes for Postgres Enterprise Manager 10.0 and later
 indexCards: none
 navigation:
-  - pem_10.0.0_rel_notes
   - pem_10.1.0_rel_notes
+  - pem_10.0.0_rel_notes
 originalFilePath: product_docs/docs/pem/10/pem_rel_notes/src/meta.yml
 editTarget: originalFilePath
 ---
@@ -16,5 +16,5 @@ The Postgres Enterprise Manager documentation describes the latest version of Po
 
 | Postgres Enterprise Manager version | Release Date |
 |---|---|
-| [10.0.0](./pem_10.0.0_rel_notes) | 24th Mar 2025 |
 | [10.1.0](./pem_10.1.0_rel_notes) | 15th May 2025 |
+| [10.0.0](./pem_10.0.0_rel_notes) | 24th Mar 2025 |

product_docs/docs/pem/10/pem_rel_notes/index.mdx

@@ -1,6 +1,6 @@
 ---
-title: EDB CloudNativePG Global Cluster
-description: EDB CloudNativePG Global Cluster is a Kubernetes operator designed to deploy and manage EDB Postgres Distributed clusters running in private, public, hybrid, or multi-cloud environments.
+title: EDB Postgres® AI for CloudNativePG™ Global Cluster
+description: EDB Postgres® AI for CloudNativePG™ Global Cluster is a Kubernetes operator designed to deploy and manage EDB Postgres Distributed clusters running in private, public, hybrid, or multi-cloud environments.
 originalFilePath: src/index.md
 indexCards: none
 navigation:
@@ -41,13 +41,12 @@ directoryDefaults:
   iconName: logos/KubernetesMono
   displayBanner: >-
     We're in the process of migrating the documentation from the previous EDB
-    Postgres Distributed for Kubernetes name to the new EDB CloudNativePG Global
-    Cluster name. You may see references to both names in this documentation.
+    Postgres Distributed for Kubernetes name to the new EDB Postgres® AI for CloudNativePG™ Global Cluster name. You may see references to both names in this documentation.
 pdf: true
 
 ---
 
-EDB Postgres Distributed for Kubernetes (`PGD4K`) is an
+EDB Postgres® AI for CloudNativePG™ Global Cluster (also `CNPG-GC` or `PGD4K`) is an
 operator designed to manage EDB Postgres Distributed (PGD) workloads on
 Kubernetes, with traffic routed by PGD Proxy.
 

product_docs/docs/postgres_distributed_for_kubernetes/1/index.mdx

@@ -1,4 +1,9 @@
 ---
-title: ''
+title: Troubleshooting
+navTitle: Troubleshooting
 originalFilePath: 'src/troubleshooting.md'
 ---
+
+!!! Note
+Content for this page is in development.
+!!!