Question: What is vertical scaling in PostgreSQL?


Vertical scaling, often referred to as 'scaling up', is a method of increasing the capacity of a single server by adding more resources such as CPU, RAM, or storage. In the context of PostgreSQL, vertical scaling can help accommodate larger databases or higher loads without the need to distribute the database across multiple instances or servers.

Benefits of Vertical Scaling in PostgreSQL

  • Simplicity: It is generally simpler to scale a system vertically (by adding resources to a single server) than horizontally (adding more servers). There's no need for complex configurations or database sharding.
  • Immediate Performance Improvement: Upgrading the server's hardware can provide an immediate boost to the performance of the PostgreSQL database, especially for workloads that are CPU-bound, memory-bound, or disk I/O-bound.

How to Vertically Scale PostgreSQL

  1. Upgrade CPU: Increasing the number of cores or upgrading to a faster CPU can significantly improve the performance of CPU-intensive operations within PostgreSQL.
  2. Increase RAM: PostgreSQL benefits greatly from having more memory. More RAM means larger caches (like the shared buffer), which can reduce disk I/O and speed up query processing.
  3. Enhance Storage: Faster storage (such as SSDs) can improve the performance of I/O-bound workloads. Increasing storage capacity can also support the growth of your data.
  4. Tuning PostgreSQL Configuration: Adjust PostgreSQL configuration parameters to better utilize the upgraded resources. For example, increasing shared_buffers and work_mem based on available memory can optimize performance.


While vertical scaling is effective and straightforward, it has its limits. Hardware upgrades can become increasingly expensive, and at some point, you may encounter physical or financial limitations to scaling up further. Additionally, high availability and fault tolerance are harder to achieve with a single-node setup.

Example: Memory Upgrade Impact

After increasing the server's RAM, you might adjust the shared_buffers parameter to allow PostgreSQL to cache more data. Here's an example change in the postgresql.conf file:

# Before shared_buffers = 4GB # After shared_buffers = 8GB

Similarly, adjusting work_mem allows more memory per operation, reducing disk sort operations:

# Before work_mem = 4MB # After work_mem = 8MB


Vertical scaling is a quick and effective way to boost the performance of a PostgreSQL database by adding more power to an existing server. However, it's important to balance this approach with considerations for long-term scalability, cost, and redundancy.

Was this content helpful?

White Paper

Free System Design on AWS E-Book

Download this early release of O'Reilly's latest cloud infrastructure e-book: System Design on AWS.

Free System Design on AWS E-Book
Start building today

Dragonfly is fully compatible with the Redis ecosystem and requires no code changes to implement.