From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Keith <kkeith@borderware.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Copy Command out of memory
Date: Thu, 15 Dec 2005 00:24:05 -0500
Message-ID: <9913.1134624245@sss.pgh.pa.us> (raw)
In-Reply-To: <43A0A82F.5070205@borderware.com>
References: <43A0A82F.5070205@borderware.com>
Kevin Keith <kkeith@borderware.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, kkeith@borderware.com
Subject: Re: Copy Command out of memory
In-Reply-To: <9913.1134624245@sss.pgh.pa.us>
References: <43A0A82F.5070205@borderware.com> <9913.1134624245@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox