I use htop command,
I noticed the CPU goes too high.
I get the error: postgres: 10/main
How to handle this error?
AI-generated summary
User hokod reports high CPU usage after a rebuild, citing an error message involving “postgres:10/main” and sharing a screenshot. pfaffman suggests PostgreSQL 10 is no longer supported and recommends upgrading to PostgreSQL 13, which may resolve performance issues; they note that if no explicit error occurred during upgrade, the system may still be stable. supermathie clarifies that the message isn’t necessarily an error but may indicate a heavy background task like a scheduled job or migration. They advise allowing time for the system to settle, backing up data, and proceeding with the PostgreSQL 13 upgrade for potential performance gains. hokod speculates the high CPU might be caused by Jobs::PeriodicalUpdates, referencing a related discussion here. The consensus leans toward upgrading PostgreSQL and monitoring background jobs to mitigate CPU load.
I think that PG 10 is no longer supported. See PostgreSQL 13 update.
But if you did an upgrade and didn’t get an error, then it’s probably OK (but you should upgrade to PG13). The PG13 upgrade was pushed because it improves some performance issues that might include the one that you’re seeing.
This is not, strictly speaking, an error. But a large is running which may be a scheduled job or migration.
Regardless, this is a good suggestion:
I would allow it some time to settle after the upgrade; you do have a lot of CPU still available. After it settles down, back up your data and go through the update procedure, it’ll likely increase performance.
I guess so, and that’s why I want to stop Jobs::PeriodicalUpdates (Jobs::PeriodicalUpdates is the cause of high CPU (over 100%) - #7 by hokod)