From: Decibel! <decibel@decibel.org>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Bill Moran <wmoran@collaborativefusion.com>
Cc: Kevin Kempter <kevin@kevinkempterllc.com>
Cc: Pgsql performance <pgsql-performance@postgresql.org>
Subject: Re: significant vacuum issues - looking for suggestions
Date: Mon, 27 Aug 2007 17:04:39 -0500
Message-ID: <20070827220438.GR54309@nasby.net> (raw)
In-Reply-To: <46D30240.EE98.0025.0@wicourts.gov>
References: <200708241357.23629.kevin@kevinkempterllc.com>
<20070824164144.93ce05bf.wmoran@collaborativefusion.com>
<20070827210041.GN54309@nasby.net>
<46D30240.EE98.0025.0@wicourts.gov>
On Mon, Aug 27, 2007 at 04:56:33PM -0500, Kevin Grittner wrote:
> >>> Decibel! <decibel@decibel.org> 08/27/07 4:00 PM >>>
> > > > They're running version 8.1.4
> >
> > As for your pg_dump idea... why not just do a CREATE TABLE AS SELECT *
> > FROM bloated_table? That would likely be much faster than messing around
> > with pg_dump.
>
> He wanted to upgrade to 8.2.4. CREATE TABLE AS won't get him there.
>
> > > > They're running version 8.1.4 on 4-way dell boxes
> > > > with 4Gig of memory on each box attached to RAID-10 disk arrays.
> >
> > What kind of disk hardware is this running on? A good raid 10 array with
> > write caching should be able to handle a 200G database fairly well
>
> What other details were you looking for?
How many drives? Write caching? 200G isn't *that* big for good drive
hardware, *IF* it's performing the way it should. You'd be surprised how
many arrays fall on their face even from a simple dd test.
--
Decibel!, aka Jim Nasby decibel@decibel.org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
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: decibel@decibel.org, Kevin.Grittner@wicourts.gov, wmoran@collaborativefusion.com, kevin@kevinkempterllc.com
Subject: Re: significant vacuum issues - looking for suggestions
In-Reply-To: <20070827220438.GR54309@nasby.net>
* 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