Re: Puzzling full database lock - Mailing list pgsql-general

From Alan Hodgson
Subject Re: Puzzling full database lock
Date
Msg-id 1856771.dLdDo9FaAs@skynet.simkin.ca
Whole thread Raw
In response to Re: Puzzling full database lock  (Carlos Mennens <carlos.mennens@gmail.com>)
Responses Re: Puzzling full database lock  (Christopher Opena <counterveil@gmail.com>)
List pgsql-general
 On Wed, Feb 1, 2012 at 7:38 PM, Christopher Opena <counterveil@gmail.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).

Define "low I/O". The only things I've ever seen interfere with console access
are running out of memory or excessive disk i/o. If you're seeing even 6-12%
iowait on a 16 core machine you might very well have swamped your available
disk I/O.


pgsql-general by date:

Previous
From: Carlos Mennens
Date:
Subject: Re: Puzzling full database lock
Next
From: Scott Frankel
Date:
Subject: Re: restart server on Lion