From: Tom Lane <tgl@sss.pgh.pa.us>
To: Adonias Malosso <malosso@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORMANCE] Error loading 37G CSV file "invalid string enlargement request size 65536"
Date: Tue, 22 Apr 2008 17:55:23 -0400
Message-ID: <27806.1208901323@sss.pgh.pa.us> (raw)
In-Reply-To: <8a5d3c890804221405m69eb84b0k76f8e08b7f41952c@mail.gmail.com>
References: <8a5d3c890804221405m69eb84b0k76f8e08b7f41952c@mail.gmail.com>
"Adonias Malosso" <malosso@gmail.com> writes:
> I´m running a copy for a 37G CSV and receiving the following error:
> "invalid string enlargement request size 65536"
AFAICS this would only happen if you've got an individual line of COPY
data exceeding 1GB. (PG versions later than 8.2 give a slightly more
helpful "out of memory" error in such a case.)
Most likely, that was not your intention, and the real problem is
incorrect quoting/escaping in the CSV file, causing COPY to think
that a large number of physical lines should be read as one logical line.
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, malosso@gmail.com
Subject: Re: [PERFORMANCE] Error loading 37G CSV file "invalid string enlargement request size 65536"
In-Reply-To: <27806.1208901323@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