| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marty Scholes <marty(at)outputservices(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: 7.4.6 pg_dump failed |
| Date: | 2005-01-26 21:32:55 |
| Message-ID: | 20157.1106775175@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Inpreet Singh | 2005-01-27 05:33:43 | Re: Restore postgres database problem |
| Previous Message | Tom Lane | 2005-01-26 17:12:14 | Re: Trouble Escaping Quotes |