Skip to content

Commit 0bf9b99

Browse files
timwaizeneggertimwaizenegger
authored
Merge branch 'develop' into DOCS-1552--aidb-aidb-4-1-0-release-train
2 parents 5159c17 + 9b5df46 commit 0bf9b99

File tree

27 files changed

+295
-128
lines changed

27 files changed

+295
-128
lines changed

‎advocacy_docs/pg_extensions/query_advisor/rel_notes/index.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: 'EDB Query Advisor release notes'
33
navTitle: "Release notes"
44
indexCards: none
55
navigation:
6+
- query_advisor_1.2.1_rel_notes
67
- query_advisor_1.2.0_rel_notes
78
- query_advisor_1.1.1_rel_notes
89
- query_advisor_1.0.0_rel_notes
@@ -15,6 +16,7 @@ about the release that introduced the feature.
1516

1617
| Version | Release Date |
1718
|----------------------------------------|--------------|
19+
| [1.2.1](query_advisor_1.2.1_rel_notes) | 15 May 2025 |
1820
| [1.2.0](query_advisor_1.2.0_rel_notes) | 28 Feb 2025 |
1921
| [1.1.1](query_advisor_1.1.1_rel_notes) | 12 Sep 2024 |
2022
| [1.0.0](query_advisor_1.0.0_rel_notes) | 10 May 2023 |

‎advocacy_docs/pg_extensions/query_advisor/rel_notes/query_advisor_1.2.1_rel_notes.mdx

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
title: Release notes for Query Advisor version 1.2.1
3+
navTitle: "Version 1.2.1"
4+
---
5+
6+
This release of Query Advisor includes:
7+
8+
| Type | Description | Addresses |
9+
| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- |
10+
| Bug fix | Fixed an issue where index recommendations were not generated for quoted table names because table and column names were not quoted when generating index candidates. The same fix is applied to extended statistics advice. |#46551|
11+
| Bug fix | Fixed an issue where hardcoded constant values in `uniquequalid` generation caused redundant entries for semantically similar qualifications. This change ensures that `uniquequalid` is now focused on the structure of the qualification. | |

‎advocacy_docs/pg_extensions/wait_states/rel_notes/index.mdx

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: 'EDB Wait States release notes'
33
navTitle: "Release notes"
44
indexCards: none
55
navigation:
6+
- wait_states_1.5.1_rel_notes
67
- wait_states_1.5_rel_notes
78
- wait_states_1.4_rel_notes
89
- wait_states_1.3_rel_notes
@@ -11,9 +12,10 @@ navigation:
1112

1213
The EDB Wait States documentation describes the latest version of EDB Wait States, including minor releases and patches. These release notes cover what was new in each release. For new functionality introduced in a minor or patch release, there are also indicators in the content about the release that introduced the feature.
1314

14-
| Version | Release Date |
15-
| -------------------------------- | ------------ |
16-
| [1.5](wait_states_1.5_rel_notes) | 28 Feb 2025 |
17-
| [1.4](wait_states_1.4_rel_notes) | 22 Nov 2024 |
18-
| [1.3](wait_states_1.3_rel_notes) | 15 May 2024 |
19-
| [1.2](wait_states_1.2_rel_notes) | 15 Feb 2024 |
15+
| Version | Release Date |
16+
|--------------------------------------|--------------|
17+
| [1.5.1](wait_states_1.5.1_rel_notes) | 15 May 2025 |
18+
| [1.5](wait_states_1.5_rel_notes) | 28 Feb 2025 |
19+
| [1.4](wait_states_1.4_rel_notes) | 22 Nov 2024 |
20+
| [1.3](wait_states_1.3_rel_notes) | 15 May 2024 |
21+
| [1.2](wait_states_1.2_rel_notes) | 15 Feb 2024 |

‎advocacy_docs/pg_extensions/wait_states/rel_notes/wait_states_1.5.1_rel_notes.mdx

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
title: Release notes for Wait States version 1.5.1
3+
navTitle: "Version 1.5.1"
4+
---
5+
Release date: 15 May 2025
6+
7+
This release of Wait States includes:
8+
9+
| Type | Description | Addresses |
10+
|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
11+
| Bug fix | Fixed an issue where the EWS worker started during a binary upgrade, causing an unintended database connection that could interfere with the upgrade process. This fix ensures the worker does not start when the server is in binary upgrade mode. Also included .sql files in the Meson build file to support Windows builds. | #47748 |

‎advocacy_docs/supported-open-source/warehousepg/edbpggpsupp/index.mdx

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: EDB Postgres AI support for Greenplum workloads
3+
description: Covering EDB Postgres AI support for Greenplum workloads with WarehousePG.
4+
deepToc: true
5+
navigation:
6+
- installing
7+
---
8+
9+
## EDB Postgres AI support for Greenplum workloads
10+
11+
For business-critical workloads, EDB Postgres AI provides support for WarehousePG. It is ideal for organizations needing an open source based solution for their existing Greenplum workloads and mission-critical workloads needing 24/7 production-level support from technical experts.
12+
13+
This includes:
14+
15+
* Technical support:
16+
* 24x7 expert technical support for EDB Postgres AI - Support for Greenplum workloads with WarehousePG.
17+
* Software updates:
18+
* Secure software delivery
19+
* Includes distribution, maintenance, and updates.
20+
* Database and extensions:
21+
* EDB packages with binaries targeting agreed OS, architecture and version combinations.
22+
* Repository entitlement:
23+
* All packaged delivered through a dedicated EDB repository.
24+

‎advocacy_docs/supported-open-source/warehousepg/edbpggpsupp/installing.mdx

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
title: Installing EDB Postgres AI support for Greenplum workloads
3+
navTitle: Installing
4+
description: Installing EDB Postgres AI support for Greenplum workloads with WarehousePG.
5+
---
6+
7+
## Installing EDB Postgres AI support for Greenplum workloads
8+
9+
To install, you will need an EDB Subscription Token. This token is available, once logged in with your EDB account from the [EDB repositories](https://www.enterprisedb.com/repos-downloads).
10+
11+
Save the EDB Subscription token in an environment variable:
12+
13+
```bash
14+
export EDB_SUBSCRIPTION_TOKEN=<your-token>
15+
```
16+
17+
Run the following command to add the EDB repository to your system:
18+
19+
```bash
20+
curl -1sSLf "https://downloads.enterprisedb.com/$EDB_SUBSCRIPTION_TOKEN/gpsupp/setup.rpm.sh' | sudo -E bash
21+
```
22+
23+
Then install the packages according to your operating system.
24+
25+
<TabContainer>
26+
27+
<Tab title="RHEL/CentOS 9" active>
28+
<br/>
29+
30+
Only WarehousePG 7 is available for RHEL/CentOS 9.
31+
32+
```bash
33+
sudo dnf install -y warehouse-pg-7 warehouse-pg-clients whpg-backup
34+
```
35+
36+
</Tab>
37+
38+
<Tab title="RHEL/CentOS 8" active>
39+
<br/>
40+
41+
WarehousePG 6 and 7 are available for RHEL/CentOS 8.
42+
43+
<TabContainer>
44+
45+
<Tab title="WarehousePG 7" active>
46+
47+
```bash
48+
sudo dnf install -y warehouse-pg-7 warehouse-pg-clients whpg-backup
49+
```
50+
51+
</Tab>
52+
53+
<Tab title="WarehousePG 6" active>
54+
55+
```bash
56+
sudo dnf install -y warehouse-pg-6 warehouse-pg-clients whpg-backup
57+
```
58+
59+
</Tab>
60+
</TabContainer>
61+
62+
</Tab>
63+
64+
<Tab title="RHEL/CentOS 7" active>
65+
<br/>
66+
67+
Only WarehousePG 6 is available for RHEL/CentOS 7.
68+
69+
```bash
70+
sudo yum install -y warehouse-pg-6 warehouse-pg-clients whpg-backup
71+
```
72+
73+
</Tab>
74+
</TabContainer>

‎advocacy_docs/supported-open-source/warehousepg/index.mdx

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
title: WarehousePG and EDB Postgres AI support for Greenplum workloads
3+
description: Covering the open source WarehousePG and EDB Postgres AI support for Greenplum workloads with WarehousePG.
4+
navigation:
5+
- warehousepg
6+
- edbpggpsupp
7+
directoryDefaults:
8+
iconName: BigData
9+
---
10+

‎advocacy_docs/supported-open-source/warehousepg/warehousepg/index.mdx

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
title: WarehousePG
3+
description: Covering the open source WarehousePG.
4+
---
5+
6+
## Introducing WarehousePG
7+
8+
[WarehousePG](https://github.com/warehouse-pg/warehouse-pg) is a new Apache 2-licensed fork of the formerly open source Greenplum Database. It offers binary compatibility with the legacy Greenplum versions most widely deployed by customers (6.x and 7.x) — plus net-new functionality and integrations.
9+
10+
### Key features
11+
12+
* Petabytes scale with high-speed /-concurrency performance, via MPP Cluster topology with a Postgres fork based on PG 12.12.
13+
* A Master (coordinator) for query optimization and parallel plan and distribution
14+
* Multiple segments (workers) for parallel execution of queries with each segment being a Postgres instance.
15+
* High availability with standbys for the Master and mirrors for the segments.
16+
* High-speed interconnections for continuous data processing pipelining.
17+
18+
### Support
19+
20+
For business-critical workloads, EDB Postgres AI provides support for WarehousePG. See the [EDB Postgres AI support for Greenplum workloads](../edbpggpsupp/) page for more information.

‎install_template/templates/products/postgres-enterprise-manager-server/base.njk

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ For more details, see [Configuring the PEM server on Linux](../configuring_the_p
9393

9494
!!! Note
9595

96-
- The operating system user pem is created while installing the PEM server. The pem application data and the session is saved to this user's home directory.
96+
- The operating system user pem is created while installing the PEM server. The PEM application data and the session is saved to this user's home directory.
9797

9898
## Supported locales
9999

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -142,8 +142,8 @@ Use the properties in the `efm.properties` file to specify connection, administr
142142
| [log.dir](#log_dir) | | | | If not specified, defaults to '/var/log/efm-&lt;version>' |
143143
| [syslog.host](#syslog_logging) | | | localhost | |
144144
| [syslog.port](#syslog_logging) | | | 514 | |
145-
| [syslog.protocol](#syslog_logging) | | | | |
146-
| [syslog.facility](#syslog_logging) | | | UDP | |
145+
| [syslog.protocol](#syslog_logging) | | | UDP | |
146+
| [syslog.facility](#syslog_logging) | | | LOCAL1 | |
147147
| [file.log.enabled](#logtype_enabled) | Y | Y | true | |
148148
| [syslog.enabled](#logtype_enabled) | Y | Y | false | |
149149
| [jgroups.loglevel](#loglevel) | | | info | |

‎product_docs/docs/efm/5/efm_quick_start/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Using EDB Postgres Advanced Server as an example (Failover Manager also works wi
2121
- Install Failover Manager on each primary and standby node. During EDB Postgres Advanced Server installation, you configured an EDB repository on each database host. You can use the EDB repository and the `yum install` command to install Failover Manager on each node of the cluster:
2222

2323
```shell
24-
yum install edb-efm49
24+
yum install edb-efm50
2525
```
2626

2727
During the installation process, the installer creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. The example that follows creates a cluster named `efm`.

‎product_docs/docs/epas/13/epas_guide/03_database_administration/02_index_advisor/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ There are three ways to use Index Advisor to analyze SQL queries:
1818

1919
- Provide queries at the EDB-PSQL command line that you want Index Advisor to analyze.
2020

21-
- Access Index Advisor through the Postgres Enterprise Manager client. When accessed via the PEM client, Index Advisor works with SQL Profiler, providing indexing recommendations on code captured in SQL traces. For more information about using SQL Profiler with PEM, see the [Using the SQL Profiler](/pem/latest/profiling_workloads/using_sql_profiler.mdx) and [Using the Index Advisor](03_using_index_advisor.mdx).
21+
- Access Index Advisor through the Postgres Enterprise Manager client. When accessed via the PEM client, Index Advisor works with SQL Profiler, providing indexing recommendations on code captured in SQL traces. For more information about using SQL Profiler with PEM, see the [Using SQL Profiler](/pem/latest/profiling_workloads/using_sql_profiler.mdx) and [Using Index Advisor](03_using_index_advisor.mdx).
2222

2323
Index Advisor will attempt to make indexing recommendations on `INSERT`, `UPDATE`, `DELETE` and `SELECT` statements. When invoking Index Advisor, you supply the workload in the form of a set of queries (if you are providing the command in an SQL file) or an `EXPLAIN` statement (if you are specifying the SQL statement at the psql command line). Index Advisor displays the query plan and estimated execution cost for the supplied query, but does not actually execute the query.
2424

‎product_docs/docs/epas/14/epas_guide/03_database_administration/02_index_advisor/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ You can use Index Advisor to analyze SQL queries in any of these ways:
1616

1717
- Invoke the Index Advisor utility program, supplying a text file containing the SQL queries that you want to analyze. Index Advisor generates a text file with `CREATE INDEX` statements for the recommended indexes.
1818
- Provide queries at the EDB-PSQL command line that you want Index Advisor to analyze.
19-
- Access Index Advisor through the Postgres Enterprise Manager (PEM) client. When accessed using the PEM client, Index Advisor works with SQL Profiler, providing indexing recommendations on code captured in SQL traces. For more information about using SQL Profiler with PEM, see [Using the SQL Profiler](/pem/latest/profiling_workloads/using_sql_profiler.mdx) and [Using the Index Advisor](03_using_index_advisor.mdx).
19+
- Access Index Advisor through the Postgres Enterprise Manager (PEM) client. When accessed using the PEM client, Index Advisor works with SQL Profiler, providing indexing recommendations on code captured in SQL traces. For more information about using SQL Profiler with PEM, see [Using SQL Profiler](/pem/latest/profiling_workloads/using_sql_profiler.mdx) and [Using Index Advisor](03_using_index_advisor.mdx).
2020
Index Advisor attempts to make indexing recommendations on `INSERT`, `UPDATE`, `DELETE`, and `SELECT` statements. When invoking Index Advisor, you supply the workload in the form of either:
2121

2222
- If you're providing the command in an SQL file, a set of queries

‎product_docs/docs/epas/15/managing_performance/02_index_advisor/index_advisor_overview.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ You can use Index Advisor to analyze SQL queries in any of these ways:
99

1010
- Invoke the Index Advisor utility program, supplying a text file containing the SQL queries that you want to analyze. Index Advisor generates a text file with `CREATE INDEX` statements for the recommended indexes.
1111
- Provide queries at the EDB-PSQL command line that you want Index Advisor to analyze.
12-
- Access Index Advisor through the Postgres Enterprise Manager (PEM) client. When accessed using the PEM client, Index Advisor works with SQL Profiler, providing indexing recommendations on code captured in SQL traces. For more information about using SQL Profiler and Index Advisor with PEM, see [Using the SQL profiler](/pem/latest/profiling_workloads/using_sql_profiler.mdx) and [Using the Index Advisor](03_using_index_advisor.mdx).
12+
- Access Index Advisor through the Postgres Enterprise Manager (PEM) client. When accessed using the PEM client, Index Advisor works with SQL Profiler, providing indexing recommendations on code captured in SQL traces. For more information about using SQL Profiler and Index Advisor with PEM, see [Using SQL profiler](/pem/latest/profiling_workloads/using_sql_profiler.mdx) and [Using Index Advisor](03_using_index_advisor.mdx).
1313

1414
Index Advisor attempts to make indexing recommendations on `INSERT`, `UPDATE`, `DELETE`, and `SELECT` statements. When invoking Index Advisor, you supply the workload in the form of either:
1515

0 commit comments

Comments
 (0)