X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 5ADD09DCA2B for ; Wed, 14 Dec 2005 19:22:16 -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 19630-07 for ; Wed, 14 Dec 2005 19:22:18 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.borderware.com (mail.borderware.com [207.236.65.231]) by postgresql.org (Postfix) with ESMTP id 0F0429DCA2C for ; Wed, 14 Dec 2005 19:22:13 -0400 (AST) Message-ID: <43A0A82F.5070205@borderware.com> Date: Wed, 14 Dec 2005 18:18:07 -0500 From: Kevin Keith User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Copy Command out of memory 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 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200512/133 X-Sequence-Number: 19853 I was trying to run a bulk data load using the COPY command on PGSQL 8.1.0. After loading about 3,500,000 records it ran out of memory - I am assuming because it ran out of space to store such a large transaction. Does the COPY command offer a similar feature to Oracle's SQL*Loader where you can specify the number of records to load between commit statements, or will I have to break the file I am loading into smaller files? Or can a transaction be bypassed altogether with the COPY command since any failure (the load is going to an empty table) could easily be solved with a reload of the data anyway. Thanks, Kevin