X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id BFB4B3A5894 for ; Wed, 26 Jan 2005 21:32:59 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 60224-02 for ; Wed, 26 Jan 2005 21:32:55 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 7720B3A5884 for ; Wed, 26 Jan 2005 21:32:56 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j0QLWtEg020158; Wed, 26 Jan 2005 16:32:55 -0500 (EST) To: Marty Scholes Cc: pgsql-admin@postgresql.org Subject: Re: 7.4.6 pg_dump failed In-reply-to: <41F7C606.8050007@outputservices.com> References: <41F7B44F.7030706@outputservices.com> <15489.1106756375@sss.pgh.pa.us> <41F7C606.8050007@outputservices.com> Comments: In-reply-to Marty Scholes message dated "Wed, 26 Jan 2005 09:32:06 -0700" Date: Wed, 26 Jan 2005 16:32:55 -0500 Message-ID: <20157.1106775175@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/274 X-Sequence-Number: 16133 I wrote: >> You might have better luck if you didn't use -d. After looking into it, the above seems to be sound advice. pg_dump appears to make several (three or four) copies of a wide field value when using -d or -D mode, but only one copy when using the default COPY mode. I made a minor change in 8.0 sources to get rid of one extra copy step, but getting it below three copies looks to be impractical. In any case it'd be a good idea to increase the data-segment ulimit setting you are using for both the postmaster and pg_dump, if you intend to push multi-hundred-meg field values around. regards, tom lane