Re: Improve COPY performance for large data sets - Mailing list pgsql-performance

From Scott Carey
Subject Re: Improve COPY performance for large data sets
Date
Msg-id a1ec7d000809101051r75f451b4yef92396965453381@mail.gmail.com
Whole thread Raw
In response to Re: Improve COPY performance for large data sets  ("Scott Carey" <scott@richrelevance.com>)
List pgsql-performance
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.

pgsql-performance by date:

Previous
From: "Scott Carey"
Date:
Subject: Re: Improve COPY performance for large data sets
Next
From: "Scott Carey"
Date:
Subject: Re: too many clog files