# 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:** 8

<div class="post-metadata">

**Author:** ![eboehnisch](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eboehnisch/32/133429_2.png) [@eboehnisch](https://meta.discourse.org/u/eboehnisch)\
**Post date:** [May 27, 2020, 4:42pm UTC](https://meta.discourse.org/t/primary-postgres-database-process-postmaster-eating-all-cpu/84410/8 "2020-05-27T16:42:25Z")

</div>

It now started happening for me, too, after installing the update to 2.5.0.beta5. One by one I get more `postmaster` processes that use as much CPU as they can get and it takes them sometimes a few minutes before they complete. Slowly this eats up all AWS credits for the server and makes the whole forum sluggish or even unusable.

Increasing `max_connections` didn’t have any effect, and so did rebuilding the app.

Before I updated to 2.5.0beta5 I’ve never seen this. Any hint where I should look?

---

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