X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id A308E9DC84A
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Mon, 20 Mar 2006 11:16:21 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 99462-02
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Mon, 20 Mar 2006 11:16:26 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from moonunit2.moonview.localnet (wsip-68-15-5-150.sd.sd.cox.net
	[68.15.5.150]) by postgresql.org (Postfix) with ESMTP id 729AF9DCCC0
	for <pgsql-performance@postgresql.org>;
	Mon, 20 Mar 2006 11:16:19 -0400 (AST)
Received: from [192.168.0.3] (moonunit3.moonview.localnet [192.168.0.3])
	by moonunit2.moonview.localnet (8.13.1/8.13.1) with ESMTP id
	k2KFHqwn029431; Mon, 20 Mar 2006 07:17:52 -0800
Message-ID: <441EC652.1010807@modgraph-usa.com>
Date: Mon, 20 Mar 2006 07:12:18 -0800
From: "Craig A. James" <cjames@modgraph-usa.com>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mikael Carneholm <Mikael.Carneholm@WirelessCar.com>
CC: pgsql-performance@postgresql.org
Subject: Re: Migration study, step 1: bulk write performance optimization
References: <7F10D26ECFA1FB458B89C5B4B0D72C2B088286@sesrv12.wirelesscar.com>
In-Reply-To: <7F10D26ECFA1FB458B89C5B4B0D72C2B088286@sesrv12.wirelesscar.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.103 required=5 tests=[AWL=0.103]
X-Spam-Score: 0.103
X-Spam-Level: 
X-Archive-Number: 200603/331
X-Sequence-Number: 17768

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 the data into a COPY-compatible set of files yourself.  But it will be worth the effort.

Craig