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 1C14D9DC804 for ; Thu, 15 Dec 2005 01:24:09 -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 81487-07 for ; Thu, 15 Dec 2005 01:24:08 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id D05FD9DC82D for ; Thu, 15 Dec 2005 01:24:06 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id jBF5O5tA009914; Thu, 15 Dec 2005 00:24:05 -0500 (EST) To: Kevin Keith cc: pgsql-admin@postgresql.org Subject: Re: Copy Command out of memory In-reply-to: <43A0A82F.5070205@borderware.com> References: <43A0A82F.5070205@borderware.com> Comments: In-reply-to Kevin Keith message dated "Wed, 14 Dec 2005 18:18:07 -0500" Date: Thu, 15 Dec 2005 00:24:05 -0500 Message-ID: <9913.1134624245@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.002 required=5 tests=[AWL=0.002] X-Spam-Score: 0.002 X-Spam-Level: X-Archive-Number: 200512/138 X-Sequence-Number: 19858 Kevin Keith writes: > 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. COPY per se shouldn't eat memory. Perhaps you have some AFTER INSERT triggers on this table (note foreign key constraints would create such)? The pending-trigger queue could have overflowed memory. Offhand I can't think of another reason. regards, tom lane