Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id B35FD64FCB1 for ; Fri, 26 Dec 2008 13:38:44 -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 35063-03 for ; Fri, 26 Dec 2008 13:38:42 -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 C338364FC78 for ; Fri, 26 Dec 2008 13:38:41 -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 mBQHccNo013142; Fri, 26 Dec 2008 12:38:38 -0500 (EST) To: Ted Allen cc: "pgsql-performance@postgresql.org" Subject: Re: Troubles dumping a very large table. In-reply-to: References: <495271EB.80508@blackducksoftware.com>, <12778.1230140996@sss.pgh.pa.us> Comments: In-reply-to Ted Allen message dated "Fri, 26 Dec 2008 11:02:55 -0500" Date: Fri, 26 Dec 2008 12:38:38 -0500 Message-ID: <13141.1230313118@sss.pgh.pa.us> From: Tom Lane 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/215 X-Sequence-Number: 32251 Ted Allen 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