From: Kevin Keith <kkeith@borderware.com>
To: pgsql-admin@postgresql.org
Subject: Copy Command out of memory
Date: Wed, 14 Dec 2005 18:18:07 -0500
Message-ID: <43A0A82F.5070205@borderware.com> (raw)
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
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: kkeith@borderware.com
Subject: Re: Copy Command out of memory
In-Reply-To: <43A0A82F.5070205@borderware.com>
References: <43A0A82F.5070205@borderware.com>
* 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