Merge pull request #5468 from EnterpriseDB/release-2024-04-03b

Release: 2024-04-03b

advocacy_docs/pg_extensions/pg_squeeze/using.mdx

@@ -3,9 +3,34 @@ title: Using pg_squeeze
 navTitle: Using
 ---
 
+Use `pg_squeeze` to remove unused space from a table and optionally sort tuples according to a particular index.
+
+## Understanding lock levels while using `pg_squeeze`
+
+While using `pg_squeeze`, the extension performs a series of actions, and some of these actions place a lock on the squeezed table, as described in the following steps. The table being squeezed is available for both read and write operations by other transactions most of the time. 
+
+When squeezing a table, the extension:
+
+1. Creates a transient table and copies the contents of the source table using the snapshot.
+
+    `pg_squeeze` holds an `ACCESS SHARE` lock on the source table during this step. 
+
+1. Builds indexes on the transient table.
+
+    `pg_squeeze` holds an `ACCESS SHARE` lock on the source table during this step. 
+
+1. Decodes and applies the concurrent changes that occurred on the source table while the initial load is in progress.
+
+1. Applies any concurrent changes that take place while waiting for the lock and swaps the storage of the transient and the source table.
+
+    `pg_squeeze` holds an `ACCESS EXCLUSIVE` lock for a short period during this step.
+
+1. Drops the transient table.
+
+
 ## Registering a table for regular processing
 
-First, ensure that your table has either a primary key or a unique constraint. This is necessary to process changes resulting from other transactions  while `pg_squeeze` is doing its work.
+Before using `pg_squeeze`, ensure that your table has either a primary key or a replica identity. This is necessary to process changes resulting from other transactions  while `pg_squeeze` is doing its work.
 
 To make the `pg_squeeze` extension aware of the table, you must insert a record into the `squeeze.tables` table. After it is added, table statistics are checked periodically. When the table meets the necessary criteria to be squeezed, a task is added to a queue. The tasks are processed sequentially, in the order they are created.
 

product_docs/docs/pgd/5/rel_notes/index.mdx

@@ -2,6 +2,7 @@
 title: "EDB Postgres Distributed Release notes"
 navTitle: "Release notes"
 navigation:
+- pgd_5.4.1_rel_notes
 - pgd_5.4.0_rel_notes
 - pgd_5.3.0_rel_notes
 - pgd_5.2.0_rel_notes
@@ -22,6 +23,7 @@ that introduced the feature.
 
 | Release Date  |   EDB Postgres Distributed   | BDR extension | PGD CLI | PGD Proxy |
 | ------------- | ---------------------------- | ------------- | ------- | --------- |
+| 03 Apr 2024  | [5.4.1](pgd_5.4.1_rel_notes) | 5.4.1         | 5.4.0   | 5.4.0     |
 | 05 Mar 2024  | [5.4.0](pgd_5.4.0_rel_notes) | 5.4.0         | 5.4.0   | 5.4.0     |
 | 14 Nov 2023  | [5.3.0](pgd_5.3.0_rel_notes) | 5.3.0         | 5.3.0   | 5.3.0     |
 | 04 Aug 2023   | [5.2.0](pgd_5.2.0_rel_notes) | 5.2.0         | 5.2.0   | 5.2.0     |

product_docs/docs/pgd/5/rel_notes/pgd_5.4.1_rel_notes.mdx

@@ -0,0 +1,21 @@
+---
+title: "EDB Postgres Distributed 5.4.1 release notes"
+navTitle: "Version 5.4.1"
+---
+
+Released: 03 Apr 2024
+
+EDB Postgres Distributed version 5.4.1 is a minor version bug-fix release of EDB Postgres Distributed.
+
+!!! Important Recommended upgrade
+We recommend that all users of PGD 5 upgrade to PGD 5.4.1. See [PGD/TPA upgrades](../upgrades/tpa_overview) for details.
+!!!
+
+
+## Bug fixes
+
+| Component | Version | Description                                                                                                                                                                                                                                                                                                     | Addresses        |
+|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|
+| 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.<br/><br/>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.                                                |                  |
+
+