From: Tom Lane <tgl@sss.pgh.pa.us>
To: Marty Scholes <marty@outputservices.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: 7.4.6 pg_dump failed
Date: Wed, 26 Jan 2005 16:32:55 -0500
Message-ID: <20157.1106775175@sss.pgh.pa.us> (raw)
In-Reply-To: <41F7C606.8050007@outputservices.com>
References: <41F7B44F.7030706@outputservices.com>
<15489.1106756375@sss.pgh.pa.us>
<41F7C606.8050007@outputservices.com>
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
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, marty@outputservices.com
Subject: Re: 7.4.6 pg_dump failed
In-Reply-To: <20157.1106775175@sss.pgh.pa.us>
References: <41F7B44F.7030706@outputservices.com> <15489.1106756375@sss.pgh.pa.us> <41F7C606.8050007@outputservices.com> <20157.1106775175@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