From: Tom Lane <tgl@sss.pgh.pa.us>
To: 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 12:38:38 -0500
Message-ID: <13141.1230313118@sss.pgh.pa.us> (raw)
In-Reply-To: <FD2D13C2E4A95C4499BF8AA8BAB85AEC20DD41D698@BDSEXCH2K7CLS.blackducksoftware.com>
References: <495271EB.80508@blackducksoftware.com>
<12778.1230140996@sss.pgh.pa.us>
<FD2D13C2E4A95C4499BF8AA8BAB85AEC20DD41D698@BDSEXCH2K7CLS.blackducksoftware.com>
Ted Allen <tallen@blackducksoftware.com> writes:
> 600mb measured by get_octet_length on data. If there is a better way to measure the row/cell size, please let me know because we thought it was the >1Gb problem too. We thought we were being conservative by getting rid of the larger rows but I guess we need to get rid of even more.
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?
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, tallen@blackducksoftware.com
Subject: Re: Troubles dumping a very large table.
In-Reply-To: <13141.1230313118@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