EnterpriseDB · josh-heyer · Dec 23, 2024 · Dec 10, 2024 · Dec 9, 2024 · Dec 10, 2024
@@ -74,7 +74,10 @@ jobs:
 
       - name: Process changes
         id: changes
-        run: ${{ github.workspace }}/destination/scripts/source/dispatch_product.py ${{env.SOURCE_REPO }}  ${{ github.workspace }}
+        run: |           
+          git config --global user.name "github-actions[bot]"
+          git config --global user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          ${{ github.workspace }}/destination/scripts/source/dispatch_product.py ${{env.SOURCE_REPO }}  ${{ github.workspace }}
         working-directory: source
 
       - name: Update PR body

@@ -13,16 +13,16 @@ We recommend that users adopt the most recent versions of Postgres for general u
 
 | Postgres distribution        | Cluster type                                   | Versions |
 | ---------------------------- | ---------------------------------------------- | -------- |
-| PostgreSQL                   | Single-node, primary/standby high-availability | 12–16    |
-| EDB Postgres Advanced Server | Single node, primary/standby high availability | 14–16    |
-| EDB Postgres Extended Server | Distributed high-availability                  | 14–16    |
-| EDB Postgres Advanced Server | Distributed high-availability                  | 14–16    |
+| PostgreSQL                   | Single-node, primary/standby high-availability | 12–17    |
+| EDB Postgres Advanced Server | Single node, primary/standby high availability | 14–17    |
+| EDB Postgres Extended Server | Distributed high-availability                  | 14–17    |
+| EDB Postgres Advanced Server | Distributed high-availability                  | 14–17    |
 
 ## Postgres distribution using your cloud account
 
 | Postgres distribution        | Cluster type                                   | Versions |
 | ---------------------------- | ---------------------------------------------- | -------- |
-| PostgreSQL                   | Single-node, primary/standby high-availability | 12–16    |
-| EDB Postgres Advanced Server | Single-node, primary/standby high-availability | 12–16    |
-| EDB Postgres Extended Server | Distributed high-availability                  | 14–16    |
-| EDB Postgres Advanced Server | Distributed high-availability                  | 14–16    |
+| PostgreSQL                   | Single-node, primary/standby high-availability | 12–17    |
+| EDB Postgres Advanced Server | Single-node, primary/standby high-availability | 12–17    |
+| EDB Postgres Extended Server | Distributed high-availability                  | 14–17    |
+| EDB Postgres Advanced Server | Distributed high-availability                  | 14–17    |
@@ -5,6 +5,9 @@ navTitle: Configuring
 
 You must add the extension to `shared_preload_libraries` on both the primary instance as well as any standby that's used for high availability (failover or switchover) purposes.
 
+!!!Note 
+   You should not run the `CREATE EXTENSION` command for PG Failover Slots.    
+
 ## Prerequisite settings
 
 The following settings are required: 

@@ -13,7 +13,7 @@ directoryDefaults:
 PG Failover Slots (pg_failover_slots) is an extension released as open source software under the PostgreSQL License. If you have logical replication publications on Postgres databases that are also part of a streaming replication architecture,
 PG Failover Slots avoids the need for you to reseed your logical replication tables when a new standby gets promoted to primary.
 
-Since the replication slot used by logical replication is maintained only on the primary node, downstream subscribers don't receive any new changes from the newly promoted primary until the slot is created on the newly promoted primary. Picking up logical replication changes from the newly promoted standby is unsafe because THE following information will be lost:
+Since the replication slot used by logical replication is maintained only on the primary node, downstream subscribers don't receive any new changes from the newly promoted primary until the slot is created on the newly promoted primary. Picking up logical replication changes from the newly promoted standby is unsafe because the following information will be lost:
 -  The data a subscriber confirmed receiving
 -  The log data that still needs to be retained for the subscriber 
 

@@ -15,3 +15,6 @@ EDB Postgres Tuner is a PostgreSQL extension that automates 15+ years of EDB Pos
 Postgres uses some conservative settings to cover different host sizes. Some of the settings provided by Postgres are unsuitable because they don't take advantage of the available resources. Configuration parameters set by `initdb` don't account for the amount of memory, the number of CPU cores, and the kind of storage devices available to set appropriate values for parameters. Some parameters depend on the workload. The workload provides metrics to use to fine-tune some parameters dynamically.
 
 This extension provides safe recommendations that maximize the use of available resources. It also allows you to control if and when to apply the changes. EDB Postgres Tuner enables you to apply tuning recommendations automatically or view tuning recommendations and selectively apply them. It's now possible to successfully manage demanding Postgres databases without tuning expertise.   
+
+As an alternative to using the Postgres Tuner extension, EDB offers a web-based utility to provide tuning advice, generate custom configurations for your operating system and `postgresql.conf` file, and output printable guides.  For 
+more information, see the [EDB Postgres Tuner web utility](https://postgrestuner.enterprisedb.com).
@@ -1,60 +1,60 @@
 ---
-title: Using Hosted Artifactory with EDB repositories
+title: Using hosted Artifactory with EDB repositories
 navTitle: Hosted Artifactory
-description: How to use Hosted JFrog Artifactory with EDB repositories
+description: How to use hosted JFrog Artifactory with EDB repositories.
 ---
 
-To set up Hosted JFrog Artifactory with EDB repositories, you need to create remote repositories in Artifactory. This article shows how to use Hosted JFrog Artifactory with EDB repositories. The process is different for on-premises Artifactory.
+To set up hosted JFrog Artifactory with EDB repositories, you need to create remote repositories in Artifactory, as described in the procedure that follows. The process is different for on-premises Artifactory.
 
 ## Get the base URLs
 
-The process is requires a base URLs to access the EDB repositories.
+The process requires that you first get the base URLs to access the EDB repositories.
 
 1. From your EDB account, [get your token](../../getting_started/with_cli/get_your_token).
 
-1. Make a note of your token, for our examples, the token will be `xyz123`.
+1. Make a note of your token. For this example, the token is `xyz123`.
 
-1. Select the repository you want to access, for example, `standard`. :
+1. Select the repository you want to access, for example, `standard`.
 
-1. Your base URL will is then formed as:
+1. Your base URL is then formed as:
 
     ```
     https://downloads.enterprisedb.com/<token>/<repository>/
     ```
 
-    For the `standard` with our token, the repository, the base URL will be:
+    For the `standard` repository with the same token, the base URL is:
 
     ```
     https://downloads.enterprisedb.com/xyz123/standard/
     ```
 
 1. Append the appropriate path for the repository type. 
-   For example, for a Red Hat Enterprise Linux 9 on x86 architecture, append `rpm/el/9/x86_64/` and seperately append `rpm/el/9/noarch/` for the noarch packages, to create two base URLs. With our example, the base URLs will be:
+   For example, for a Red Hat Enterprise Linux 9 on x86 architecture, to create the two base URLs, append `rpm/el/9/x86_64/`. Then separately append `rpm/el/9/noarch/` for the `noarch` packages. Using the same example token and repository, the base URLs are:
 
     ```
     https://downloads.enterprisedb.com/xyz123/standard/rpm/el/9/x86_64/
     https://downloads.enterprisedb.com/xyz123/standard/rpm/el/9/noarch/
     ```
 
-## Setup Artifactory remote repositories
+## Set up Artifactory remote repositories
 
-With your base URLs, you can now create the remote repositories in Artifactory.
+After you have your base URLs, you can create the remote repositories in Artifactory.
 
-Use the Artifactory UI to create the 2 repositories (`x86_64` and `noarch`), one for each base URL. The `x86_64` repository will contain the `rpm` packages specifically for the `x86_64` architecture, and the `noarch` repository will contain the `rpm` packages which are for any architecture.
+Use the Artifactory interface to create the two repositories (`x86_64` and `noarch`), one for each base URL. The `x86_64` repository will contain the `rpm` packages specifically for the `x86_64` architecture. The `noarch` repository will contain the `rpm` packages, which are for any architecture.
 
 Starting with the `x86_64` base URL:
 
-1. Select **Create Repository** and choose **Remote**.
-1. Choose **rpm** as the repository type.
+1. Select **Create Repository > Remote**.
+1. Select **rpm** as the repository type.
 1. Enter a unique name for the repository key, for example, `edb-x86_64`.
-1. Fill in the URL as `https://downloads.enterprisedb.com/xyz123/standard/rpm/el/9/x86_64/`.
+1. Enter the `x86_64` base URL, for example,  `https://downloads.enterprisedb.com/xyz123/standard/rpm/el/9/x86_64/`.
 1. Select **Create Remote Repository**.
 
-At this point, a prompt to setup the `yum` client configuration appears. This client configuration is the configuration you use on your local server or VM to access the configured EDB repositories via Artifactory.
+    A prompt to set up the yum client configuration appears. This client configuration is the configuration you use on your local server or VM to access the configured EDB repositories via Artifactory.
 
-6.  On your local RHEL 9 server or VM create the yum repository file `/etc/yum.repos.d/artifactory-edb.repo`.
+1.  On your local RHEL 9 server or VM, create the yum repository file `/etc/yum.repos.d/artifactory-edb.repo`.
 
-7.  Add the text generated by Artifactory to the `/etc/yum.repos.d/artifactory-edb.repo` file. The generated text should resemble:
+1.  Add the text generated by Artifactory to the `/etc/yum.repos.d/artifactory-edb.repo` file. The generated text should resemble:
 
     ```
     [Artifactory]
@@ -64,9 +64,9 @@ At this point, a prompt to setup the `yum` client configuration appears. This cl
     gpgcheck=0
     ```
 
-    Remove the `<PATH_TO_REPODATA_FOLDER>` from the baseurl. It's not needed.
+    Remove `<PATH_TO_REPODATA_FOLDER>` from the baseurl. It's not needed.
 
-    You should also edit the `Artifactory` name to be more descriptive and unique as there are multiple repositories to add. For example, append `-edb-x86_64` to the name to give:
+    Also edit the name to be more descriptive and unique, as there are multiple repositories to add. For example, append `-edb-x86_64` to the name:
 
     ```
     [Artifactory-edb-x86_64]
@@ -78,7 +78,7 @@ At this point, a prompt to setup the `yum` client configuration appears. This cl
 
     Save the file.
 
-8.  Repeat the process, steps 1-7, to create an Artifactory remote repository for the `noarch` repository. When you generate the **yum** configuration text, add that text to the `/etc/yum.repos.d/artifactory-edb.repo` file previously created. The file should now contain:
+1.  Repeat steps 1-7, to create an Artifactory remote repository for the `noarch` repository. After you generate the yum configuration text, add that text to the `/etc/yum.repos.d/artifactory-edb.repo` file you previously created. The file should now contain:
 
     ```
     [Artifactory-edb-x86_64]
@@ -94,31 +94,32 @@ At this point, a prompt to setup the `yum` client configuration appears. This cl
     gpgcheck=0
     ```
 
-## Check the configuration works
-
-On the local Linux server where the `/etc/yum.repos.d/artifactory-edb.repo` file resides, check that the repositories configuration is correct by running the following command:
+## Check that the configuration works
 
+On the local Linux server where the `/etc/yum.repos.d/artifactory-edb.repo` file resides, check that the repository's configuration is correct by running the following command:
 
 ```bash
 dnf repolist | grep -i Art
 ```    
 
-The output returned should be:
+A correct configuration produces the following output:
 
 ```
 Artifactory-edb-noarch                   Artifactory-edb-noarch
 Artifactory-edb-x86_64                   Artifactory-edb-x86_64
 ```
 
-As you can see the two repositories are now configured. 
+This result indicates that the two repositories are configured. 
+
+You can now check for a specific package, such as `postgresextended` in the Artifactory repository, using the `dnf list` command. 
 
-You can now check for a specific package, such as `postgresextended` in the Artifactory repository, using the `dnf list` command. The package name for this example is `edb-postgresextended15-server` which is EDB Postgres Extended 15. To ensure that you don't get false positives from other repositories,  disable all repositories using `--disable-repo=*` and then only enable the `Artifactory-` prefixed repositories using `--enablerepo=Artifactory-*`:
+The package name for this example is `edb-postgresextended15-server`, which is EDB Postgres Extended 15. To ensure that you don't get false positives from other repositories, disable all repositories using `--disable-repo=*`, and then enable only the `Artifactory-` prefixed repositories using `--enablerepo=Artifactory-*`:
 
 ```bash
 dnf list edb-postgresextended15-server --disablerepo=* --enablerepo=Artifactory-*
 ```
 
-If configured and working correctly the output should resemble:
+If the repository is configured and working correctly the output resembles:
 
 ```
 Updating Subscription Management repositories.

@@ -1,16 +1,13 @@
 ---
-title: Integrating with configuration management tools with EDB repositories
+title: Integrating configuration management tools with EDB repositories
 navTitle: Integrating
 description: How to integrate EDB repositories with configuration management tools
 ---
 
-In this section, you will find information on how to integrate EDB repositories with configuration management tools.
+This section includes information on how to integrate EDB repositories with configuration management tools.
 
   * [Hosted JFrog Artifactory](artifactory)
 
 <br/>
 <br/>
 <br/>
-
-
-
@@ -12,7 +12,7 @@ With the release of EPAS 17, the DRITA is being deprecated and will not be inclu
 !!!
 
 !!! Note 
-The `pgAgent` and `adminpack` packages are end of life from EPAS 17 and later.
+The `pgAgent` and `adminpack` packages are end of life in EPAS 17 and later.
 !!!
 
 | Type              | Description                                                                                                                                                                                                                                                                                                                                                                                                                                       | Addresses&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;                                                                                                                                                                                                                                                  |

@@ -2,11 +2,11 @@
 title: "APPENDCHILD"
 ---
 
-The `APPENDCHILD` function adds the node at the end of the list of children of a particular node. It returns the newly added node and if the node is already present, it removes the existing node before adding new node.
+The `APPENDCHILD` function adds the node at the end of the list of children of a particular node. It returns the newly added node and, if a node is already present, removes the existing node before adding the new node.
 
-You can append more than one child to a document node. However, a node cannot belong to several documents.
+You can append more than one child to a document node. However, a node can't belong to several documents.
 
-When appending elements, you cannot add an element to itself. Additionally, if the same element is added twice, only the latest is considered.
+When appending elements, you can't add an element to itself. Also, if the same element is added twice, only the latest is considered.
 
 ```
 APPENDCHILD(n DOMNode, newChild IN DOMNode) RETURN DOMNode
@@ -16,15 +16,15 @@ APPENDCHILD(n DOMNode, newChild IN DOMNode) RETURN DOMNode
 
 `n`
 
-The `DOMNode` where the new node is to be added.
+The `DOMNode` to add the new node to.
 
 `newchild`
 
-The child node to be added to the existing list of children of node n.
+The child node to add to the existing list of children of node `n`.
 
 ## Examples
 
-This example creates a new XML `DOMDocument` named `l_domdoc` and a new `DOMElement` named `l_department_element` with tag name `Departments`. It then appends the `DOMElement` as a child of the `DOMDocument`.
+This example creates an XML `DOMDocument` named `l_domdoc` and a `DOMElement` named `l_department_element` with the tag name `Departments`. It then appends the `DOMElement` as a child of the `DOMDocument`.
 
 ```sql
 DECLARE

@@ -2,7 +2,7 @@
 title: "CREATEELEMENT"
 ---
 
-The `CREATEELEMENT` function creates and returns a DOMElement.
+The `CREATEELEMENT` function creates and returns a `DOMElement`.
 
 ```
 CREATEELEMENT( doc DOMDocument, tagname IN VARCHAR2) RETURN DOMElement
@@ -16,11 +16,11 @@ Any `DOMDocument`.
 
 `tagname`
 
-Tag name to be given to the new `DOMElement`.
+Tag name to give to the new `DOMElement`.
 
 ## Examples
 
-This example creates a new XML `DOMDocument` named `l_domdoc` and a new `DOMElement` named `l_department_element` with tag name `Departments`. It then appends the `DOMElement` as a child of the `DOMDocument`.
+This example creates an XML `DOMDocument` named `l_domdoc` and a `DOMElement` named `l_department_element` with the tag name `Departments`. It then appends the `DOMElement` as a child of the `DOMDocument`.
 
 ```sql
 DECLARE

@@ -2,7 +2,7 @@
 title: "CREATETEXTNODE"
 ---
 
-The `CREATETEXTNODE` function creates and returns a DOMText node.
+The `CREATETEXTNODE` function creates and returns a `DOMText` node.
 
 ```
 CREATETEXTNODE( doc DOMDocument, data IN VARCHAR2) RETURN DOMText
@@ -20,7 +20,7 @@ Content provided for the `DOMText` node.
 
 ## Examples
 
-This example creates a new XML `DOMDocument`, a `DOMElement` with tag name “Departments” and a text node with “Depts list” as its value. The `DOMElement` is appended as a child to the `DOMDocument`, and the text node as a child to the `DOMElement`. 
+This example creates an XML `DOMDocument`, a `DOMElement` with the tag name `Departments`, and a text node with `Depts list` as its value. The `DOMElement` is appended as a child to the `DOMDocument` and the text node as a child to the `DOMElement`. 
 
 ```sql
 DECLARE

@@ -2,7 +2,7 @@
 title: "FREEDOCUMENT"
 ---
 
-The `FREEDOCUMENT` procedure is used to free the `DOMDocument` object.
+The `FREEDOCUMENT` procedure frees the `DOMDocument` object.
 
 ```
 FREEDOCUMENT(doc IN DOMDocument)
@@ -12,12 +12,12 @@ FREEDOCUMENT(doc IN DOMDocument)
 
 `doc`
 
-The `DOMDocument` to be made free.
+The `DOMDocument` to free.
 
 
 ## Examples
 
-This example creates a new `DOMDocument`, which is not accessible after it has been freed.
+This example creates a `DOMDocument` that's not accessible after it's free.
 
 ```sql
 DECLARE