Skip to content

Commit

Permalink
Merge pull request #5382 from EnterpriseDB/release/2024-03-13a
Browse files Browse the repository at this point in the history 
Release/2024-03-13a
  • Loading branch information
@gvasquezvargas
gvasquezvargas authored Mar 13, 2024
2 parents 3925373 + 556c582 commit 5a4586e
Show file tree
Hide file tree
Showing 9 changed files with 104 additions and 53 deletions.
14 changes: 7 additions & 7 deletions product_docs/docs/lasso/4/release-notes.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,13 +10,13 @@ Lasso Version 4.14.0 includes the following enhancements and bug fixes:

| Type | Description | Addresses |
|-----------------|-------------|-----------|
| Feature | Collect device mapper (`dm-X`) mappings for `iostat` on non-container instances. | DC-970 |
| Improvement | Change message about the lock file detected | DC-974 |
| Bug fix | Fix issue on lock file removal for some exception cases | DC-947 |
| Bug fix | Fix detection issue on non-Redwood instances, for `SYS.ALL_PART_*` relations | DC-973 |
| Bug fix | Remove the `tools/pem` directory when there is no PEM agent service | DC-859 |
| Doc improvement | Requirements for running Lasso on Windows Server | DC-250 |
| Doc improvement | Clarification related to the usage of `libpq` and `.pgpass` | DC-292 |
| Feature | Lasso now collects device mapper (`dm-X`) mappings for `iostat` on non-container instances. | DC-970 |
| Improvement | Changed message about the lock file detected. | DC-974 |
| Bug fix | Fixed issue on lock file removal for some exception cases. | DC-947 |
| Bug fix | Fixed detection issue on non-Redwood instances for `SYS.ALL_PART_*` relations. | DC-973 |
| Bug fix | Removed the `tools/pem` directory when there's no PEM agent service. | DC-859 |
| Doc improvement | Added requirements for running Lasso on Windows Server. | DC-250 |
| Doc improvement | Added clarification related to the usage of `libpq` and `.pgpass`. | DC-292 |


## Lasso - Version 4.13.0
Expand Down
6 changes: 3 additions & 3 deletions product_docs/docs/lasso/4/report-types.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -42,13 +42,13 @@ gathered with:
```

If a password is required, it's a common practice to create a `~/.pgpass`
file for the `postgres` or `enterprisedb` operating system user. You can
file for the postgres or enterprisedb operating system user. You can
find more details about the `.pgpass` file [in the PostgreSQL
documentation](https://www.postgresql.org/docs/current/libpq-pgpass.html).
As Lasso connects to the database using `libpq`, then Lasso will use the
As Lasso connects to the database using `libpq`, then Lasso uses the
`.pgpass` file as appropriate.

If the `.pgpass` file is not found or a corresponding entry for the
If the `.pgpass` file isn't found or a corresponding entry for the
database connection doesn't exist in the `.pgpass` file, then Lasso
prompts for a password. Alternatively, you can specify a password using
the `PGPASSWORD` environment variable:
Expand Down
12 changes: 12 additions & 0 deletions product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/03_12200_rel_notes.mdx
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
---
title: "EDB PgBouncer 1.22.0.0 release notes"
navTitle: Version 1.22.0.0
---

Released: 29 Feb 2024

EDB PgBouncer 1.22.0.0 includes the following upstream merge and security fix:

| Type | Description |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Upstream merge | Merged with community PgBouncer 1.22.0.0. See the community [Release Notes](https://www.pgbouncer.org/changelog.html#pgbouncer-122x) for details. |
1 change: 1 addition & 0 deletions product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/index.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ The EDB PgBouncer documentation describes the latest version of EDB PgBouncer 1,

| Version | Release date | Upstream merges |
| ------------------------------ | ------------ | ---------------------------------------------------------------------------- |
| [1.22.0.0](04_12200_rel_notes) | 29 Feb 2024 | Upstream [1.22.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-122x) |
| [1.21.0.0](04_12100_rel_notes) | 16 Oct 2023 | Upstream [1.21.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-121x) |
| [1.20.0.0](05_12000_rel_notes) | 09 Aug 2023 | Upstream [1.20.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-120x) |
| [1.19.0.0](06_11900_rel_notes) | 07 Jun 2023 | Upstream [1.19.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-119x) |
Expand Down
27 changes: 15 additions & 12 deletions product_docs/docs/pgbouncer/1/supported_platforms.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8,18 +8,21 @@ The EDB PgBouncer is supported on the same platforms as EDB Postgres Advanced Se

This table lists the latest EDB PgBouncer versions and their supported corresponding EDB Postgres Advanced Server (EPAS) versions.

| EDB PgBouncer | EPAS 15 | EPAS 14 | EPAS 13 | EPAS 12 | EPAS 11 |
| ------------- | ------- | ------- | ------- | ------- | ------- |
| 1.19 | Y | Y | Y | Y | Y |
| 1.18 | Y | Y | Y | Y | Y |
| 1.17 | N | Y | Y | Y | Y |
| 1.16 | N | Y | Y | Y | Y |
| 1.15 | N | N | Y | Y | Y |
| 1.14 | N | N | Y | Y | Y |
| 1.13 | N | N | N | Y | N |
| 1.12 | N | N | N | Y | N |
| 1.9 | N | N | N | N | Y |
| 1.7 | N | N | N | N | N |
| EDB PgBouncer | EPAS 16 | EPAS 15 | EPAS 14 | EPAS 13 | EPAS 12 |
| ------------- | ------- | ------- | ------- | ------- | ------- |
| 1.22 | Y | Y | Y | Y | Y |
| 1.21 | Y | Y | Y | Y | Y |
| 1.20 | Y | Y | Y | Y | Y |
| 1.19 | Y | Y | Y | Y | Y |
| 1.18 | Y | Y | Y | Y | Y |
| 1.17 | N | N | Y | Y | Y |
| 1.16 | N | N | Y | Y | Y |
| 1.15 | N | N | N | Y | Y |
| 1.14 | N | N | N | Y | Y |
| 1.13 | N | N | N | N | Y |
| 1.12 | N | N | N | N | Y |
| 1.9 | N | N | N | N | N |
| 1.7 | N | N | N | N | N |


The documented and supported functionality of each version of EDB PgBouncer is the same. The information in this documentation applies to all supported versions of EDB PgBouncer.
36 changes: 23 additions & 13 deletions product_docs/docs/pgd/5/upgrades/tpa_overview.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3,28 +3,32 @@ title: Upgrading PGD clusters with TPA
---

!!! Note No Postgres major version upgrades
TPA doesn't currently support major version upgrades of Postgres. The techniques outlined here can perform minor version upgrades of the PGD software and minor version upgrades of Postgres. To perform a major version upgrade of Postgres, see [In-place Postgres major version upgrades](bdr_pg_upgrade).
TPA doesn't currently support major version upgrades of Postgres.

To perform a major version upgrade of Postgres, see [In-place Postgres major version upgrades](bdr_pg_upgrade).
!!!

If you used TPA to install your cluster, you can also use TPA to upgrade your cluster. You can read more, in detail, about the capabilities of TPA upgrades in [Upgrading your cluster](/tpa/latest/tpaexec-upgrade/) in the TPA documentation.
If you used TPA to install your cluster, you can also use TPA to upgrade it. The techniques outlined here can perform minor and major version upgrades of the PGD software. They can also perform minor version upgrades of Postgres.

You can read more about the capabilities of TPA upgrades in [Upgrading your cluster](/tpa/latest/tpaexec-upgrade/) in the TPA documentation.

!!! Warning Always test first
If possible, always test upgrade processes in a QA environment first to ensure there are no unexpected factors to be taken into account. TPA's ability to reproducibly deploy a PGD configuration makes it much easier to build a test environment to work with.
If possible, always test upgrade processes in a QA environment first. This should help ensure that there are no unexpected factors that should be taken into account. TPA's ability to reproducibly deploy a PGD configuration makes it much easier to build a test environment to work with.
!!!

## Minor and major PGD upgrades

Minor version upgrades of PGD are managed automatically
TPA automatically manages minor version upgrades of PGD.

Major version upgrades of PGD will require changes to the TPA `config.yml` file which contains the deployment configuration.
Major version upgrades of PGD require changes to the TPA `config.yml` file, which contains the deployment configuration.

If you are upgrading to PGD 5, from previous PGD major versions, you will be able to use [`tpaexec reconfigure`](/tpa/latest/reference/tpaexec-reconfigure/) to help you make appropriate modifications to your deployment configuration.
When upgrading to PGD 5 from previous PGD major versions, you can use [`tpaexec reconfigure`](/tpa/latest/reference/tpaexec-reconfigure/). This command helps you make appropriate modifications to your deployment configuration.

The `reconfigure` command will require settings for architecture (only `PGD_Always_ON` and PGD Proxy routing to run. Remember to back up your deployment configuration before running, and use the `--describe` and `--output` options to preview the reconfiguration.
The `reconfigure` command requires settings for architecture (only `PGD_Always_ON` and PGD Proxy routing to run. Remember to back up your deployment configuration before running, and use the `--describe` and `--output` options to preview the reconfiguration.

## Pre-requisites

* The cluster configuration directory that was created when TPA deployed your PGD cluster.
* The cluster configuration directory created when TPA deployed your PGD cluster.

* If performing a major version upgrade of PGD, ensure that `tpaexec reconfigure` has been run and [appropriate configuration changes](#minor-and-major-pgd-upgrades) have been made.

Expand All @@ -39,17 +43,23 @@ tpaexec upgrade clustername

Where **clustername** is the name of the cluster and the path to the cluster configuration directory. By default, TPA will upgrade each node of the cluster to the latest minor versions of the software the nodes were configured with.

!!! Note TPA's automated rolling upgrade procedure

TPA will test first the cluster then the nodes. Each node will then be isolated from the cluster, upgraded and then returned to operation within the cluster.
## TPA's automated rolling upgrade procedure

TPA first tests the cluster and then the nodes.

Each node is then isolated from the cluster, upgraded, and returned to operation within the cluster.

### TPA upgrades - step by step

* Checks that all preconditions for upgrading the cluster are met.
* For each instance in the cluster, checks that it has the correct repositories configured and that the required postgres packages are available in them.
* For each instance in the cluster
* Checks that it has the correct repositories configured
* Check that the required Postgres packages are available in those repositories.
* For each BDR node in the cluster, one at a time:
* Fences the node off to ensure that pgd-proxy doesn't send any connections to it.
* Stops, updates, and restarts postgres.
* Stops, updates, and restarts Postgres.
* Unfences the node so it can receive connections again.
* Updates pgbouncer, pgd-proxy, and pgd-cli, as applicable for this node.

!!!

13 changes: 13 additions & 0 deletions product_docs/docs/pgpool/4/pgpool_rel_notes/444_rel_notes.mdx
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
title: "EDB PgPool-II 4.4.4 release notes"
navTitle: Version 4.4.4
---

Released: 26 Feb 2024

EDB Pgpool-II 4.4.4 includes the following upstream merge:

| Type | Description |
|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
| Upstream merge | Merged with community Pgpool-II 4.4.4. See the community [Release Notes](https://www.pgpool.net/docs/latest/en/html/release-4-4-4.html) for details. |
| Bug fix | Fixed an issue for JDBC application, where it was throwing an error while doing prepare for call() statement with load balancing feature enabled. |
2 changes: 2 additions & 0 deletions product_docs/docs/pgpool/4/pgpool_rel_notes/index.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ title: "Release notes"
redirects:
- ../01_whats_new/
navigation:
- 444_rel_notes
- 443_rel_notes
- 442_rel_notes
- 07_432_rel_notes
Expand All @@ -19,6 +20,7 @@ The EDB Pgpool-II documentation describes the latest version of EDB Pgpool-II, i

| Version | Release Date | Upstream merges | |
| ------------------------------------------------------------------------------------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- |
| [4.4.4](444_rel_notes) | 26 Feb 2024 | Upstream [4.4.4](https://www.pgpool.net/docs/44/en/html/release-4-4-4.html) | |
| [4.4.3](443_rel_notes) | 09 Nov 2023 | Upstream [4.4.3](https://www.pgpool.net/docs/44/en/html/release-4-4-3.html) | |
| [4.4.2](442_rel_notes) | 14 Feb 2023 | Upstream [4.4.2](https://www.pgpool.net/docs/44/en/html/release-4-4-2.html) | |
| [4.3.2](07_432_rel_notes), [4.2.9](429_rel_notes), [4.1.12](4112_rel_notes), [4.0.19](4019_rel_notes), [3.7.24](3724_rel_notes) | 05 Jul 2022 | Upstream [4.3.2](https://www.pgpool.net/docs/43/en/html/release-4-3-2.html#bug-fixes), [4.2.9](https://www.pgpool.net/docs/43/en/html/release-4-2-9.html#bug-fixes), [4.1.12](https://www.pgpool.net/docs/43/en/html/release-4-1-12.html#bug-fixes), [4.0.19](https://www.pgpool.net/docs/43/en/html/release-4-0-19.html#bug-fixes), [3.7.24](https://www.pgpool.net/docs/43/en/html/release-3-7-24.html#bug-fixes) | |
Expand Down
Loading

1 comment on commit 5a4586e

@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.netlify.app as production
🚀 Deployed on https://65f181bc90c57bc8a4796172--edb-docs.netlify.app

Please sign in to comment.