Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Troubles dumping a very large table.


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: Ted Allen <tallen(at)blackducksoftware(dot)com>
  • Cc: pgsql-performance(at)postgresql(dot)org
  • Subject: Re: Troubles dumping a very large table.
  • Date: Wed, 24 Dec 2008 12:49:56 -0500
  • Message-id: <12778.1230140996@sss.pgh.pa.us> <text/plain>

Ted Allen <tallen(at)blackducksoftware(dot)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



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group