From: Tom Lane <tgl@sss.pgh.pa.us>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: Ted Allen <tallen@blackducksoftware.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Troubles dumping a very large table.
Date: Fri, 26 Dec 2008 15:18:50 -0500
Message-ID: <14875.1230322730@sss.pgh.pa.us> (raw)
In-Reply-To: <b42b73150812261150k6b17b819i704b6b7720243eb8@mail.gmail.com>
References: <495271EB.80508@blackducksoftware.com>
<12778.1230140996@sss.pgh.pa.us>
<FD2D13C2E4A95C4499BF8AA8BAB85AEC20DD41D698@BDSEXCH2K7CLS.blackducksoftware.com>
<13141.1230313118@sss.pgh.pa.us>
<b42b73150812261150k6b17b819i704b6b7720243eb8@mail.gmail.com>
"Merlin Moncure" <mmoncure@gmail.com> writes:
> On Fri, Dec 26, 2008 at 12:38 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Yeah, the average expansion of bytea data in COPY format is about 3X :-(
>> So you need to get the max row length down to around 300mb. I'm curious
>> how you got the data in to start with --- were the values assembled on
>> the server side?
> Wouldn't binary style COPY be more forgiving in this regard? (if so,
> the OP might have better luck running COPY BINARY)...
Yeah, if he's willing to use COPY BINARY directly. AFAIR there is not
an option to get pg_dump to use it. But maybe "pg_dump -s" together
with a manual dump of the table data is the right answer. It probably
beats shoving some of the rows aside as he's doing now...
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, mmoncure@gmail.com, tallen@blackducksoftware.com
Subject: Re: Troubles dumping a very large table.
In-Reply-To: <14875.1230322730@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