X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 5A80ED1B8B9 for ; Mon, 24 Nov 2003 04:42:33 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 81247-04 for ; Mon, 24 Nov 2003 00:42:02 -0400 (AST) Received: from joeconway.com (66-146-172-86.skyriver.net [66.146.172.86]) by svr1.postgresql.org (Postfix) with ESMTP id E3DE3D1CAD1 for ; Mon, 24 Nov 2003 00:42:01 -0400 (AST) Received: from [192.168.5.3] (account jconway HELO joeconway.com) by joeconway.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 610270; Sun, 23 Nov 2003 20:39:54 -0800 Message-ID: <3FC18BAF.7070506@joeconway.com> Date: Sun, 23 Nov 2003 20:40:15 -0800 From: Joe Conway User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: William Yu Cc: pgsql-performance@postgresql.org Subject: Re: Maximum Possible Insert Performance? References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/204 X-Sequence-Number: 4764 William Yu wrote: > My situation is this. We have a semi-production server where we > pre-process data and then upload the finished data to our production > servers. We need the fastest possible write performance. Having the DB > go corrupt due to power loss/OS crash is acceptable because we can > always restore from last night and re-run everything that was done since > then. If you can, use COPY -- it is far faster than INSERT. See: http://www.postgresql.org/docs/current/static/sql-copy.html HTH, Joe