Re: How to best use 32 15k.7 300GB drives?

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Robert Schnabel <schnabelr(at)missouri(dot)edu>, "david(at)lang(dot)hm" <david(at)lang(dot)hm>, pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: How to best use 32 15k.7 300GB drives?
Date: 2011-01-28 17:28:10
Message-ID: 20110128172810.GE30352@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

* Scott Marlowe (scott(dot)marlowe(at)gmail(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message yazan suleiman 2011-01-28 17:30:19 postgres 9 query performance
Previous Message Stephen Frost 2011-01-28 17:14:11 Re: How to best use 32 15k.7 300GB drives?