Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 18A5E64FDD7
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Wed, 24 Dec 2008 13:50:02 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 51838-07
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Wed, 24 Dec 2008 13:49:59 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 1C1FC64FC85
	for <pgsql-performance@postgresql.org>;
	Wed, 24 Dec 2008 13:49:58 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id mBOHnvwZ012779;
	Wed, 24 Dec 2008 12:49:57 -0500 (EST)
To: Ted Allen <tallen@blackducksoftware.com>
cc: pgsql-performance@postgresql.org
Subject: Re: Troubles dumping a very large table. 
In-reply-to: <495271EB.80508@blackducksoftware.com> 
References: <495271EB.80508@blackducksoftware.com>
Comments: In-reply-to Ted Allen <tallen@blackducksoftware.com>
	message dated "Wed, 24 Dec 2008 12:31:23 -0500"
Date: Wed, 24 Dec 2008 12:49:56 -0500
Message-ID: <12778.1230140996@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200812/210
X-Sequence-Number: 32246

Ted Allen <tallen@blackducksoftware.com> writes:
> during the upgrade.  The trouble is, when I dump the largest table, 
> which is 1.1 Tb with indexes, I keep getting the following error at the 
> same point in the dump.

> pg_dump: SQL command failed
> pg_dump: Error message from server: ERROR:  invalid string enlargement 
> request size 1
> pg_dump: The command was: COPY public.large_table (id, data) TO stdout;

> As you can see, the table is two columns, one column is an integer, and 
> the other is bytea.   Each cell in the data column can be as large as 
> 600mb (we had bigger rows as well but we thought they were the source of 
> the trouble and moved them elsewhere to be dealt with separately.)

600mb measured how?  I have a feeling the problem is that the value
exceeds 1Gb when converted to text form...

			regards, tom lane