diff --git a/product_docs/docs/pem/9/index.mdx b/product_docs/docs/pem/9/index.mdx index 7624ced8cfa..19db59efe42 100644 --- a/product_docs/docs/pem/9/index.mdx +++ b/product_docs/docs/pem/9/index.mdx @@ -78,10 +78,10 @@ PEM is a comprehensive database design and management system. PEM is designed to Supported versions of Postgres for PEM 9.x: -| |**Monitored Instance** |**Backend Instance** | -|:-----------------------------------------|:---------------------------|:---------------------| -|**EDB Postgres Advanced Server (EPAS)** |12, 13, 14, 15, 16 |12, 13, 14, 15, 16 | -|**PostgreSQL (PG)** |12, 13, 14, 15, 16 |12, 13, 14, 15, 16 | -|**EDB Postgres Extended Server (PGE)** |12, 13, 14, 15, 16 |13, 14, 15, 16[^1] | +| | **Monitored Instance** | **Backend Instance** | +|:----------------------------------------|:-----------------------|:-----------------------| +| **EDB Postgres Advanced Server (EPAS)** | 12, 13, 14, 15, 16, 17 | 12, 13, 14, 15, 16, 17 | +| **PostgreSQL (PG)** | 12, 13, 14, 15, 16, 17 | 12, 13, 14, 15, 16, 17 | +| **EDB Postgres Extended Server (PGE)** | 12, 13, 14, 15, 16, 17 | 13, 14, 15, 16, 17[^1] | [^1]: sslutils isn't available for RHEL 7 on IBM Power, so this distribution can't use PGE as a backend. diff --git a/product_docs/docs/pem/9/installing/dependencies.mdx b/product_docs/docs/pem/9/installing/dependencies.mdx index ff9555f20b5..c6ef5d43864 100644 --- a/product_docs/docs/pem/9/installing/dependencies.mdx +++ b/product_docs/docs/pem/9/installing/dependencies.mdx @@ -37,6 +37,7 @@ Python 3 and mod_wsgi (a Python module for Apache HTTPD) are required for PEM Se | RHEL 9 | x86_64 | `python39/python39-mod_wsgi` | 3.9 | `/usr/bin/python3` | | | ppc64le | `python39/python39-mod_wsgi` | 3.9 | `/usr/bin/python3` | | | s390x | `python39/python39-mod_wsgi` | 3.9 | `/usr/bin/python3` | +| | arm64 | `python39/python39-mod_wsgi` | 3.9 | `/usr/bin/python3` | | SLES 15 | x86_64 | `edb-python310/edb-python310-mod-wsgi` | 3.10 | `/usr/libexec/edb-python310/bin/python3` | | | ppc64le | `edb-python310/edb-python310-mod-wsgi` | 3.10 | `/usr/libexec/edb-python310/bin/python3` | | | s390x | `edb-python310/edb-python310-mod-wsgi` | 3.10 | `/usr/libexec/edb-python310/bin/python3` | @@ -60,6 +61,7 @@ The PEM Server and Agent require OpenSSL. | RHEL 9 | x86_64 | `openssl-3.0.7` | | | ppc64le | `openssl-3.0.7` | | | s390x | `openssl-3.0.7` | +| | arm64 | `openssl-3.0.7` | | SLES 12 | x86_64 | `openssl-1.0.2p` | | | ppc64le | `openssl-1.0.2p` | | | s390x | `openssl-1.0.2p` | diff --git a/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx new file mode 100644 index 00000000000..260a735f006 --- /dev/null +++ b/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx @@ -0,0 +1,23 @@ +--- +title: "Postgres Enterprise Manager 9.8.0 release notes" +navTitle: Version 9.8.0 +--- + +Released: 19th Nov 2024 +!!! Note +This release includes a fix for a bug that previously prevented the correct purging of historical data when the configured retention time expired. As a result, the first purge job to run after this update is expected to delete more data than usual and may take longer to complete. + +The purge job should begin within three hours of the upgrade. Additionally, after this job and the subsequent vacuuming process are finished, you may notice a significant reduction in the total size of your PEM database. +!!! + +New features, enhancements, bug fixes, and other changes in PEM 9.8.0 include: + +| Type | Description | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Enhancement | Added support for EDB Advanced Server, EDB Postgres Distributed, and PostgreSQL 17. | +| Enhancement | Added support for RHEL9 ARM64 platform. | +| Enhancement | Added support to allow sslmode connections from PEM agent to PEM server. | +| Bug fix | Fixed an issue for PEM port while registering the server. Now `pemworker` picks up the PEM port from the agent config file while registering the server. | +| Bug fix | Fixed an issue where PEM agent installation on Windows was failing if a `%` character was used to set the service for the agent. | +| Bug fix | Fixed an issue where some historical probe data was not purged because the system job that tracks data for purging would be erroneously deleted by another system job. | +| Bug fix | Fixed an issue for displaying errors on EINTR signal. Now spoolers `select()` error will be displayed on EINTR signal only when log level is set to INFO. | diff --git a/product_docs/docs/pem/9/pem_rel_notes/index.mdx b/product_docs/docs/pem/9/pem_rel_notes/index.mdx index 652a9654806..69890c99b51 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/index.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/index.mdx @@ -1,6 +1,7 @@ --- title: "Release notes" navigation: + - 980_rel_notes - 970_rel_notes - 960_rel_notes - 951_rel_notes @@ -19,22 +20,23 @@ navigation: The Postgres Enterprise Manager (PEM) documentation describes the latest version of PEM 9 including minor releases and patches. The release notes in this section provide information on what was new in each release. For new functionality introduced after 8.0.0 in a minor or patch release, there are also indicators within the content about what release introduced the feature. -| Version | Release Date | Upstream Merges | Accessibility Conformance | -| ------------------------- | ------------ | --------------------------------------------------------------------------| --------------------------------------------------------------------------------------------------- | -| [9.7.0](970_rel_notes) | 13 Aug 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.6.0](960_rel_notes) | 15 May 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.5.1](951_rel_notes) | 04 Mar 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.5.0](950_rel_notes) | 15 Feb 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.4.1](941_rel_notes) | 28 Nov 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.4.0](940_rel_notes) | 16 Nov 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.3.1](931_rel_notes) | 12 Oct 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.3.0](930_rel_notes) | 31 Aug 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.2.2](922_rel_notes) | 14 Jul 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.2.1](921_rel_notes) | 03 Jul 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.2.0](920_rel_notes) | 24 May 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.1.1](911_rel_notes) | 31 Mar 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.1.0](910_rel_notes) | 14 Feb 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.0.0](900_rel_notes) | 9 Dec 2022 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| Version | Release Date | Upstream Merges | Accessibility Conformance | +|------------------------|--------------|-----------------|------------------------------------------------------------------| +| [9.8.0](980_rel_notes) | 19 Nov 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.7.0](970_rel_notes) | 13 Aug 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.6.0](960_rel_notes) | 15 May 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.5.1](951_rel_notes) | 04 Mar 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.5.0](950_rel_notes) | 15 Feb 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.4.1](941_rel_notes) | 28 Nov 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.4.0](940_rel_notes) | 16 Nov 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.3.1](931_rel_notes) | 12 Oct 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.3.0](930_rel_notes) | 31 Aug 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.2.2](922_rel_notes) | 14 Jul 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.2.1](921_rel_notes) | 03 Jul 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.2.0](920_rel_notes) | 24 May 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.1.1](911_rel_notes) | 31 Mar 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.1.0](910_rel_notes) | 14 Feb 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.0.0](900_rel_notes) | 9 Dec 2022 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | Often only select issues are included in the upstream merges. The specific issues included in the merges are listed in the release note topics. diff --git a/product_docs/docs/pem/9/registering_agent.mdx b/product_docs/docs/pem/9/registering_agent.mdx index 73d558b884a..3c617e4f678 100644 --- a/product_docs/docs/pem/9/registering_agent.mdx +++ b/product_docs/docs/pem/9/registering_agent.mdx @@ -44,26 +44,27 @@ set PEM_SERVER_PASSWORD=edb ./pemworker.exe REGISTER ``` -| Option | Description | -|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| `--pem-server` | The IP address of the PEM backend database server. This parameter is required. | -| `--pem-port` | The port of the PEM backend database server. The default value is `5432`. | -| `--pem-user` | The name of the database user having superuser privileges of the PEM backend database server. This parameter is required. | -| `--pem-agent-user` | The agent user to connect the PEM server backend database server. | -| `--cert-path` | The complete path to the directory where certificates are created. If you don't provide a path, certificates are created in `~/.pem` on Linux and `%APPDATA%/pem` on Windows. | -| `--config-dir` | The directory path for the configuration file. The default is `/../etc`. | -| `--display-name` | A user-friendly name for the agent to display in the PEM browser tree. In PEM 9.6 and later, the default is the host's fully qualified domain name (FQDN), falling back to the hostname if this option isn't set. For releases earlier than PEM 9.6, the default is the hostname. | -| `--force-registration` | Include the `force_registration` clause to register the agent with the arguments provided. This clause is useful if you're overriding an existing agent configuration. The default value is `Yes`. | -| `--group` | The name of the group in which the agent is displayed. | -| `--team` | The name of the database role on the PEM backend database server with access to the monitored database server. | -| `--owner` | The name of the database user on the PEM backend database server who owns the agent. | -| `--allow_server_restart` | Enable the `allow_server_restart` parameter to allow PEM to restart the monitored server. The default value is `True`. | -| `--allow-batch-probes` | Enable the `allow-batch-probes` parameter to allow PEM to run batch probes on this agent. The default value is `False`. | -| `--batch-script-user` | The operating system user to use for executing the batch/shell scripts. The default value is none. The scripts don't execute if you leave this parameter blank or the specified user doesn't exist. | -| `--enable-heartbeat-connection` | Enable the `enable-heartbeat-connection` parameter to create a dedicated heartbeat connection between the PEM agent and server to update the active status. The default value is `False`. | -| `--enable-smtp` | Enable the `enable-smtp parameter` to allow the PEM agent to send the email on behalf of the PEM server. The default value is `False`. | -| `--enable-snmp` | Enable the `enable-snmp parameter` to allow the PEM agent to send the SNMP traps on behalf of the PEM server. The default value is `False`. | -| `-o` | Specifies whether you want to override the configuration file options. | +| Option | Description | +|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| `--pem-server` | The IP address of the PEM backend database server. This parameter is required. | +| `--pem-port` | The port of the PEM backend database server. The default value is `5432`. | +| `--pem-user` | The name of the database user having superuser privileges of the PEM backend database server. This parameter is required. | +| `--pem-agent-user` | The agent user to connect the PEM server backend database server. | +| `--pem-ssl-mode` | Type of SSL authentication used for connecting PEM agent to the PEM server. The possible values are `prefer`, `require`,`disable`,`verify-CA`, and `verify-full`. | +| `--cert-path` | The complete path to the directory where certificates are created. If you don't provide a path, certificates are created in `~/.pem` on Linux and `%APPDATA%/pem` on Windows. | +| `--config-dir` | The directory path for the configuration file. The default is `/../etc`. | +| `--display-name` | A user-friendly name for the agent to display in the PEM browser tree. In PEM 9.6 and later, the default is the host's fully qualified domain name (FQDN), falling back to the hostname if this option isn't set. For releases earlier than PEM 9.6, the default is the hostname. | +| `--force-registration` | Include the `force_registration` clause to register the agent with the arguments provided. This clause is useful if you're overriding an existing agent configuration. The default value is `Yes`. | +| `--group` | The name of the group in which the agent is displayed. | +| `--team` | The name of the database role on the PEM backend database server with access to the monitored database server. | +| `--owner` | The name of the database user on the PEM backend database server who owns the agent. | +| `--allow_server_restart` | Enable the `allow_server_restart` parameter to allow PEM to restart the monitored server. The default value is `True`. | +| `--allow-batch-probes` | Enable the `allow-batch-probes` parameter to allow PEM to run batch probes on this agent. The default value is `False`. | +| `--batch-script-user` | The operating system user to use for executing the batch/shell scripts. The default value is none. The scripts don't execute if you leave this parameter blank or the specified user doesn't exist. | +| `--enable-heartbeat-connection` | Enable the `enable-heartbeat-connection` parameter to create a dedicated heartbeat connection between the PEM agent and server to update the active status. The default value is `False`. | +| `--enable-smtp` | Enable the `enable-smtp parameter` to allow the PEM agent to send the email on behalf of the PEM server. The default value is `False`. | +| `--enable-snmp` | Enable the `enable-snmp parameter` to allow the PEM agent to send the SNMP traps on behalf of the PEM server. The default value is `False`. | +| `-o` | Specifies whether you want to override the configuration file options. | !!! Note Allowing the agent to restart the database server If you use any feature of PEM that requires a database server restart by the PEM agent (such as Audit Manager, Log Manager, or the Tuning Wizard), then you must set the value of `allow_server_restart` to `true` in the `agent.cfg` file or restart the server manually for changes to take effect.