You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/releases/4.4.0.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,6 +104,7 @@ When mounted to the container, the connection `sslmode` that the replication use
104
104
- Bring up the correct number of pgBouncer replicas when `pgo update cluster --startup` is issued.
105
105
- Fixed issue where `pgo scale` would not work after `pgo update cluster --shutdown` and `pgo update cluster --startup` were run.
106
106
- Ensure `pgo scaledown` deletes external WAL volumes from the replica that is removed.
107
+
- Fix for PostgreSQL cluster startup logic when performing a restore.
107
108
- Several fixes for selecting default storage configurations and sizes when using the `pgo-deployer` container. These include #1, #4, and #8.
108
109
- Do not consider non-running Pods as primary Pods when checking for multiple primaries (Reported by @djcooklup).
109
110
- Fix race condition that could occur while `pgo upgrade` was running while a HA configuration map attempted to sync. (Reported by Paul Heinen @v3nturetheworld).
0 commit comments