Merge pull request #4557 from EnterpriseDB/release/2023-08-02

Release: 2023-08-02
EnterpriseDB · Aug 2, 2023 · 0213754 · 0213754 · github-actions · Aug 2, 2023
2 parents db9413f + 0b7bac4
commit 0213754
Show file tree

Hide file tree

Showing 15 changed files with 228 additions and 327 deletions.
diff --git a/advocacy_docs/supported-open-source/pgbackrest/06-use_case_1.mdx b/advocacy_docs/supported-open-source/pgbackrest/06-use_case_1.mdx
@@ -105,8 +105,6 @@ repo1-sftp-private-key-passphrase=BeSureToGenerateAndUseASecurePassphrase
 
 `repo1-sftp-host` defines the SFTP host containing the repository. It is also possible to generate a dedicated SSH key pair for the SFTP connection using a secured passphrase with it (stored in `repo1-sftp-private-key-passphrase`).
 
-Note: the SFTP file transfer is relatively slow compared to the other supported repository types.
-
 ##### Recommended Settings
 
 Use those settings to enable encryption, parallel operations and ensure displaying enough information in the console and in the log file:

diff --git a/advocacy_docs/supported-open-source/pgbackrest/99-faq.mdx b/advocacy_docs/supported-open-source/pgbackrest/99-faq.mdx
@@ -31,3 +31,12 @@ See [Setup TLS](https://pgbackrest.org/user-guide-rhel.html#repo-host/config) fo
 Since compression/decompression is performed on the Postgres host, the repository host does only need to encrypt/decrypt SSH or TLS connections. Usually 1 repository core per 4 Postgres cores is a good starting point.
 
 <!-- See https://github.com/pgbackrest/pgbackrest/issues/1618 for details. -->
+
+---
+
+- Does pgBackRest support immutable (WORM) storage?
+
+Immutable storage is a broad term referring to data storage that cannot be edited, altered, or deleted. WORM means _Write Once, Read Many_.
+
+With the current repository format, needing to have temporary files and updating information about the latest backups inside the repository, pgBackRest currently doesn't support this kind of storage.
+However, it is best practice to regularly save a copy of the repository content (backup set, archives, `.info` files,...) to an external storage.
diff --git a/advocacy_docs/supported-open-source/pgbackrest/index.mdx b/advocacy_docs/supported-open-source/pgbackrest/index.mdx
@@ -17,6 +17,6 @@ pgBackRest is an easy-to-use backup and restore tool that aims to enable your or
 !!! Note
     Looking for pgBackRest documentation? Head over to [http://www.pgbackrest.org](http://www.pgbackrest.org)
 
-pgBackRest [v2.46](https://github.com/pgbackrest/pgbackrest/releases/tag/release/2.46) is the current stable release. Release notes are on the [Releases](http://www.pgbackrest.org/release.html) page.
+pgBackRest [v2.47](https://github.com/pgbackrest/pgbackrest/releases/tag/release/2.47) is the current stable release. Release notes are on the [Releases](http://www.pgbackrest.org/release.html) page.
 
 EDB collaborates with the community on this open-source software. The packages are provided by the **PostgreSQL** community. All of the use cases shown in this document are fully tested and supported by **EDB Postgres Advanced Server**.
diff --git a/product_docs/docs/biganimal/release/reference/cli/index.mdx b/product_docs/docs/biganimal/release/reference/cli/index.mdx
@@ -96,8 +96,6 @@ The credential ba-user1 has been set up
 ```shell
 biganimal config set context_credential ba-user1
 ```
-!!!warning Current limitation
-   When an organization owner using BigAnimal's cloud account invites a user in another organization to join a second organization for that user, the user can't create a credential in the second organization. The workaround for this limitation is for the organization to set up their own identify provider. See [Setting up your identity provider](/biganimal/latest/getting_started/identity_provider/).
 
 ## Configuring
 The initial running of the CLI creates a hidden configuration folder in your user root directory. For example, for Linux it’s `${HOME}/.edb-cli`. The CLI persists the configuration file in this directory as well as the credentials.

diff --git a/product_docs/docs/hadoop_data_adapter/2/upgrading.mdx b/product_docs/docs/hadoop_data_adapter/2/upgrading.mdx
@@ -6,63 +6,58 @@ redirects:
 
 <div id="updating_the_hadoop_data_adapter" class="registered_link"></div>
 
-If you have an existing installation of MongoDB Foreign Data Wrapper that you installed using the EDB repository, you can use the `upgrade` command to update your repository configuration file and then upgrade to a more recent product version. To start the process, open a terminal window, assume superuser privileges, and enter the commands that apply to the operating system and package manager used for the installation:
+If you have an existing installation of Hadoop Foreign Data Wrapper that you installed using the EDB repository, you can update your repository configuration file and then upgrade Hadoop to a more recent product version. 
 
-## On RHEL or Rocky Linux or AlmaLinux or OL 8
+To perform the process, open a terminal window and enter the commands that apply to the operating system and package manager used for the installation:
 
-```shell
-# Update your edb.repo file to access the current EDB repository
-dnf upgrade edb-repo
+To update your repository configuration file:
 
-# Upgrade to the latest version product 
-dnf upgrade edb-as<xx>-hdfs_fdw
-# where <xx> is the EDB Postgres Advanced Server version number
+```shell
+sudo <package-manager> 
 ```
-## On RHEL or CentOS or OL 7:
 
-```shell
-# Update your edb.repo file to access the current EDB repository 
-yum upgrade edb-repo
+Where `<package-manager>` is the package manager used with your operating system:
+
+  | Package manager |         Operating system         |
+  | --------------- | -------------------------------- |
+  | dnf             | RHEL 8/9 and derivatives         |
+  | yum             | RHEL 7 and derivatives, CentOS 7 |
+  | zypper          | SLES                             |
+  | apt-get         | Debian and Ubuntu                |
+
+
+To upgrade to the latest product version, enter one of the following commands:
+
+  |         Operating system         |                                  Upgrade command                                  |
+  | -------------------------------- | --------------------------------------------------------------------------------- |
+  | RHEL 8/9 and derivatives         | `sudo dnf upgrade edb-as<xx>-hdfs_fdw`                              |
+  | RHEL 7 and derivatives, CentOS 7 | `sudo yum upgrade edb-as<xx>-hdfs_fdw edb-hdfs-libs`           |
+  | SLES                             | `sudo zypper upgrade edb-as<xx>-hdfs_fdw`                              |
+  | Debian and Ubuntu                | `sudo apt-get --only-upgrade install edb-as<xx>-hdfs-fdw edb-hdfs` |
+
+Where
+
+- `<package-manager>` is the package manager used with your operating system.
+
+- `<xx>` is the EDB Postgres Advanced Server version number.
+
+
+
+
+
+
+
+
+
+
+
 
-# Upgrade to the latest version product version
-yum upgrade edb-as<xx>-hdfs_fdw edb-libmongoc-libs
-# where <xx> is the EDB Postgres Advanced Server version number
-```
 
-## On SLES
 
-```shell
-# Update your edb.repo file to access the current EDB repository
-zypper upgrade edb-repo
 
-# Upgrade to the latest version product 
-zypper upgrade edb-as<xx>-hdfs_fdw
-# where <xx> is the EDB Postgres Advanced Server version number
-```
 
-## On Debian or Ubuntu
 
-```shell
-# Update your edb.repo file to access the current EDB repository
-zypper upgrade edb-repo
 
-# Upgrade to the latest version product
-apt-get --only-upgrade install edb-as<xx>-hdfs-fdw edb-libmongoc
-# where <xx> is the EDB Postgres Advanced Server version number
-```
 
-## On RHEL or CentOS 7 on PPCLE
 
-```shell
-# Update your edb.repo file to access the current EDB repository 
-yum upgrade edb-repo
-
-# Upgrade to the latest version product version
-yum upgrade edb-as<xx>-hdfs_fdw edb-libmongoc-at<yy>-libs     
-# where:
-# <xx> is the EDB Postgres Advanced Server version number
-# <yy> is Advance Toolchain major version number. For EDB Postgres 
-# Advanced Server versions 10 to 11, <yy> must be 10 and for 
-# EDB Postgres Advanced Server version 12 and later, <yy> must be 11. 
-```
 
diff --git a/product_docs/docs/jdbc_connector/42.5.4.1/installing/upgrading.mdx b/product_docs/docs/jdbc_connector/42.5.4.1/installing/upgrading.mdx
@@ -5,22 +5,23 @@ redirects:
   - /jdbc_connector/latest/04_installing_and_configuring_the_jdbc_connector/13_upgrading_rpm_install/
 ---
 
-If you have an existing JDBC Connector RPM installation, you can use yum or dnf to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter:
+If you have an existing JDBC Connector installation on a Linux platform, you can upgrade your repository configuration file, which enables access to the current EDB repository. Then you can upgrade to a more recent version of JDBC Connector.
 
--   On RHEL or CentOS 7:
+To update the `edb.repo` file:
 
-     `yum upgrade edb-repo`
+```shell
+# Update your repository configuration file
+sudo <package-manager> upgrade edb-repo
 
--   On RHEL or Rocky Linux or AlmaLinux 8:
+# Upgrade the installed product
+sudo <package-manager> upgrade edb-repo
+```
 
-     `dnf upgrade edb-repo`
+Where `<package-manager>` is the package manager used with your operating system:
 
-yum or dnf will update the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum or dnf to upgrade any installed packages:
-
--   On RHEL or CentOS 7:
-
-     `yum upgrade edb-jdbc`
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-     `dnf upgrade edb-jdbc`
+  | Package manager |         Operating system         |
+  | --------------- | -------------------------------- |
+  | dnf             | RHEL 8/9 and derivatives         |
+  | yum             | RHEL 7 and derivatives, CentOS 7 |
+  | zypper          | SLES                             |
+  | apt-get         | Debian and Ubuntu                |
diff --git a/product_docs/docs/migration_toolkit/55/upgrading.mdx b/product_docs/docs/migration_toolkit/55/upgrading.mdx
@@ -4,14 +4,23 @@ redirects:
   - /migration_toolkit/latest/13_upgrading_rpm_install/
 ---
 
-If you have an existing RPM installation, you can use `yum` (or the appropriate package manager for your operating system) to upgrade your repository configuration file and update to a more recent product version. To update the edb.repo file, assume superuser privileges and enter:
+You can upgrade an existing Linux installation by first upgrading the `edb.repo` file, which enables access to the current EnterpriseDB repository, and then upgrading Migration Toolkit.
 
-```text
-yum upgrade edb-repo
-```
+To upgrade the `edb.repo` file:
 
-yum will update the edb.repo file to enable access to the current EnterpriseDB repository, configured to connect with the credentials specified in your edb.repo file. Then, you can use yum to upgrade Migration toolkit:
+```shell
+# Update your repository configuration file
+sudo <package-manager> -y upgrade edb-repo
 
-```text
-yum upgrade edb-migrationtoolkit
+# Upgrade the installed product
+sudo <package-manager> -y edb-migrationtoolkit
 ```
+
+Where `<package-manager>` is the package manager used with your operating system:
+
+  | Package manager |             Operating system     |
+  | --------------- | -------------------------------- |
+  | dnf             | RHEL 8/9 and derivatives         |
+  | yum             | RHEL 7 and derivatives, CentOS 7 |
+  | zypper          | SLES                             |
+  | apt-get         | Debian and Ubuntu                |
diff --git a/product_docs/docs/mongo_data_adapter/5/upgrading.mdx b/product_docs/docs/mongo_data_adapter/5/upgrading.mdx
@@ -6,63 +6,39 @@ redirects:
 
 <div id="updating_the_mongo_data_adapter" class="registered_link"></div>
 
-If you have an existing installation of MongoDB Foreign Data Wrapper that you installed using the EDB repository, you can use the `upgrade` command to update your repository configuration file and then upgrade to a more recent product version. To start the process, open a terminal window, assume superuser privileges, and enter the commands applicable to the operating system and package manager used for the installation.
 
-## On RHEL or Rocky Linux or AlmaLinux or OL 8
+If you have an existing installation of MongoDB Foreign Data Wrapper that you installed using the EDB repository, you can update your repository configuration file and then upgrade MongoDB to a more recent product version. 
 
-```shell
-# Update your edb.repo file to access the current EDB repository
-dnf upgrade edb-repo
+To perform the process, open a terminal window and enter the commands that apply to the operating system and package manager used for the installation:
 
-# Upgrade to the latest version product 
-dnf upgrade edb-as<xx>-mongo_fdw
-# where <xx> is the EDB Postgres Advanced Server version number
-```
-## On RHEL or CentOS or OL 7
+To update your repository configuration file:
 
 ```shell
-# Update your edb.repo file to access the current EDB repository 
-yum upgrade edb-repo
-
-# Upgrade to the latest version product version
-yum upgrade edb-as<xx>-mongo_fdw edb-libmongoc-libs
-# where <xx> is the EDB Postgres Advanced Server version number
+sudo <package-manager> upgrade edb-repo
 ```
 
-## On SLES
-
-```shell
-# Update your edb.repo file to access the current EDB repository
-zypper upgrade edb-repo
+Where `<package-manager>` is the package manager used with your operating system:
 
-# Upgrade to the latest version product 
-zypper upgrade edb-as<xx>-mongo_fdw
-# where <xx> is the EDB Postgres Advanced Server version number
-```
+  | Package manager |         Operating system         |
+  | --------------- | -------------------------------- |
+  | dnf             | RHEL 8/9 and derivatives         |
+  | yum             | RHEL 7 and derivatives, CentOS 7 |
+  | zypper          | SLES                             |
+  | apt-get         | Debian and Ubuntu                |
 
-## On Debian or Ubuntu
+
+To upgrade to the latest product version, enter one of the following commands:
 
-```shell
-# Update your edb.repo file to access the current EDB repository
-zypper upgrade edb-repo
+  |         Operating system         |                                  Upgrade command                                   |
+  | -------------------------------- | ---------------------------------------------------------------------------------- |
+  | RHEL 8/9 and derivatives         | `sudo dnf upgrade edb-as<xx>-mongo_fdw`                              |
+  | RHEL 7 and derivatives, CentOS 7 | `sudo yum upgrade edb-as<xx>-mongo_fdw edb-libmongoc-libs`           |
+  | SLES                             | `sudo zypper upgrade edb-as<xx>-mongo_fdw`                              |
+  | Debian and Ubuntu                | `sudo apt-get --only-upgrade install edb-as<xx>-mongo-fdw edb-libmongoc` |
 
-# Upgrade to the latest version product
-apt-get --only-upgrade install edb-as<xx>-mongo-fdw edb-libmongoc
-# where <xx> is the EDB Postgres Advanced Server version number
-```
+Where
 
-## On RHEL or CentOS 7 on PPCLE
+- `<package-manager>` is the package manager used with your operating system.
 
-```shell
-# Update your edb.repo file to access the current EDB repository 
-yum upgrade edb-repo
+- `<xx>` is the EDB Postgres Advanced Server version number.
 
-# Upgrade to the latest version product version
-yum upgrade edb-as<xx>-mongo_fdw edb-libmongoc-at<yy>-libs
-
-# where:
-# <xx> is the EDB Postgres Advanced Server version number
-# <yy> is Advance Toolchain major version number. For EDB Postgres 
-# Advanced Server versions 10 to 11, <yy> must be 10 and for 
-# EDB Postgres Advanced Server version 12 and later, <yy> must be 11. 
-```
diff --git a/product_docs/docs/mysql_data_adapter/2/upgrading.mdx b/product_docs/docs/mysql_data_adapter/2/upgrading.mdx
@@ -7,42 +7,39 @@ redirects:
 
 <div id="updating_the_mysql_data_adapter" class="registered_link"></div>
 
-## Upgrading an RPM installation
-
-If you have an existing RPM installation of MySQL Foreign Data Wrapper, you can use yum or dnf to upgrade your repository configuration file and upgrade to a more recent product version. yum or dnf will update the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum or dnf to upgrade any installed packages:
-
-- For MySQL 8:
-
-    -  On RHEL or CentOS 7:
-       ```shell
-       sudo yum -y upgrade edb-as<xx>-mysql8_fdw* mysql-community-devel
-       ```
-    -  On RHEL or Rocky Linux or AlmaLinux 8:
-       ```shell
-       sudo dnf -y upgrade edb-as<xx>-mysql8_fdw* mysql-community-devel
-       ```
-- For MySQL 5 on RHEL or CentOS 7:
-  ```shell
-  sudo yum -y upgrade edb-as<xx>-mysql5_fdw* mysql-community-devel
-  ```
-
-## Upgrading MySQL Foreign Data Wrapper on a Debian or Ubuntu host
-
-In the previously released version of MySQL FDW, the package name for MySQL FDW was `edb-as*-mysql-fdw`. In the current release, two separate packages have been made available for MySQL 5 and MySQL 8 i.e `edb-as*-mysql5-fdw` and `edb-as*-mysql8-fdw` Respectively. 
-
-If you are upgrading from MySQL FDW 2.5.5 to 2.6.0 for MySQL 5, then installation of `edb-as*mysql5-fdw` package for version 2.6.0 will automatically remove the previously installed package `edb-as*-mysql-fdw`.
-
-If you are upgrading from MySQL FDW 2.5.5 to 2.6.0 for MySQL 8, then before installing the `edb-as*-mysql8-fdw` package for version 2.6.0, you need to manually remove the following packages:
-- `default-mysqlclient-dev` 
-- `edb-as*-mysql-fdw`
-
-Use the following command to upgrade the FDW installation:
-- For MySQL 8: 
-  ```shell
-  apt-get upgrade edb-as<xx>-mysql8-fdw*
-  ```
-- For MySQL 5:
-  ```shell
-  apt-get upgrade edb-as<xx>-mysql5-fdw* 
-  ```
-where `xx` is the server version number.
+If you have an existing installation of MySQL Foreign Data Wrapper that you installed using the EDB repository, you can update your repository configuration file and then upgrade MySQL Foreign Data Wrapper to a more recent product version. 
+
+To perform the process, open a terminal window and enter the commands that apply to the operating system and package manager used for the installation:
+
+To update your repository configuration file:
+
+```shell
+sudo <package-manager> upgrade edb-repo
+```
+
+Where `<package-manager>` is the package manager used with your operating system:
+
+  | Package manager |         Operating system         |
+  | --------------- | -------------------------------- |
+  | dnf             | RHEL 8/9 and derivatives         |
+  | yum             | RHEL 7 and derivatives, CentOS 7 |
+  | zypper          | SLES                             |
+  | apt-get         | Debian and Ubuntu                |
+
+
+To upgrade to the latest product version, enter one of the following commands:
+
+  |         Operating system         |                                  Upgrade command                                   |
+  | -------------------------------- | ---------------------------------------------------------------------------------- |
+  | RHEL 8/9 and derivatives         | `sudo dnf -y upgrade edb-as<xx>-mysql<y>_fdw* mysql-community-devel` |
+  | RHEL 7 and derivatives, CentOS 7 | `sudo yum -y upgrade edb-as<xx>-mysql<y>_fdw* mysql-community-devel` |
+  | SLES                             | `sudo zypper -y upgrade edb-as<xx>-mysql<y>_fdw* mysql-community-devel` |
+  | Debian and Ubuntu                | `sudo apt-get upgrade edb-as<xx>-mysql<y>-fdw`                           |
+
+Where
+
+- `<package-manager>` is the package manager used with your operating system.
+
+- `<xx>` is the EDB Postgres Advanced Server version number.
+
+- `<y>` is the version of MySQL to be upgraded.