Date: Mon, 27 Aug 2007 17:04:39 -0500
From: Decibel! <decibel@decibel.org>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Bill Moran <wmoran@collaborativefusion.com>,
	Kevin Kempter <kevin@kevinkempterllc.com>,
	Pgsql performance <pgsql-performance@postgresql.org>
Subject: Re: significant vacuum issues - looking for suggestions
Message-ID: <20070827220438.GR54309@nasby.net>
References: <200708241357.23629.kevin@kevinkempterllc.com>
	<20070824164144.93ce05bf.wmoran@collaborativefusion.com>
	<20070827210041.GN54309@nasby.net>
	<46D30240.EE98.0025.0@wicourts.gov>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="EeeDLpRJNGbogvEL"
Content-Disposition: inline
In-Reply-To: <46D30240.EE98.0025.0@wicourts.gov>
User-Agent: Mutt/1.5.13 (2006-08-11)


--EeeDLpRJNGbogvEL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Aug 27, 2007 at 04:56:33PM -0500, Kevin Grittner wrote:
> >>> Decibel! <decibel@decibel.org> 08/27/07 4:00 PM >>>=20
> > > > They're running  version 8.1.4
> >=20
> > 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.
> =20
> He wanted to upgrade to 8.2.4.  CREATE TABLE AS won't get him there.
> =20
> > > > They're running  version 8.1.4 on 4-way dell boxes=20
> > > > with 4Gig of memory on each box attached to RAID-10 disk arrays.=20
> >=20
> > 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
> =20
> 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.
--=20
Decibel!, aka Jim Nasby                        decibel@decibel.org
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

--EeeDLpRJNGbogvEL
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (FreeBSD)

iD8DBQFG00p2dO30qud8SkgRArIWAKCFEaseYwVoRWN1bWug8rB+muhkfACdGxch
BV6BBwrzy+LVp9BxVim3tWY=
=PLsY
-----END PGP SIGNATURE-----

--EeeDLpRJNGbogvEL--