From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | dylangregory612(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #16542: High CPU Usage |
Date: | 2020-07-15 07:35:59 |
Message-ID: | CAApHDvqiQW7cMEum9UaBjv+DfO4YN3mv6XmnMUL-AgO_4mmdCQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, 15 Jul 2020 at 19:16, PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> I'm not sure if it's 12.0 as I installed it with "sudo apt-get install
> PostgreSQL" and only know that it is v12.x. Our VPS has a 3x vCore (3.70ghz)
> CPU but when we checked HTOP, we noticed that PostgreSQL was maxing out all
> 3 cores after sorting the list out by CPU Percentage. This is incredibly
> high and we don't know why it's being maxed out. You can view the HTOP
> results here: https://imgur.com/a/FxByiyX
There's no evidence here to suggest a bug yet. If you connect to
PostgreSQL with psql, you can look at what each of those processes is
doing with:
SELECT * FROM pg_stat_activity;
Perhaps you just have some queries that are busy with something.
David
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2020-07-15 07:48:29 | Re: BUG #16501: Incorrect result. select multi_key_columns_range_partition_table |
Previous Message | Etsuro Fujita | 2020-07-15 07:35:52 | Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table |