Re: Migration study, step 1: bulk write performance optimization - Mailing list pgsql-performance

From Craig A. James
Subject Re: Migration study, step 1: bulk write performance optimization
Date
Msg-id 441EC652.1010807@modgraph-usa.com
Whole thread Raw
In response to Migration study, step 1: bulk write performance optimization  ("Mikael Carneholm" <Mikael.Carneholm@WirelessCar.com>)
Responses update == delete + insert?  ("Craig A. James" <cjames@modgraph-usa.com>)
Re: Migration study, step 1: bulk write performance optimization  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
Mikael Carneholm wrote:

> I am responisble for an exciting project of evaluating migration of a
> medium/large application for a well-known swedish car&truck manufacturer
> ... The goal right now is to find the set of parameters that gives as
> short bulk insert time as possible, minimizing downtime while the data
> itself is migrated.

If you haven't explored the COPY command yet, check it out.  It is stunningly fast compared to normal INSERT commands.

   http://www.postgresql.org/docs/8.1/static/sql-copy.html

pg_dump and pg_restore make use of the COPY command.  Since you're coming from a different vendor, you'd have to dump
thedata into a COPY-compatible set of files yourself.  But it will be worth the effort. 

Craig

pgsql-performance by date:

Previous
From: Marco Furetto
Date:
Subject: Query Feromance
Next
From: Csaba Nagy
Date:
Subject: Re: Migration study, step 1: bulk write performance