Skip to content

Commit 55b0418

Browse files
gvasquezvargasgvasquezvargas
authored
Merge pull request #5977 from EnterpriseDB/release/2024-08-22a
Release/2024 08 22a
2 parents 200f00c + 65f3195 commit 55b0418

File tree

8 files changed

+109
-22
lines changed

8 files changed

+109
-22
lines changed

‎product_docs/docs/efm/4/04_configuring_efm/01_cluster_properties.mdx

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -614,12 +614,12 @@ ping.server.command=/bin/ping -q -c3 -w5
614614

615615
<div id="auto_allow_hosts" class="registered_link"></div>
616616

617-
Use the `auto.allow.hosts` property to instruct the server to use the addresses specified in the `.nodes` file of the first nostarts to update the allowed host list. Enabling this property by setting `auto.allow.hosts` to `true` can simplify cluster startup.
617+
Use the `auto.allow.hosts` property to instruct the server to use the addresses specified in the `.nodes` file of the first node to start to set the allowed host list. Enabling this property by setting `auto.allow.hosts` to `true` can simplify cluster startup.
618618

619619
```ini
620-
# Have the first nostarts automatically add the addresses
621-
# from its .nodes file to the allowed host list. This will make
622-
# it faster to start the cluster when the initial set of hosts
620+
# Have the first node started automatically add the addresses from
621+
# its .nodes file to the allowed host list. This will make it
622+
# faster to start the cluster when the initial set of hosts
623623
# is already known.
624624
auto.allow.hosts=false
625625
```
@@ -1237,7 +1237,9 @@ lock.dir=
12371237

12381238
<div id="log_dir" class="registered_link"></div>
12391239

1240-
Use the `log.dir` property to specify the location to write agent log files. Failover Manager attempts to create the directory if the directory doesn't exist.
1240+
Use the `log.dir` property to specify the location to write agent log files. Failover Manager attempts to create the directory if the directory doesn't exist. The `log.dir` parameter defined in the efm.properties file determines the directory path where the EFM logs are stored. Please note that this parameter applies exclusively to the EFM logs and does not affect the logging configuration for any other components or services.
1241+
1242+
To change the startup log location for EFM, you need to modify the `runefm.sh` script located in the EFM's bin directory. Specifically, you can set the `LOG` parameter within this script to define the desired log file location.
12411243

12421244
```ini
12431245
# Specify the directory of agent logs on the node. If the path

‎product_docs/docs/epas/16/epas_rel_notes/epas16_3_0_rel_notes.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,4 +18,4 @@ EDB Postgres Advanced Server 16.3.0 includes the following enhancements and bug
1818
| Bug&nbsp;fix | Fixed an crash issue for `edbldr`. Now `edbldr` loads data into multiple tables with different encodings from the target database. | |
1919
| Bug&nbsp;fix | Fixed an issue with possible data loss and `pg_dump` failures when using rowids. | #35901 |
2020
| Bug&nbsp;fix | Fixed an issue with assertion in `DROP ROLE` statement having duplicate names. | |
21-
| Buf&nbsp;fix | Fixed server crash with `edb_dblink_oci` in left join with whole row reference. | |
21+
| Bug&nbsp;fix | Fixed server crash with `edb_dblink_oci` in left join with whole row reference. | |

‎product_docs/docs/epas/16/epas_rel_notes/epas16_4_0_rel_notes.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ EDB Postgres Advanced Server 16.4.0 includes the following enhancements and bug
1414
| Bug&nbsp;fix | Fixed an issue for EDB*Loader. Now when multiple duplicate key errors occur during the load it doesn't slow down and memory doesn't overflow. | #37017 |
1515
| Bug&nbsp;fix | Fixed an issue for replication connections. Now it correctly displays the authentication failure error message. | #101591 |
1616
| Bug&nbsp;fix | Fixed an issue for `ecpg`. Now it supports `do..while()` in Pro*C mode (`-C PROC`). | #35988 |
17-
| Bug&nbsp;fix | Fixed an issue for `edb_dblink_oci`. Now it correctly push downs `ANY` and `ALL` operators when used with scalar array. | #36220 |
17+
| Bug&nbsp;fix | Fixed an issue for `edb_dblink_oci`. Now it correctly push downs `ANY` and `ALL` operators when used with scalar array. | |
1818
| Bug&nbsp;fix | Fixed an issue for `to_number()` function. Now it correctly accepts the `"+"` sign. | #92903 |
1919
| Bug&nbsp;fix | Fixed an issue with incomplete transactions clean up after a crash. Now the incomplete transactions are cleaned up in reorder buffer after a crash. | #99636 |
20-
| Bug&nbsp;fix | Fixed an issue with `edb_dblink_oci`. Now it uses SHA256 instead of MD5 for password obfuscation. | #86497 |
20+
| Bug&nbsp;fix | Fixed an issue with `edb_dblink_oci`. Now it uses SHA256 instead of MD5 for password obfuscation. | #38240 |

‎product_docs/docs/eprs/7/05_smr_operation/08_optimizing_performance/02_optimize_sync_replication/using_bacth_lob.mdx

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
title: "Using batch synchronization for LOB objects"
3+
---
4+
5+
When synchronizing tables with LOB-type columns (with BLOB, CLOB, BYTEA etc. objects), Replication Server copies the rows by grouping 5 rows in a batch by default. This is to avoid causing out-of-memory errors when an LOB column has a large amount of data. You can customize the batch size to increase or decrease the number of rows copied in a batch.
6+
7+
To improve the performance of synchronization procedures, reduce network roundtrips and speed up data replication, you can copy rows with LOBs in larger batches. Configure larger batches only if the instance hosting the replication server has enough memory.
8+
9+
You can configure the replication of up to 1000 rows per batch.
10+
11+
!!!note
12+
Before increasing the number of rows to synchronize per batch, consider resource availability. Batch procedures increase memory consumption during replication processes.
13+
!!!
14+
15+
## Enabling batch operations on LOBs
16+
17+
### Prerequisites
18+
19+
You have upgraded your instances to a Replication Server version that includes this feature. See [Release Notes](../../../eprs_rel_notes) for an overview of the available release versions and the included enhancements.
20+
21+
### Altering the number of rows per batch
22+
23+
1. In the publication or primary server, open the `xdb_pubserver.conf` file.
24+
25+
See [Installation details](../../../installing/installation_details/#additional-details) to find out where this file is stored according to your operating system.
26+
27+
1. In the `xdb_pubserver.conf` file, look for the `syncLOBBatchSize` value.
28+
29+
1. Adapt the `syncLOBBatchSize` value according to your needs. If not uncommented already, uncomment the line to override the default. In this example, the Replication Server will synchronize 150 rows with LOB data per batch:
30+
31+
```
32+
syncLOBBatchSize=150
33+
```
34+
35+
1. Reload the configuration file as specified in [Reloading the configuration file](../../../08_xdb_cli/03_xdb_cli_commands/52_reload_conf_file).
36+
37+
Now, each time you perform a synchronization, the Replication Server will copy 150 rows with LOB objects per network roundtrip.

‎product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.9.0.mdx

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
title: "Replication Server 7.9.0 release notes"
3+
navTitle: Version 7.9.0
4+
---
5+
6+
Released: 22 Aug 2024
7+
8+
New features, enhancements, bug fixes, and other changes in Replication Server 7.9.0 include the following:
9+
10+
| Type | Description | Ticket |
11+
|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
12+
| Enhancement | EDB Postgres Replication Server now supports batch replication for Oracle CLOB and BLOB types in Synchronize mode. This significantly reduces the time required to replicate a large number of row changes containing CLOB/BLOB type columns. | #102185 <br/> #35513 |
13+
| Enhancement | The transaction commit timestamp from the origin node is now preserved when replicating to a target node. This is required to process the timestamp-based UPDATE conflicts when EDB Postgres Replication Server is used in a hybrid cluster where the EPRS Publication node is shared with EDB Postgres Distributed (PGD). | |
14+
| Bug&nbsp;fix | Fixed a corner case issue where the synchronization from the target MMR node failed to resume. | #102604 <br/> #35539 |
15+
| Bug&nbsp;fix | Fixed an issue where some of the processed entries in the `rrep_tx_monitor` table were not cleaned up. | |
16+
17+
## End-of-support notice
18+
19+
Replication Server 6.2 is no longer a supported version.
20+
21+
To ensure that your usage of Replication Server is supported, please upgrade any installations with version 6.2 to version 7. See the end-of-support notes that follow:
22+
23+
**Software:** Replication Server
24+
25+
**Version:** 6.2
26+
27+
**End of Standard Support:** June 1, 2023
28+
29+
Additional details can be found at [EDB Platform Compatibility](https://www.enterprisedb.com/resources/platform-compatibility).
30+
31+
!!! Note
32+
Version 7.x provides a non-breaking upgrade path for existing 6.2.x-based cluster deployments. However, we strongly recommend that the upgrade be verified in a staging or non-production environment before applying the upgrade in a production environment.

‎product_docs/docs/eprs/7/eprs_rel_notes/index.mdx

Lines changed: 16 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: "Release notes"
33
redirects:
44
- ../01_whats_new/
55
navigation:
6+
- eprs_rel_notes_7.9.0
67
- eprs_rel_notes_7.8.0
78
- eprs_rel_notes_7.7.0
89
- eprs_rel_notes_7.6.0
@@ -14,20 +15,21 @@ navigation:
1415

1516
The Replication Server documentation describes the latest version including minor releases and patches. The release notes in this section provide information on what was new in each release. For new functionality introduced in a minor or patch release, there are also indicators within the content about what release introduced the feature.
1617

17-
| Version | Release Date |
18-
| -------------------------------- | ------------ |
19-
| [7.8.0](eprs_rel_notes_7.8.0) | 17 May 2024 |
20-
| [7.7.0](eprs_rel_notes_7.7.0) | 14 Dec 2023 |
21-
| [7.6.0](eprs_rel_notes_7.6.0) | 07 Sep 2023 |
22-
| [7.5.1](eprs_rel_notes_7.5.1) | 26 May 2023 |
23-
| [7.5.0](eprs_rel_notes_7.5.0) | 14 Feb 2023 |
24-
| [7.4.0](eprs_rel_notes_7.4.0) | 29 Nov 2022 |
25-
| [7.3.0](15_eprs_rel_notes_7.3.0) | 15 Nov 2022 |
26-
| [7.2.1](16_eprs_rel_notes_7.2.1) | 25 Jul 2022 |
27-
| [7.2.0](17_eprs_rel_notes_7.2.0) | 24 Jun 2022 |
28-
| [7.1.0](18_eprs_rel_notes_7.1.0) | 21 Mar 2022 |
29-
| [7.0.1](19_eprs_rel_notes_7.0.1) | 03 Mar 2022 |
30-
| [7.0.0](20_eprs_rel_notes_7.0.0) | 01 Dec 2021 |
18+
| Version | Release Date |
19+
|----------------------------------|--------------|
20+
| [7.9.0](eprs_rel_notes_7.9.0) | 22 Aug 2024 |
21+
| [7.8.0](eprs_rel_notes_7.8.0) | 17 May 2024 |
22+
| [7.7.0](eprs_rel_notes_7.7.0) | 14 Dec 2023 |
23+
| [7.6.0](eprs_rel_notes_7.6.0) | 07 Sep 2023 |
24+
| [7.5.1](eprs_rel_notes_7.5.1) | 26 May 2023 |
25+
| [7.5.0](eprs_rel_notes_7.5.0) | 14 Feb 2023 |
26+
| [7.4.0](eprs_rel_notes_7.4.0) | 29 Nov 2022 |
27+
| [7.3.0](15_eprs_rel_notes_7.3.0) | 15 Nov 2022 |
28+
| [7.2.1](16_eprs_rel_notes_7.2.1) | 25 Jul 2022 |
29+
| [7.2.0](17_eprs_rel_notes_7.2.0) | 24 Jun 2022 |
30+
| [7.1.0](18_eprs_rel_notes_7.1.0) | 21 Mar 2022 |
31+
| [7.0.1](19_eprs_rel_notes_7.0.1) | 03 Mar 2022 |
32+
| [7.0.0](20_eprs_rel_notes_7.0.0) | 01 Dec 2021 |
3133

3234
## Supported upgrade paths
3335

‎product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/12310_rel_notes.mdx

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: "EDB PgBouncer 1.23.1.0 release notes"
3+
navTitle: Version 1.23.1.0
4+
---
5+
6+
Released: 22 Aug 2024
7+
8+
EDB PgBouncer 1.23.1.0 includes the following upstream merge and security fix:
9+
10+
| Type | Description |
11+
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
12+
| Upstream merge | Merged with community PgBouncer 1.23.1.0. See the community [Release Notes](https://www.pgbouncer.org/changelog.html#pgbouncer-123x) for details. |

‎product_docs/docs/pgbouncer/1/pgbouncer_rel_notes/index.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: "Release notes"
33
redirects:
44
- ../01_whats_new/
55
navigation:
6+
- 12310_rel_notes
67
- 12300_rel_notes
78
- 02_12210_rel_notes
89
- 03_12200_rel_notes
@@ -19,6 +20,7 @@ The EDB PgBouncer documentation describes the latest version of EDB PgBouncer 1,
1920

2021
| Version | Release date | Upstream merges |
2122
| ------------------------------ | ------------ | ---------------------------------------------------------------------------- |
23+
| [1.23.1.0](12310_rel_notes) | 22 Aug 2024 | Upstream [1.23.1.0](https://www.pgbouncer.org/changelog.html#pgbouncer-123x) |
2224
| [1.23.0.0](12300_rel_notes) | 01 Aug 2024 | Upstream [1.23.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-123x) |
2325
| [1.22.1.0](02_12210_rel_notes) | 16 Apr 2024 | Upstream [1.22.1.0](https://www.pgbouncer.org/changelog.html#pgbouncer-122x) |
2426
| [1.22.0.0](03_12200_rel_notes) | 29 Feb 2024 | Upstream [1.22.0.0](https://www.pgbouncer.org/changelog.html#pgbouncer-122x) |

0 commit comments

Comments
 (0)