# Postgres al 100% di CPU per database di grandi dimensioni, Discourse 2.7.7

**URL:** <https://meta.discourse.org/t/postgres-has-100-cpu-for-large-databases-discourse-2-7-7/202106>\
**Category:** Self-hosting\
**Tags:** server-resources\
**Created:** [30 Agosto 2021, 11:36am UTC](https://meta.discourse.org/t/postgres-has-100-cpu-for-large-databases-discourse-2-7-7/202106 "2021-08-30T11:36:37Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![dmorlock](https://avatars.discourse-cdn.com/v4/letter/d/7993a0/32.png) [@dmorlock](https://meta.discourse.org/u/dmorlock)\
**Post date:** [30 Agosto 2021, 12:13pm UTC](https://meta.discourse.org/t/postgres-has-100-cpu-for-large-databases-discourse-2-7-7/202106/3 "2021-08-30T12:13:47Z")

</div>

Abbiamo individuato che il problema era causato da una query SQL personalizzata in un badge utente. Quindi non si tratta di un problema upstream. Grazie.

---

_[View the full topic](https://meta.discourse.org/t/postgres-has-100-cpu-for-large-databases-discourse-2-7-7/202106)._