Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Disclaimer: I'm relatively new to Postgres.

On my production EC2 DB server, I'm experiencing high CPU usage on two of the five CPUs, ultimately resulting in latency for users of my application.

I've noticed that Postgres appears to only run two processes by default. How might I increased the default number of Postgres processes and thus allow for better spreading out of the load?

I'm using Rails/ActiveRecord on the application server if it makes a difference.

share|improve this question
up vote 2 down vote accepted

If you want more backends (the processes that actually process queries) running, connect more clients.
Postgres spawns a separate backend for each connection.

Beyond that, what your asking makes no sense if you know how Postgres internals work.

I suggest you start by reading and understanding how Postgres uses processes.

Then when you're done reading that go read about how to go about optimizing Postgres performance properly.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.