Skip to content

Commit 0b6ecb3

Browse files
robert-stringerrobert-stringer
authored
Merge pull request #1280 from EnterpriseDB/pem_7.16_enterprise_features_guide
Updated the content of PEM 7.16 Enterprise Features guide Former-commit-id: 302f3e9
2 parents e96ca06 + 95d49e9 commit 0b6ecb3

8 files changed

+83
-199
lines changed

‎product_docs/docs/pem/7.16/pem_ent_feat/01_what's_new.mdx

Lines changed: 17 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -2,20 +2,21 @@
22
title: "What's New"
33
---
44

5-
The following changes have been made to Postgres Enterprise Manager to create version 8.0.1:
5+
The following features have been added to Postgres Enterprise Manager 7.16:
66

7-
Improved the overall performance, usability, and stability of the product by:
8-
9-
- Allowing the dash (-) character in the superuser name that is provided during configuration.
10-
- Gracefully closing the operating system resources during batch probe and command execution to avoid errors.
11-
- Improved support for unicode string handling in pemAgent.
12-
- Fixed a regression restoring BART backup when agent is not bound with the BART server.
13-
- In addition to the above-listed items, a few other minor bugs have also been fixed.
14-
15-
PEM 8.0.1 provides an option to hide or unhide the Dashboard, Statistics, Dependents, and Dependencies tabs.
16-
17-
Features and Functionalities removed in recent versions of PEM:
18-
19-
- PEM 8.0 and later is not supported on CentOS/RHEL 6.x.
20-
- EDB ARK UI Management is not supported by PEM 7.16 and later.
21-
- PEM 7.16 and later is not supported on Internet explorer version 11 and lesser.
7+
- **Enhanced BART Integration**: You can now automate the cleanup of obsolete backups, allow incremental backups from a parent backup in a `tar.gz` format, and manage the BART scanner via the PEM Console.
8+
- **Enhanced EFM Integration**: You can now perform cluster switchover and monitor cluster property values such as `missingnodes`, `minimumstandbys` and `membershipcoordinators` for a Failover Manager cluster via the PEM Console.
9+
- **Auto-discovery of server clusters on Debian Platforms**: You can now quickly locate the database servers that reside on the monitored system.
10+
- **Extended the REST API on alerts states for agents, servers, and databases**: PEM has now exposed endpoints to:
11+
- Current threshold alert violations
12+
- State change history on available alerts for agent, server, and database.
13+
- Current state of all agents and monitored servers.
14+
- **Other features and changes include**:
15+
- You can use the same agent-id on agent registration using `--force-registration` and regenerate the certificates.
16+
- Documentation now includes information about defining and monitoring Postgres instances on `AWS EC2` and `RDS`.
17+
- The `Query Tool` now provides SQL Formatter support.
18+
- The `Query Tool` toolbar now has a button to provide easy access to a new query tool window.
19+
- The modified `Schema diff` tool will now compare two databases instead of two schemas.
20+
- Added High Contrast (Beta) theme support.
21+
- A warning now alerts the user when connecting to a server version that is no longer supported.
22+
- The management user interface for EDB Ark is no longer distributed with PEM.

‎product_docs/docs/pem/7.16/pem_ent_feat/02_pem_query_tool.mdx

Lines changed: 9 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ Hover over an icon to display a tool-tip that describes the icon's functionality
4646
| `Stop` | Click the `Stop` icon to cancel the execution of the currently running query. | Accesskey + Q |
4747
| `Execute/Refresh` | Click the `Execute/Refresh` icon to either execute or refresh the query highlighted in the SQL editor panel. Click the down arrow to access other execution options:<br/>- Add a check next to `Auto-Rollback` to instruct the server to automatically roll back a transaction if an error occurs during the transaction.<br/>- Add a check next to `Auto-Commit` to instruct the server to automatically commit each transaction. Any changes made by the transaction will be visible to others, and durable in the event of a crash. | F5 |
4848
| `Explain` | Click the `Explain` icon to view an explanation plan for the current query. The result of EXPLAIN is displayed graphically on the `Explain` tab of the output panel, and in text form on the `Data Output` tab. | F7 |
49-
| `Explain analyze` | Click the `Explain analyze` icon to invoke an EXPLAIN ANALYZE command on the current query.Navigate through the Explain Options menu to select options for the EXPLAIN command:<br/>- Select `Verbose` to display additional information regarding the query plan.<br/> - Select `Costs` to include information on the estimated startup and total cost of each plan node, as well as the estimated number of rows and the estimated width of each row.<br/>- Select `Buffers` to include information on buffer usage.<br/>- Select `Timing` to include information about the startup time and the amount of time spent in each node of the query.<br/>- Select `Summary` to include the summary information about the query plan. | |
49+
| `Explain analyze` | Click the `Explain analyze` icon to invoke an EXPLAIN ANALYZE command on the current query.Navigate through the Explain Options menu to select options for the EXPLAIN command:<br/>- Select `Verbose` to display additional information regarding the query plan.<br/> - Select `Costs` to include information on the estimated startup and total cost of each plan node, as well as the estimated number of rows and the estimated width of each row.<br/>- Select `Buffers` to include information on buffer usage.<br/>- Select `Timing` to include information about the startup time and the amount of time spent in each node of the query.<br/>- Select `Summary` to include the summary information about the query plan. | Shift+F7 |
5050
| `Commit` | Click the `Commit` icon to commit the transaction. | Shift+CTRL+M |
5151
| `Rollback` | Click the `Rollback` icon to rollback the transaction. | Shift+CTRL+R |
5252
| `Clear` | Use options on the `Clear` drop-down menu to erase display contents:<br/>- Select `Clear Query Window` to erase the content of the SQL Editor panel.<br/>- Select `Clear History` to erase the content of the `History` tab. | Accesskey + L |
@@ -146,19 +146,19 @@ The `Analysis` tab shows the plan details in table format, it generates a format
146146

147147
If the percentage of the exclusive/inclusive timings of the total query time is:
148148

149-
Greater than 90 --> Red
149+
- Greater than 90 --> Red
150150

151-
Greater than 50 --> Orange (between red and yellow)
151+
- Greater than 50 --> Orange (between red and yellow)
152152

153-
Greater than 10 --> Yellow
153+
- Greater than 10 --> Yellow
154154

155155
If the planner has misestimated the number of rows (actual vs planned) by:
156156

157-
10 times --> Yellow color
157+
- 10 times --> Yellow color
158158

159-
100 times --> Orange (between Red and Yellow) color
159+
- 100 times --> Orange (between Red and Yellow) color
160160

161-
1000 times --> Red color
161+
- 1000 times --> Red color
162162

163163
![Query Tool - Explain tab - Analysis tab](../images/query_explain_analyze_table.png)
164164

@@ -187,7 +187,7 @@ Use the `Notifications` tab to view details of the asynchronous notifications th
187187

188188
![Query Tool - Output Notifications tab](../images/query_output_notifications.png)
189189

190-
You can see details such as recorded time of the asynchronous notification event, name of the event or channel, process ID of the client process that has sent the notification, and the payload string that might have been sent along with the notification.
190+
You can see details such as the recorded time of the asynchronous notification event, the name of the event or channel, the process ID of the client process that has sent the notification, and the payload string that might have been sent along with the notification.
191191

192192
## Query History Panel
193193

@@ -214,30 +214,4 @@ Query history is maintained across sessions for each database on a per-user basi
214214

215215
Use the `Connection status` feature to view the current connection and transaction status by clicking on the status icon in query tool:
216216

217-
![Query Tool - Connection Status button](../images/query_tool_connection_status.png)
218-
219-
## Macros
220-
221-
Query Tool Macros enable you to execute pre-defined SQL queries with a single key press. Pre-defined queries can contain the placeholder $SELECTION$. Upon macro execution, the placeholder will be replaced with the currently selected text in the Query Editor pane of the Query Tool.
222-
223-
![Query Tool - Connection Status button](../images/query_tool_manage_macros.png)
224-
225-
To create a macro, select the *Manage Macros* option from the *Macros* menu on the *Query Tool*. Select the key you wish to use, enter the name of the macro, and the query, optionally including the selection placeholder, and then click the *Save* button to store the macro.
226-
227-
![Query Tool - Connection Status button](../images/query_tool_manage_macros_dialog.png)
228-
229-
To clear a macro, select the macro on the *Manage Macros* dialogue, and then click the *Clear* button.
230-
231-
![Query Tool - Connection Status button](../images/query_tool_macros_clear_row.png)
232-
233-
The server will prompt you for confirmation to clear the macro.
234-
235-
![Query Tool - Connection Status button](../images/query_tool_macros_clear_confirmation.png)
236-
237-
To clear all macros, click on the *Clear* button on left side of the key. The server will prompt you for confirmation to clear all the rows.
238-
239-
![Query Tool - Connection Status button](../images/query_tool_macros_clear_all.png)
240-
241-
To execute a macro, simply select the appropriate shortcut keys, or select it from the *Macros* menu.
242-
243-
![Query Tool - Connection Status button](../images/query_tool_macros_execution.png)
217+
![Query Tool - Connection Status button](../images/query_tool_connection_status.png)

0 commit comments

Comments
 (0)