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 a 100% de CPU pour les grandes bases de données, Discourse 2.7.7

pfaffman (Jay Pfaffman) Août 30, 2021, 1:11 5

Je soupçonne que vous voudrez également vous assurer de procéder à la commande VACUUM et de réindexer comme décrit dans Mise à jour PostgreSQL 13.

Sujet		Réponses	Vues
Postgres using 100% of CPU Self-hosting server-resources	18	20094	Avril 10, 2021
Unusually high CPU usage Self-hosting	32	685	Mars 20, 2026
Some queries that don't finish Support	18	976	Juin 18, 2022
Long-Running Sidekiq Jobs Feature	21	1721	Décembre 24, 2020
Primary Postgres database process (postmaster) eating all CPU Self-hosting server-resources	13	4173	Mai 28, 2020