Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 9C89A9FB9E3 for ; Thu, 12 Apr 2007 13:56:10 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 23232-04 for ; Thu, 12 Apr 2007 13:56:07 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id A48339FB958 for ; Thu, 12 Apr 2007 13:56:06 -0300 (ADT) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Thu, 12 Apr 2007 16:56:04 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 12 Apr 2007 11:56:04 -0500 Subject: Re: Slow Postgresql server From: Scott Marlowe To: Guido Neitzer Cc: Ron , PostgreSQL Performance In-Reply-To: <0914C05F-BA1B-4A6C-A1B1-52256BC851A4@event-s.net> References: <57271CC2-BCB1-4ACA-A177-4FF64F1BC33F@brandeis.edu> <16E9A17C-ADFA-43B2-B7EA-5C7A4D7E96D1@event-s.net> <0914C05F-BA1B-4A6C-A1B1-52256BC851A4@event-s.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1176396964.13754.16.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 12 Apr 2007 11:56:04 -0500 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/257 X-Sequence-Number: 24134 On Thu, 2007-04-12 at 10:19, Guido Neitzer wrote: > On 12.04.2007, at 08:59, Ron wrote: > > Depends. As I said - if the whole DB fits into the remaining space, > and a lot of website backend DBs do, it might just work out. But this > seems not to be the case - either the site is chewing on seq scans > all the time which will cause I/O or it is bound by the lack of > memory and swaps the whole time ... He has to find out. It could also be something as simple as a very bloated data store. I'd ask the user what vacuum verbose says at the end