Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 4E85164FD04 for ; Wed, 10 Sep 2008 14:57:07 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 57088-01 for ; Wed, 10 Sep 2008 14:57:04 -0300 (ADT) X-Greylist: delayed 00:05:27.586092 by SQLgrey-1.7.6 Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by postgresql.org (Postfix) with ESMTP id 0B79564FD02 for ; Wed, 10 Sep 2008 14:57:03 -0300 (ADT) Received: by yx-out-2324.google.com with SMTP id 8so1437949yxb.73 for ; Wed, 10 Sep 2008 10:57:02 -0700 (PDT) Received: by 10.142.185.13 with SMTP id i13mr533182wff.219.1221069094456; Wed, 10 Sep 2008 10:51:34 -0700 (PDT) Received: by 10.143.39.19 with HTTP; Wed, 10 Sep 2008 10:51:34 -0700 (PDT) Message-ID: Date: Wed, 10 Sep 2008 10:51:34 -0700 From: "Scott Carey" To: "Alan Hodgson" Subject: Re: Improve COPY performance for large data sets Cc: pgsql-performance@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_39709_1870693.1221069094451" References: <48C7FA69.1080507@brightbuilders.com> <200809101014.34249@hal.medialogik.com> X-Google-Sender-Auth: 869660599764babc X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200809/118 X-Sequence-Number: 31431 ------=_Part_39709_1870693.1221069094451 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Correction -- 2 hours to read the whole disk. 1. It won't make a load take 12 hours unless we're talking a load that is in > total, similar to the size of the disk. A slow, newer SATA drive will read > and write at at ~50MB/sec at minimum, so the whole 320GB can be scanned at > 3GB per minute. Thats ~ 5 hours. It is not likely that 20M records is over > 20GB, and at that size there is no way the disk is the bottleneck. > ------=_Part_39709_1870693.1221069094451 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Correction --
 2 hours to read the whole disk.

1. It won't make a load take 12 hours unless we're talking a load that is in total, similar to the size of the disk.  A slow, newer SATA drive will read and write at at ~50MB/sec at minimum, so the whole 320GB can be scanned at 3GB per minute.  Thats ~ 5 hours.  It is not likely that 20M records is over 20GB, and at that size there is no way the disk is the bottleneck.

------=_Part_39709_1870693.1221069094451--