Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id 28A5E1337B5C
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Fri, 28 Jan 2011 13:28:18 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 74106-07
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Fri, 28 Jan 2011 17:28:11 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from tamriel.snowman.net (tamriel.snowman.net [72.66.115.51])
	by mail.postgresql.org (Postfix) with ESMTP id E00E11337B53
	for <pgsql-performance@postgresql.org>;
	Fri, 28 Jan 2011 13:28:10 -0400 (AST)
Received: by tamriel.snowman.net (Postfix, from userid 1000)
	id 6EFE1229CD; Fri, 28 Jan 2011 12:28:10 -0500 (EST)
Date: Fri, 28 Jan 2011 12:28:10 -0500
From: Stephen Frost <sfrost@snowman.net>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Robert Schnabel <schnabelr@missouri.edu>, "david@lang.hm" <david@lang.hm>,
	pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: How to best use 32 15k.7 300GB drives?
Message-ID: <20110128172810.GE30352@tamriel.snowman.net>
References: <4D41F92F.9030006@missouri.edu>
	<alpine.DEB.2.00.1101271512390.17579@asgard.lang.hm>
	<4D420D61.3000109@missouri.edu>
	<20110128131410.GC30352@tamriel.snowman.net>
	<4D42F127.9050307@missouri.edu>
	<AANLkTi=3j3PW=Lkrwu2XiWdS4jCy0TcLLO4L2h3=9U0G@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="mVonZaCXjkyW6e25"
Content-Disposition: inline
In-Reply-To: <AANLkTi=3j3PW=Lkrwu2XiWdS4jCy0TcLLO4L2h3=9U0G@mail.gmail.com>
X-Editor: Vim http://www.vim.org/
X-Info: http://www.snowman.net
X-Operating-System: Linux/2.6.32-5-amd64 (x86_64)
X-Uptime: 12:27:08 up 36 days, 16:15, 11 users,  load average: 1.09, 1.07,
 1.02
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201101/319
X-Sequence-Number: 42106


--mVonZaCXjkyW6e25
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

* Scott Marlowe (scott.marlowe@gmail.com) wrote:
> There's nothing wrong with whole table updates as part of an import
> process, you just have to know to "clean up" after you're done, and
> regular vacuum can't fix this issue, only vacuum full or reindex or
> cluster.

Just to share my experiences- I've found that creating a new table and
inserting into it is actually faster than doing full-table updates, if
that's an option for you.

	Thanks,

		Stephen

--mVonZaCXjkyW6e25
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk1C/KoACgkQrzgMPqB3kijCOQCfUq8W51nsOugyqmZDQCY/DSIk
pgMAnju8TV7TYkESx3ruN19pv/qNX7Q9
=aJBI
-----END PGP SIGNATURE-----

--mVonZaCXjkyW6e25--