From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Guido Neitzer <lists@event-s.net>
Cc: Ron <rjpeace@earthlink.net>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Slow Postgresql server
Date: Thu, 12 Apr 2007 11:56:04 -0500
Message-ID: <1176396964.13754.16.camel@state.g2switchworks.com> (raw)
In-Reply-To: <0914C05F-BA1B-4A6C-A1B1-52256BC851A4@event-s.net>
References: <57271CC2-BCB1-4ACA-A177-4FF64F1BC33F@brandeis.edu>
<E1HbzJr-0005VG-GC@elasmtp-curtail.atl.sa.earthlink.net>
<16E9A17C-ADFA-43B2-B7EA-5C7A4D7E96D1@event-s.net>
<E1Hc0lc-0001iE-La@elasmtp-banded.atl.sa.earthlink.net>
<0914C05F-BA1B-4A6C-A1B1-52256BC851A4@event-s.net>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: smarlowe@g2switchworks.com, lists@event-s.net, rjpeace@earthlink.net
Subject: Re: Slow Postgresql server
In-Reply-To: <1176396964.13754.16.camel@state.g2switchworks.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox