Merge pull request #5091 from EnterpriseDB/release/2023-12-14

Release: 2023-12-14
EnterpriseDB · Dec 14, 2023 · 153ce5c · 153ce5c · github-actions · Dec 14, 2023
2 parents acd0103 + 9eb81da
commit 153ce5c
Show file tree

Hide file tree

Showing 13 changed files with 51 additions and 79 deletions.
diff --git a/install_template/config.yaml b/install_template/config.yaml
@@ -961,9 +961,6 @@ products:
       - name: Debian 11
         arch: x86_64
         supported versions: [7]
-      - name: Ubuntu 18.04
-        arch: x86_64
-        supported versions: [7]
       - name: Ubuntu 20.04
         arch: x86_64
         supported versions: [7]

diff --git a/install_template/templates/products/replication-server/index.njk b/install_template/templates/products/replication-server/index.njk
@@ -25,5 +25,5 @@ redirects:
 
 {% block otherosinstall %}
 ## Windows
-- [Windows Server 2019](windows)
+- [Windows Server 2022](windows), [Windows Server 2019](windows)
 {% endblock otherosinstall %}
diff --git a/product_docs/docs/biganimal/release/overview/05_database_version_policy.mdx b/product_docs/docs/biganimal/release/overview/05_database_version_policy.mdx
@@ -34,7 +34,7 @@ BigAnimal will automatically upgrade your Postgres 11 instances to a later versi
 | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- |
 | BigAnimal no longer supports version 11.                                                                                                                                                                                                                                                                                                           | November 20, 2023   |
 | The PostgreSQL community plans to deprecate PostgreSQL 11 and won't provide any security patches after this date.                                                                                                                                                                                                                                  | November 9, 2023    |
-| Start upgrading your BigAnimal instances to a later major version starting on this date. You can use pg_dump to restore your cluster into a later version.                                                                                    | now to May 20, 2023 |
+| Start upgrading your BigAnimal instances to a later major version starting on this date. You can use pg_dump to restore your cluster into a later version.                                                                                    | May 20, 2023 |
 | You can't create a new instance with PostgreSQL major version 11 in the BigAnimal interfaces after this date.                                                                                                                                                                                                                                      | May 20, 2023        |
 | If you manually restore a cluster, you can't restore it with Postgres 11 after this date. You will need to restore that Postgres 11 cluster into a newer version of Postgres, for example, PostgreSQL version 15.                                                                                                                       | May 20, 2023        |
 | BigAnimal will force a major version upgrade and won't allow any new clusters to be provisioned or restored to version 11 even for customers previously using version 11. Only customers on Extended Life Support are exempt for the duration of their contract. If you don’t purchase Extended Life Support on this date, your clusters will be upgraded. | April 20, 2024      |

diff --git a/product_docs/docs/efm/4/efm_quick_start/index.mdx b/product_docs/docs/efm/4/efm_quick_start/index.mdx
@@ -21,7 +21,7 @@ Using EDB Postgres Advanced Server as an example (Failover Manager also works wi
 -   Install Failover Manager on each primary and standby node. During EDB Postgres Advanced Server installation, you configured an EDB repository on each database host. You can use the EDB repository and the `yum install` command to install Failover Manager on each node of the cluster:
 
     ```shell
-    yum install edb-efm47
+    yum install edb-efm48
     ```
 
 During the installation process, the installer creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. The example that follows creates a cluster named `efm`.

diff --git a/product_docs/docs/eprs/7/01_introduction/03_certified_supported_versions.mdx b/product_docs/docs/eprs/7/01_introduction/03_certified_supported_versions.mdx
@@ -4,17 +4,19 @@ title: "Certified and supported product versions"
 
 You can use the following database product versions with Replication Server:
 
--   PostgreSQL versions 11, 12, 13, 14, and 15
--   EDB Postgres Advanced Server versions 11, 12, 13, 14, and 15
+-   PostgreSQL versions 12, 13, 14, 15, and 16
+-   EDB Postgres Advanced Server versions 12, 13, 14, 15, and 16
 -   Oracle 11g Release 2 version 11.2.0.2.0 is explicitly certified. Newer minor versions in the 11.2 line are supported as well.
 -   Oracle 12c version 12.1.0.2.0 is explicitly certified. Newer minor versions in the 12.1 line are supported as well.
 -   Oracle 18c version 18.1.0.2.0 is explicitly certified. Newer minor versions in the 18.1 line are supported as well.
 -   Oracle 19c version 19.1.0.2.0 is explicitly certified. Newer minor versions in the 19.1 line are supported as well.
 -   SQL Server 2014 version 12.0.5000.0 is explicitly certified. Newer minor versions in the 12.0 line are supported as well.
 
 !!!Note
-   All PostgreSQL and EDB Postgres Advanced Server versions available as BigAnimal single-node and primary/standby high-availability cluster types are also supported for SMR configurations. See the BigAnimal (EDB’s managed database cloud service) [documentation](/biganimal/latest) for more information about BigAnimal’s [supported cluster types](/biganimal/latest/overview/02_high_availability/). See the [database version policy documentation](/biganimal/latest/overview/05_database_version_policy/) for the versions of PostgreSQL and EDB Postgres Advanced Server available in BigAnimal.
+All PostgreSQL and EDB Postgres Advanced Server versions available as BigAnimal single-node and primary/standby high-availability cluster types are also supported for SMR configurations. See the BigAnimal (EDB’s managed database cloud service) [documentation](/biganimal/latest) for more information about BigAnimal’s [supported cluster types](/biganimal/latest/overview/02_high_availability/). See the [database version policy documentation](/biganimal/latest/overview/05_database_version_policy/) for the versions of PostgreSQL and EDB Postgres Advanced Server available in BigAnimal.
 
+EDB Postgres Distributed (PGD) v5.3.0 is explicitly certified as a Publishing database for trigger mode and as Subscription database for both trigger and wal modes.
+!!!
 
 As of Replication Server 7.1.0:
 - SQL Server 2016 version 13.00.5026 is explicitly certified. Newer minor versions in the 13.0 line are supported as well.

diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.7.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.7.0.mdx
@@ -0,0 +1,31 @@
+---
+title: "Replication Server 7.7.0 release notes"
+navTitle: Version 7.7.0
+---
+
+Released: 14 Dec 2023
+
+New features, enhancements, bug fixes, and other changes in Replication Server 7.7.0 include the following:
+
+|    Type     |                                                                                              Description                                                                                               |
+| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Enhancement | Implemented CPU and memory usage related optimizations specifically applicable for publications with a large number of tables. [Support ticket #91588 #94343]                                          |
+| Enhancement | EDB Postgres Replication Server is now certified to use EDB Postgres Distributed (PGD) v5.3.0 as a publishing database for trigger mode and as a subscription database for both trigger and wal modes. |
+| Enhancement | EDB Replication Server is now certified for use on Windows Server 2022.                                                                                                                                |
+| Bug fix     | Fixed memory issues observed for a multi-master setup with a fairly heavy load resulting in the Replication Server restart. [Support ticket #91588]                                                    |
+| Bug fix     | Fixed the null pointer exception observed for an edge case when a publication table is truncated and immediately removed from the publication.  [Support ticket #96054]                                |
+| Bug fix     | Fixed an issue where the synchronize operation failed to replicate a table with a `BIGINT` value greater than integer range. [Support ticket #99264]                                                   |
+| Bug fix     | Fixed an issue where triggers manually configured by users on the target PostgreSQL or EDB Postgres Advanced Server databases are disabled during a data snapshot. [Support ticket #97637]             |
+
+## End-of-Support notice
+
+We recommend you update to the most recent software version. *If you have not yet updated to the most current version, please see the end-of-support notes below*: 
+
+Software: Replication Server 
+Version: 6.2
+End of Standard Support: June 1, 2023
+
+Additional details can be found at [EDB Platform Compatibility](https://www.enterprisedb.com/resources/platform-compatibility).
+
+!!! Note
+    Version 7.x provides a non-breaking upgrade path for existing 6.2.x-based cluster deployments; however, we strongly recommend that the upgrade be verified in a staging or non-production environment before applying the upgrade in a production environment.
diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx
@@ -3,6 +3,7 @@ title: "Release notes"
 redirects:
   - ../01_whats_new/
 navigation:
+ - eprs_rel_notes_7.7.0
  - eprs_rel_notes_7.6.0
  - eprs_rel_notes_7.5.1
  - eprs_rel_notes_7.5.0
@@ -14,6 +15,7 @@ The Replication Server documentation describes the latest version including mino
 
 | Version                          | Release Date | 
 | -------------------------------- | ------------ |
+| [7.7.0](eprs_rel_notes_7.7.0)    | 14 Dec 2023 |
 | [7.6.0](eprs_rel_notes_7.6.0)    | 07 Sep 2023 |
 | [7.5.1](eprs_rel_notes_7.5.1)    | 26 May 2023 |
 | [7.5.0](eprs_rel_notes_7.5.0)    | 14 Feb 2023 |

diff --git a/product_docs/docs/eprs/7/installing/index.mdx b/product_docs/docs/eprs/7/installing/index.mdx
@@ -44,7 +44,7 @@ Select a link to access the applicable installation instructions:
 
 ### Debian and derivatives
 
-- [Ubuntu 22.04](linux_x86_64/eprs_ubuntu_22), [Ubuntu 20.04](linux_x86_64/eprs_ubuntu_20), [Ubuntu 18.04](linux_x86_64/eprs_ubuntu_18)
+- [Ubuntu 22.04](linux_x86_64/eprs_ubuntu_22), [Ubuntu 20.04](linux_x86_64/eprs_ubuntu_20)
 
 - [Debian 11](linux_x86_64/eprs_debian_11), [Debian 10](linux_x86_64/eprs_debian_10)
 
@@ -60,4 +60,4 @@ Select a link to access the applicable installation instructions:
 
 ## Windows
 
-- [Windows Server 2019](windows)
+- [Windows Server 2022](windows), [Windows Server 2019](windows)
diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_ubuntu_18.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_ubuntu_18.mdx
diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/index.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/index.mdx
@@ -64,8 +64,6 @@ Operating system-specific install instructions are described in the correspondin
 
 - [Ubuntu 20.04](eprs_ubuntu_20)
 
-- [Ubuntu 18.04](eprs_ubuntu_18)
-
 - [Debian 11](eprs_debian_11)
 
 - [Debian 10](eprs_debian_10)
diff --git a/product_docs/docs/eprs/7/installing/windows.mdx b/product_docs/docs/eprs/7/installing/windows.mdx
@@ -19,7 +19,10 @@ EDB provides a graphical interactive installer for Windows. You can access it tw
 
 - You must have Java Runtime Environment (JRE) version 1.8 or later installed on the hosts where you intend to install any Replication Server component (Replication Console, publication server, or subscription server). You can use Any Java product, such as Oracle Java or OpenJDK. Follow the directions for your host operating system to install the Java runtime environment.
 
-- Be sure the system environment variable, `JAVA_HOME`, is set to the JRE installation directory of the JRE version and bitness (32-bit or 64-bit) you want to use with Replication Server. The Replication Server installer for a Windows platform contains both the 32-bit and 64-bit versions. The `JAVA_HOME` setting determines whether the 32-bit or the 64-bit version of Replication Server is installed. If `JAVA_HOME` isn't set, the first JRE version encountered in the `path` system environment variable determines the Replication Server version to be installed.
+- Be sure the system environment variable, `JAVA_HOME`, is set to the JRE installation directory of the JRE version you want to use with Replication Server. Please ensure that 64-bit version of JRE is installed and `JAVA_HOME` is set before installing Replication Server.
+
+!!! Note
+Replication Server doesn't support JRE installations with 32-bit.
 
 
 ## Installing directly

diff --git a/product_docs/docs/eprs/7/supported_platforms.mdx b/product_docs/docs/eprs/7/supported_platforms.mdx
@@ -19,7 +19,8 @@ Replication Server is certified to work with the following Java platforms:
 | PPCLE RHEL 8               | Red Hat OpenJDK 8                                                   |
 | PPCLE RHEL 9               | Red Hat OpenJDK 11                                                  |
 | Windows Server 2019        | Red Hat OpenJDK 8                                                   |
+| Windows Server 2022        | Oracle JDK 8                                                        |
 | Debian 10 and 11           | Red Hat OpenJDK 11                                                  |
-| Ubuntu 18, 20, 22          | OpenJDK 11                                                          |
+| Ubuntu 20, 22          | OpenJDK 11                                                          |
 
 See [Product Compatibility](https://www.enterprisedb.com/platform-compatibility#eprs) for more information on operating system support.
diff --git a/product_docs/docs/pgd/5/postgres-configuration.mdx b/product_docs/docs/pgd/5/postgres-configuration.mdx
@@ -17,8 +17,8 @@ To run correctly, PGD requires these Postgres settings:
 -   `wal_level` &mdash; Must be set to `logical`, since PGD relies on logical decoding.
 -   `shared_preload_libraries` &mdash; Must include `bdr` to enable the extension. Most other
      extensions can appear before of after the bdr entry in the comma-separated list. One exception
-     to that is `pgaudit` which must appear in the list before `bdr`. Also, do not include 
-     `pglogical` in this list
+     to that is `pgaudit`, which must appear in the list before `bdr`. Also, don't include 
+     `pglogical` in this list.
 -   `track_commit_timestamp` &mdash; Must be set to `on` for conflict resolution to
     retrieve the timestamp for each conflicting row.