# Primary Postgres database process (postmaster) eating all CPU

**URL:** <https://meta.discourse.org/t/primary-postgres-database-process-postmaster-eating-all-cpu/84410>\
**Category:** Self-hosting\
**Tags:** server-resources\
**Created:** [April 2, 2018, 10:12pm UTC](https://meta.discourse.org/t/primary-postgres-database-process-postmaster-eating-all-cpu/84410 "2018-04-02T22:12:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [April 3, 2018, 3:05am UTC](https://meta.discourse.org/t/primary-postgres-database-process-postmaster-eating-all-cpu/84410/2 "2018-04-03T03:05:39Z")

</div>

The postgresql connection limit needs to be increased. That will cause the database as a whole to use more memory, but based on the `free` output you’ve got plenty that could be used if required. I’d double the current value, and review errors and resource consumption.

---

_[View the full topic](https://meta.discourse.org/t/primary-postgres-database-process-postmaster-eating-all-cpu/84410)._
