Skip to main content

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:

ServiceComponentCPURAMDiskComments
OrchestrationPgSmart CLI1 GHZ Dual Core512 MB100 MB
PgSmart Web2 GHZ Dual Core2 GB1 GB
PgSmart Agent1 GHZ Dual Core512 MB100 MB
DatabasePostgreSQL1 GHZ Dual Core4 GB [^1]2 GBRecommended CPU with 4 or more cores.
PostGIS1 GHZ Dual Core1 GB [^6]100 MB
Connection PoolPgBouncer1 GHZ Dual Core1 GB [^2]100 MB
Backup ManagementpgBackRest1 GHZ Dual Core512 MB100 MBConsider resizing computational resources when using WAL-E and WAL-G.
High AvailabilityPatroni [^3]1 GHZ Dual Core2 GB100 MB
etcd2 GHZ Dual Core2 GB [^4]100 MBSSD disks are recommended.
HAProxy1GHZ Dual Core1 GB [^5]100 MB
ObservabilityPrometheus1 GHZ Dual Core4 GB-SSD disks are recommended.
Prometheus Exporter1 GHz Dual Core512 MB-
Grafana2 GHZ Dual Core2 GB1 GBFor installation and logs.
Alertmanager1 GHZ Dual Core2 GB-
Karma1 GHz Dual Core1 GB-
note

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.

ServiceComponentRecomendations
DatabasePostgreSQLWhenever possible, use a dedicated host for this component.
BackuppgBackRestWhenever 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)
PatroniIt must be installed on the host(s) of the database instance(s)..
High Availability
(HA)
etcdIn 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)
HAProxyIt is recommended that this component be installed on a dedicated.
Connections PoolPgBouncerThe 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.
ObservabilityPrometheusWhenever possible, use a dedicated host for this component.
ObservabilityGrafanaWhenever possible, use a dedicated host for this component. Otherwise, preferably place it on the same server as Prometheus.
ObservabilityAlertmanagerWhenever possible, use a dedicated host for this component. Otherwise, preferably place it on the same server as Prometheus.
ObservabilityKarmaWhenever 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:

PostgreSYSOperating SystemVersionArchitecture
4.1.0CentOS8.xx86-64
4.1.0CentOS9.xx86-64
4.1.0Red Hat Enterprise Linux8.xx86-64
4.1.0Red Hat Enterprise Linux9.xx86-64
4.1.0Oracle Linux8.xx86-64
4.1.0Oracle Linux9.xx86-64
4.1.0Rocky Linux8.xx86-64
4.1.0Rocky Linux9.xx86-64
4.1.0AlmaLinux8.xx86-64
4.1.0AlmaLinux9.xx86-64
4.1.0Amazon Linux2023x86-64

New Linux distributions will be supported soon.