Hi, we are running Docker based Discourse 2.7.7 with a very large user base. After upgrading from 2.4.2 to 2.7.7, we are experiencing that some Postgres process are stuck at 100% CPU. Further investigation results that such queries seem to cause the problem: discourse_prod=# select pid, datid, que…

We’ve found the issue was caused by a custom SQL query in a user badge. So this is not an upstream issue. Thanks.

This query seems to come from Jobs::BadgeGrant.

I suspect that you’ll also want to make sure that you vacuum and reindex as described in PostgreSQL 13 update .

Postgres al 100% de CPU con bases de datos grandes, Discourse 2.7.7

pfaffman (Jay Pfaffman) 30 Agosto, 2021 13:11 5

Sospecho que también querrás asegurarte de ejecutar vacuum y reindexar como se describe en Actualización de PostgreSQL 13.

Tema		Respuestas	Vistas
Postgres using 100% of CPU Self-hosting server-resources	18	20093	10 Abril 2021
Unusually high CPU usage Self-hosting	32	656	20 Marzo 2026
Some queries that don't finish Support	18	973	18 Junio 2022
Long-Running Sidekiq Jobs Feature	21	1719	24 Diciembre 2020
Primary Postgres database process (postmaster) eating all CPU Self-hosting server-resources	13	4172	28 Mayo 2020