Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release: 2024-11-27a #6310

Closed
wants to merge 6 commits into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: "EDB*Plus 41.3.0 release notes"
navTitle: Version 41.3.0
---

Released: 27 Nov 2024

New features, enhancements, bug fixes, and other changes in EDB\*Plus 41.3.0 include:

| Type | Description | Addresses |
|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
| Enhancement | EDB\*Plus has been certified for use with EDB Postgres Advanced Server version 17. | |
| Enhancement | Enhanced the behavior where the `SET LINESIZE` command doesn't behave as expected when set to a value greater than 10. This enhancement mainly applies to the constants used in the select statement. | #103591 <br/> #35673 |
| Bug&nbsp;fix | Corrected the behavior where `SPOOL` was introducing redundant blank lines after each output. | #37846 |
| Bug&nbsp;fix | Fixed the issue where EDB\*Plus is unable to process the command when `--` is used in between `/* */`. | #100496 |
| Bug&nbsp;fix | Fixed the issue causing the execution of a trivial procedural script to perform quite slowly in EDB\*Plus. | #37747 |
| Bug&nbsp;fix | Fixed an issue related to the configuration of EDB\*Plus with SSL certificate authentication method when the password is not specified. | #37970 |
6 changes: 4 additions & 2 deletions product_docs/docs/edb_plus/41/02_release_notes/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
title: "Release notes"

navigation:
- edbplus_41.3_rel_notes
- edbplus_41.2_rel_notes
- edbplus_41.1_rel_notes
- edbplus_41.0_rel_notes
Expand All @@ -11,8 +12,9 @@ EDB\*Plus is a utility program that provides a command line interface to EDB Pos

The EDB\*Plus documentation describes the latest version of EDB\*Plus Version 41. The release notes provide information on what was new in each release.

| Version | Release Date |
| ------------------------------------- | ------------ |
| Version | Release Date |
|--------------------------------------|--------------|
| [41.3.0](edbplus_41.3_rel_notes.mdx) | 27 Nov 2024 |
| [41.2.0](edbplus_41.2_rel_notes.mdx) | 23 Aug 2023 |
| [41.1.0](edbplus_41.1_rel_notes.mdx) | 20 Apr 2023 |
| [41.0.0](edbplus_41.0_rel_notes.mdx) | 14 Feb 2023 |
4 changes: 2 additions & 2 deletions product_docs/docs/edb_plus/41/02a_supported_platforms.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,8 @@ EDB\*Plus is supported on the same platforms as EDB Postgres Advanced Server. To
## Supported database versions

The following list of EDB Postgres Advanced Server (EPAS) versions are currently supported for use with EDB\*Plus:
- EPAS 17
- EPAS 16
- EPAS 15
- EPAS 14
- EPAS 13
- EPAS 12
- EPAS 11
14 changes: 7 additions & 7 deletions product_docs/docs/edb_plus/41/04_using_edb_plus.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -78,9 +78,9 @@ The following example shows user `enterprisedb` with password `password` connect

```text
C:\Program Files\edb\edbplus>edbplus enterprisedb/password
Connected to EnterpriseDB 14.1.0 (localhost:5444/edb) AS enterprisedb
Connected to EnterpriseDB 16.4.1 (localhost:5444/edb) AS enterprisedb

EDB*Plus: Release 14 (Build 40.0.0)
EDB*Plus: (Build 41.3.0)
Copyright (c) 2008-2021, EnterpriseDB Corporation. All rights reserved.

SQL>
Expand All @@ -90,9 +90,9 @@ The following example shows user `enterprisedb` with password `password` connect

```text
C:\Program Files\edb\edbplus>edbplus enterprisedb/password@localhost:5445/edb
Connected to EnterpriseDB 14.1.0 (localhost:5445/edb) AS enterprisedb
Connected to EnterpriseDB 16.4.1 (localhost:5445/edb) AS enterprisedb

EDB*Plus: Release 14 (Build 40.0.0)
EDB*Plus: (Build 41.3.0)
Copyright (c) 2008-2021, EnterpriseDB Corporation. All rights reserved.

SQL>
Expand All @@ -102,9 +102,9 @@ Using variable `hr_5445` in the `login.sql` file, the following shows how it is

```text
C:\Program Files\edb\edbplus>edbplus enterprisedb/password@hr_5445
Connected to EnterpriseDB 14.0.0 (localhost:5445/hr) AS enterprisedb
Connected to EnterpriseDB 16.4.1 (localhost:5445/hr) AS enterprisedb

EDB*Plus: Release 14 (Build 40.1.0)
EDB*Plus: (Build 41.3.0)
Copyright (c) 2008-2021, EnterpriseDB Corporation. All rights reserved.

SQL>
Expand All @@ -127,7 +127,7 @@ The following example executes a script file, `dept_query.sql`, after connecting

```sql
C:\Program Files\edb\edbplus>edbplus enterprisedb/password @dept_query
Connected to EnterpriseDB 14.1.0 (localhost:5444/edb) AS enterprisedb
Connected to EnterpriseDB 16.4.1 (localhost:5444/edb) AS enterprisedb

SQL> SELECT * FROM dept;

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -284,9 +284,9 @@ $ export PGSSLCERTPASS=keypass
$ export PGSSLKEYPASS=exppass
$ cd /usr/edb/edbplus
$ ./edbplus.sh enterprisedb/[email protected]:5444/edb?ssl=true
Connected to EnterpriseDB 14.0.0 (192.168.2.22:5444/edb) AS enterprisedb
Connected to EnterpriseDB 16.4.1 (192.168.2.22:5444/edb) AS enterprisedb

EDB*Plus: Release 14 (Build 40.0.1)
EDB*Plus: (Build 41.3.0)
Copyright (c) 2008-2021, EnterpriseDB Corporation. All rights reserved.

SQL>
Expand All @@ -301,9 +301,9 @@ $ export PGSSLCERTPASS=keypass
$ export PGSSLKEYPASS=exppass
$ cd /usr/edb/edbplus
$ ./edbplus.sh enterprisedb/[email protected]:5444/edb?ssl=true
Connected to EnterpriseDB 14.0.0 (192.168.2.22:5444/edb) AS enterprisedb
Connected to EnterpriseDB 16.4.1 (192.168.2.22:5444/edb) AS enterprisedb

EDB*Plus: Release 14 (Build 40.0.1)
EDB*Plus: (Build 41.3.0)
Copyright (c) 2008-2021, EnterpriseDB Corporation. All rights reserved.

SQL>
Expand Down
6 changes: 3 additions & 3 deletions product_docs/docs/edb_plus/41/06_command_summary.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -320,23 +320,23 @@ In this example, the database connection is changed to database `edb` on the loc
```sql
SQL> CONNECT smith/mypassword@localhost:5445/edb
Disconnected from EnterpriseDB Database.
Connected to EnterpriseDB 14.0.0 (localhost:5445/edb) AS smith
Connected to EnterpriseDB 16.4.1 (localhost:5445/edb) AS smith
```

In this session, the connection is changed to the username `enterprisedb`. The host defaults to the localhost, the port defaults to `5444` (which isn't the same as the port previously used), and the database defaults to `edb`.

```sql
SQL> CONNECT enterprisedb/password
Disconnected from EnterpriseDB Database.
Connected to EnterpriseDB 14.0.0 (localhost:5444/edb) AS enterprisedb
Connected to EnterpriseDB 16.4.1 (localhost:5444/edb) AS enterprisedb
```

This example shows connectivity for a multi-node cluster (one primary node and two secondary nodes) setup. The given multi-host `connectstring` syntax is used to establish a connection with the active primary database server. In this case, using `CONNECT` command, the connection is established with the primary database node on host `192.168.22.24` at port `5444`.

```sql
SQL> CONNECT enterprisedb/[email protected]:5444,192.168.22.25:5445,192.168.22.26:5446/edb?targetServerType=primary
Disconnected from EnterpriseDB Database.
Connected to EnterpriseDB 15.3.0 (192.168.22.24:5444/edb) AS enterprisedb
Connected to EnterpriseDB 16.4.1 (192.168.22.24:5444/edb) AS enterprisedb
```

## DEFINE
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -9,25 +9,14 @@ The EDB JDBC connector provides connectivity between a Java application and an E

New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.7.3.2 include:

| Type | Description
|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Performance | Improved parsing performance with large SQL (MTK/SQL Plus). |
| Enhancement | Added support for EDB Postgres Advanced Server 17.2. |
| Bug fix | Fixes an incompatibility issue with JDK 8 that found in version 42.7.3.1 of the `edb-jdbc18` driver. |
| Fix | edb-jdbc installation should not install a lower JDK version when a higher version is installed. |
| Fix | Fixed issue where `Message.getJMSMessageID()` returns `null`. |
| Fix | Fixed issue with determining the queue table for a queue when there is more than one queue defined within a single schema. |
| Fix | Fixed issue where EDBJmsMessageConsumer.receiveNoWait() always returns null even when messages are available on the queue.
| Fix | Fixed issue where EDBJmsMessageConsuder() [without time parameter] is supposed to block until a message is available. |












| Type | Description |
|-------------|----------------------------------------------------------------------------------------------------------------------------|
| Performance | Improved parsing performance with large SQL (MTK/SQL Plus). |
| Enhancement | Added support for EDB Postgres Advanced Server 17.2. |
| Bug fix | Fixes an incompatibility issue with JDK 8 that was found in version 42.7.3.1 of the `edb-jdbc18` driver. |
| Bug Fix | `edb-jdbc` installation should not install a lower JDK version when a higher version is installed. |
| Bug Fix | Fixed issue where `Message.getJMSMessageID()` returns `null`. |
| Bug Fix | Fixed issue with determining the queue table for a queue when there is more than one queue defined within a single schema. |
| Bug Fix | Fixed issue where `EDBJmsMessageConsumer.receiveNoWait()` returns `null` even when messages are available on the queue. |
| Bug Fix | Fixed issue where `EDBJmsMessageConsumer.receive()` [without time parameter] fails to block until a message is available. |
| Bug Fix | Fixed issue where `EDBJmsMessageConsumer.receive(timeout)` doesn't honor the timeout specified. |
11 changes: 5 additions & 6 deletions product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ If the <code>nodename</code> parameter is NULL, the function will wait for all n
LSN. If the <code>target</code> LSN is NULL, it will wait for the current <code>wal_flush_lsn</code>.</p>
</details></td><td></td></tr>
<tr><td>BDR</td><td>5.6.1</td><td><details><summary>Improvements made in SO Node Management and Progress Tracking.</summary><hr/><p>An update addresses the movement of group slots in SO nodes, ensuring they don't appear as peers in
progress updates. Improvements include enhanced watermark management for SO leaders in the Himesh
progress updates. Improvements include enhanced watermark management for SO leaders in the Optimized Topology
configuration, where write leaders now include watermarks in their updates. Watermarks are broadcasted
to simplify progress tracking on idle clusters. The peer progress mapping for SO nodes has been corrected,
and the tap test for group slot movement has been revised.
Expand Down Expand Up @@ -72,13 +72,12 @@ that are prone to failure won't consistently impact the success of other tasks.<
<tr><td>BDR</td><td>5.6.1</td><td><details><summary>Fixed parting subscription with standbys.</summary><hr/><p>The parting subscription used to hang, failing to wait for standbys when the
bdr.standby_slot_names parameter was defined.</p>
</details></td><td>41821</td></tr>
<tr><td>BDR</td><td>5.6.1</td><td><details><summary>Fixed parting SO node with multiple origins.</summary><hr/><p>All relevant origins must be removed when parting SO node
With himesh, parting an SO node should result in removing all origins it
<tr><td>BDR</td><td>5.6.1</td><td><details><summary>Fixed parting SO node with multiple origins.</summary><hr/><p>All relevant origins must be removed when parting SO node.
With Optimized Topology, parting an SO node should result in removing all origins it
has, not just the one related to its SO group leader.
When parting a data node, even though there is no subscription to it
from SO node, the origin should be removed
DO not make SO node target of a part catchup subscription when himesh
enabled</p>
from SO node, the origin should be removed.
DO not make SO node target of a part catchup subscription when Optimized Topology is enabled.</p>
</details></td><td></td></tr>
<tr><td>BDR</td><td>5.6.1</td><td><details><summary>Stopped creation of slots for subscriber only nodes on witness nodes.</summary><hr/><p>Subscriber only nodes should not have slots on witness nodes.</p>
</details></td><td></td></tr>
Expand Down
11 changes: 5 additions & 6 deletions product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,7 @@ relnotes:
component_version: 5.6.1
details: |
An update addresses the movement of group slots in SO nodes, ensuring they don't appear as peers in
progress updates. Improvements include enhanced watermark management for SO leaders in the Himesh
progress updates. Improvements include enhanced watermark management for SO leaders in the Optimized Topology
configuration, where write leaders now include watermarks in their updates. Watermarks are broadcasted
to simplify progress tracking on idle clusters. The peer progress mapping for SO nodes has been corrected,
and the tap test for group slot movement has been revised.
Expand All @@ -130,13 +130,12 @@ relnotes:
component: BDR
component_version: 5.6.1
details: |
All relevant origins must be removed when parting SO node
With himesh, parting an SO node should result in removing all origins it
All relevant origins must be removed when parting SO node.
With Optimized Topology, parting an SO node should result in removing all origins it
has, not just the one related to its SO group leader.
When parting a data node, even though there is no subscription to it
from SO node, the origin should be removed
DO not make SO node target of a part catchup subscription when himesh
enabled
from SO node, the origin should be removed.
DO not make SO node target of a part catchup subscription when Optimized Topology is enabled.
jira: BDR-5552
addresses: ""
type: Bug-fix
Expand Down
Loading