Warning: If you are using RAID, please ensure below calculation are suitable for RAID0 where READ and WRITE can be scaled equally (not linearly) and all disks has same capacity. If you are wandering if these calculations are correct, benchmark your whole volume in throughput (MiB/s) and random IOPS (with 8KiB page size) and set the number of disks to be 1 to disable the RAID estimation.
Note that for a performant PostgreSQL server, you should host your database on at least 4 disks or 4 separate volumes: 1 for PostgreSQL binaries, configuration, and transaction management; 1 for WAL; 1 for data and index; and 1 for database logging. Also, if you use tablespace to separate random IOPS for data/index volume then it would be great. You then also need a remote storage to store the backup, WAL archive, and compressed database logs.
These settings are used to estimate what is the optimized scenario to perform aggressive anti-wraparound vacuum.
These advanced parameters allowed you to have more control over the PostgreSQL database settings, such as higher memory utilization per connection, connection scaling, future-proofing your server against multiple profiles, and more. Some benefits of these advanced settings are: - Reduce fine-grained memory control (session-based memory tuning) by application. - Higher WAL utilization for high-transactional databases. - ...