Minimum Requirements
The minimum requirements for installing PostgreSYS components may vary depending on the desired workload or the technical and organizational needs of each environment and project.
However, to meet the minimum requirements of production environments, we suggest:
| Service | Component | CPU | RAM | Disk | Comments |
|---|---|---|---|---|---|
| Orchestration | PgSmart CLI | 1 GHZ Dual Core | 512 MB | 100 MB | |
| PgSmart Web | 2 GHZ Dual Core | 2 GB | 1 GB | ||
| PgSmart Agent | 1 GHZ Dual Core | 512 MB | 100 MB | ||
| Database | PostgreSQL | 1 GHZ Dual Core | 4 GB 1 | 2 GB | Recommended CPU with 4 or more cores. |
| PostGIS | 1 GHZ Dual Core | 1 GB 2 | 100 MB | ||
| Connection Pool | PgBouncer | 1 GHZ Dual Core | 1 GB 3 | 100 MB | |
| Backup Management | pgBackRest | 1 GHZ Dual Core | 512 MB | 100 MB | Consider resizing computational resources when using WAL-E and WAL-G. |
| High Availability | Patroni 4 | 1 GHZ Dual Core | 2 GB | 100 MB | |
| etcd | 2 GHZ Dual Core | 2 GB 5 | 100 MB | SSD disks are recommended. | |
| HAProxy | 1GHZ Dual Core | 1 GB 6 | 100 MB | ||
| Observability | Prometheus | 1 GHZ Dual Core | 4 GB | - | SSD disks are recommended. |
| Prometheus Exporter | 1 GHz Dual Core | 512 MB | - | ||
| Grafana | 2 GHZ Dual Core | 2 GB | 1 GB | For installation and logs. | |
| Alertmanager | 1 GHZ Dual Core | 2 GB | - | ||
| Karma | 1 GHz Dual Core | 1 GB | - |
Up to 5 GB of free disk space is required to download the installation packages. If needed, request support at the Área de Suporte.
Recommendations
Although the distribution of services changes according to available resources, the desired level of isolation and availability, and the performance requirements of each environment, here are some recommendations that can be observed as general guidelines.
| Service | Component | Recomendations |
|---|---|---|
| Database | PostgreSQL | Whenever possible, use a dedicated host for this component. |
| Backup | pgBackRest | Whenever possible, use a dedicated host for this component. If this component is installed on the same host as the database service component, it is recommended to use separate disks for backup storage. |
| High Availability (HA) | Patroni | It must be installed on the host(s) of the database instance(s).. |
| High Availability (HA) | etcd | In production, it must be installed on at least 3 distinct and, if possible, dedicated hosts. Additionally, an odd number of members in the etcd cluster is recommended. Since this component uses the Raft consensus algorithm, which relies on a majority of votes (quorum) to elect a leader and apply changes to the cluster, having an odd number maximizes fault tolerance with the fewest possible nodes. |
| High Availability (HA) | HAProxy | It is recommended that this component be installed on a dedicated. |
| Connections Pool | PgBouncer | The host where PgBouncer will be installed depends on the desired architecture. In a common scenario, it is recommended to install it on a dedicated host or together with the Database to reduce network latency. However, in HA environments, it can be installed alongside the Proxy component to achieve better performance. |
| Observability | Prometheus | Whenever possible, use a dedicated host for this component. |
| Observability | Grafana | Whenever possible, use a dedicated host for this component. Otherwise, preferably place it on the same server as Prometheus. |
| Observability | Alertmanager | Whenever possible, use a dedicated host for this component. Otherwise, preferably place it on the same server as Prometheus. |
| Observability | Karma | Whenever possible, use a dedicated host for this component. Otherwise, preferably place it on the same server as Prometheus. |
We emphasize that each environment is unique and should be assessed individually for proper configuration.
Supported Operating Systems
PostgreSYS is available for the following operating systems:
| PostgreSYS | Operating System | Version | Architecture |
|---|---|---|---|
| 4.1 | CentOS | 8.x | x86-64 |
| 4.1 | CentOS | 9.x | x86-64 |
| 4.1 | Red Hat Enterprise Linux | 8.x | x86-64 |
| 4.1 | Red Hat Enterprise Linux | 9.x | x86-64 |
| 4.1 | Oracle Linux | 8.x | x86-64 |
| 4.1 | Oracle Linux | 9.x | x86-64 |
| 4.1 | Rocky Linux | 8.x | x86-64 |
| 4.1 | Rocky Linux | 9.x | x86-64 |
| 4.1 | AlmaLinux | 8.x | x86-64 |
| 4.1 | AlmaLinux | 9.x | x86-64 |
| 4.1 | Amazon Linux | 2023 | x86-64 |
| 4.1 | SUSE Linux Enterprise Server | 15.6 | x86-64 |
| 4.1 | openSUSE | 15.6 | x86-64 |
| 4.1 | Ubuntu | 20.04 | x86-64 |
| 4.1 | Ubuntu | 22.04 | x86-64 |
| 4.1 | Ubuntu | 24.04 | x86-64 |
| 4.1 | Debian | 11 | x86-64 |
| 4.1 | Debian | 12 | x86-64 |
Footnotes
-
Considering production environments, which require significant memory for maintenance processes, parallelism, work_mem, etc. ↩
-
Additional 1 to 2 GB for complex geospatial operations. ↩
-
By default, the PgBouncer component requires 2kB of memory per connection. ↩
-
The high availability agent, represented by the Patroni component, must be installed on the same server as the database service, represented by the PostgreSQL component. ↩
-
The performance of the etcd component is directly related to the memory available on the server to cache the key-value data. For high availability environments with more than 20 PostgreSQL servers, consider increasing the memory. ↩
-
Considering up to 1000 connections per second. ↩