| From: | Carlos Mennens <carlos(dot)mennens(at)gmail(dot)com> |
|---|---|
| To: | Christopher Opena <counterveil(at)gmail(dot)com>, "PostgreSQL (General)" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Puzzling full database lock |
| Date: | 2012-02-02 00:44:24 |
| Message-ID: | CAAQLLO4MzKOAA3fLE=dJp6yprtH4OE=k0FyX6NgyTGcLuY7U3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Feb 1, 2012 at 7:38 PM, Christopher Opena <counterveil(at)gmail(dot)com> wrote:
> Hello folks,
>
> We've been running into some very strange issues of late with our PostgreSQL
> database(s). We have an issue where a couple of queries push high CPU on a
> few of our processors and the entire database locks (reads, writes, console
> cannot be achieved unless the high CPU query procs are killed). Further
> investigation shows ~59% total cpu usage (we have 16 total cores), low io,
> and mid-to-low memory usage (we have 74GB of memory, shared_buffers=16GB).
Just out of curiosity, what OS are you running?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2012-02-02 00:46:15 | Re: EXT :Re: Intermittent occurrence of ERROR: could not open relation |
| Previous Message | Christopher Opena | 2012-02-02 00:38:31 | Puzzling full database lock |