Skip to content

Commit

Permalink
Merge pull request #5718 from EnterpriseDB/docs/pgd/fix/relnotes551po…
Browse files Browse the repository at this point in the history 
…streview
  • Loading branch information
@djw-m
djw-m authored May 31, 2024
2 parents c978059 + 95e79a0 commit 084a375
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions product_docs/docs/pgd/5/rel_notes/pgd_5.4.1_rel_notes.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.<hr/>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 | <details><summary>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.</summary><hr/>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. </details>| |



4 changes: 2 additions & 2 deletions product_docs/docs/pgd/5/rel_notes/pgd_5.5.1_rel_notes.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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 | <details><summary>Fix a data inconsistency issue with mixed version usage during upgrades</summary>Upgrading 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.</details> | |
| BDR | 5.5.1 | <details><summary>Disabled auto-triggering of node sync by default</summary>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)).</details> | 11510 |
| BDR | 5.5.1 | <details><summary>Fix potential data inconsistency issue with mixed version usage during a rolling upgrade</summary><hr/>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.<br/>This release addresses a backward compatibility issue in mixed version operation, enabling seamless rolling upgrades.</details> | |
| BDR | 5.5.1 | <details><summary>Disabled auto-triggering of node sync by default</summary><hr/>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)).</details> | 11510 |


1 comment on commit 084a375

@github-actions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉 Published on https://edb-docs-staging.netlify.app as production
🚀 Deployed on https://665aaec58484c0fb87e44f01--edb-docs-staging.netlify.app

Please sign in to comment.