From 95e79a07ba020f0536724f443645fb75bf3eaeeb Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Fri, 31 May 2024 17:40:21 +0100 Subject: [PATCH] Fixes from PM review Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/rel_notes/pgd_5.4.1_rel_notes.mdx | 4 ++-- product_docs/docs/pgd/5/rel_notes/pgd_5.5.1_rel_notes.mdx | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.4.1_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.4.1_rel_notes.mdx index 0eda5e3fdce..45e49e64f6f 100644 --- a/product_docs/docs/pgd/5/rel_notes/pgd_5.4.1_rel_notes.mdx +++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.4.1_rel_notes.mdx @@ -14,9 +14,9 @@ We recommend that all users of PGD 5 upgrade to PGD 5.4.1. See [PGD/TPA upgrades ## Bug fixes -| Component | Version | Description | Addresses | +| Component | Version | Description | Tickets | |-----------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| -| BDR | 5.4.1 | Fixed WAL retention logic: prevent a PGD node from running out of disk space due to a bug in 5.4.0 in combination with Postgres 16, PGE 16, and EPAS 16.
We now make sure WAL gets properly cleaned even after 4 GB of WAL produced on a node. A change in 5.4.0 caused WAL to be retained forever after that point. This issue affects only release PGD 5.4.0 in combination with Postgres 16, PGE 16, and EPAS 16. | | +| BDR | 5.4.1 |
Fixed WAL retention logic to prevent disk space issues on a PGD node with version 5.4.0 and Postgres 16, PGE 16, and EPAS 16.
A fix has been implemented to ensure proper cleanup of Write-Ahead Logs (WAL) even after reaching a size of 4 GB on a node. A change in version 5.4.0 resulted in WAL being retained indefinitely after reaching this threshold. This issue is specific to PGD 5.4.0 in conjunction with Postgres 16, PGE 16, and EPAS 16.
| | diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.5.1_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.5.1_rel_notes.mdx index b8940b60046..eee123638ff 100644 --- a/product_docs/docs/pgd/5/rel_notes/pgd_5.5.1_rel_notes.mdx +++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.5.1_rel_notes.mdx @@ -16,7 +16,7 @@ We recommend that all users of PGD 5 upgrade to PGD 5.5.1. See [PGD/TPA upgrades | Component | Version | Description | Ticket | |-----------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| -| BDR | 5.5.1 |
Fix a data inconsistency issue with mixed version usage during upgradesUpgrading from any previous PGD version to PGD 5.5.0 may result in inconsistencies when replicating from the newer PGD 5.5.0 node to an older version PGD node. This release fixes mixed version operation to allow for smooth rolling upgrades.
| | -| BDR | 5.5.1 |
Disabled auto-triggering of node sync by defaultAutomatically triggered synchronization of data from a down node caused issues by failing to resume once it came back up. As a precautionary measure, the feature is now disabled by default (PGD setting [`bdr.enable_auto_sync_reconcile`](/pgd/latest/reference/pgd-settings#bdrenable_auto_sync_reconcile)).
| 11510 | +| BDR | 5.5.1 |
Fix potential data inconsistency issue with mixed version usage during a rolling upgrade
Backward incompatible change in PGD 5.5.0 may lead to inconsistencies when replicating from a newer PGD 5.5.0 node to an older version of the PGD node, specifically during the mixed mode rolling upgrade.
This release addresses a backward compatibility issue in mixed version operation, enabling seamless rolling upgrades.
| | +| BDR | 5.5.1 |
Disabled auto-triggering of node sync by default
Automatically triggered synchronization of data from a down node caused issues by failing to resume once it came back up. As a precautionary measure, the feature is now disabled by default (PGD setting [`bdr.enable_auto_sync_reconcile`](/pgd/latest/reference/pgd-settings#bdrenable_auto_sync_reconcile)).
| 11510 |