From: Thomas Markus <t.markus@proventis.net>
To: pgsql-admin@postgresql.org
Subject: Re: out of memory in backup and restore
Date: Mon, 18 Dec 2006 10:07:49 +0100
Message-ID: <45865A65.3050207@proventis.net> (raw)
In-Reply-To: <9065.1166197474@sss.pgh.pa.us>
References: <45826AD7.7050005@proventis.net>
<bf54be870612150319x90ea963hf2b0c3443139ad3e@mail.gmail.com>
<45828ED6.9020501@proventis.net>
<9065.1166197474@sss.pgh.pa.us>
Hi,
i tried various ways to backup that db.
if i use a separate 'copy table to 'file' with binary' i can export the
problematic table and restore without problems. resulting outputfile is
much smaller than default output and runtime is much shorter.
is there any way to say pg_dump to use a copy command with option 'with
binary'? it should be possible with the custom or tar format. i searched
the docs and manpage and cant find something.
thx
Thomas
Tom Lane schrieb:
> Thomas Markus <t.markus@proventis.net> writes:
>
>> logfile content see http://www.rafb.net/paste/results/cvD7uk33.html
>>
>
> It looks to me like you must have individual rows whose COPY
> representation requires more than half a gigabyte (maybe much more,
> but at least that) and the system cannot allocate enough buffer space.
>
yes, msg is DETAIL: Failed on request of size 546321213. (521mb)
> It could be that this is a symptom of corrupted data, if you're certain
> that there shouldn't be any such rows in the table.
>
no
>
>> kernel is 2.6.15-1-em64t-p4-smp, pg version is 8.1.0 32bit
>>
>
> You really need a 64-bit PG build if you want to push
> multi-hundred-megabyte field values around --- otherwise there's just
> not enough headroom in the process address space. (Something newer than
> 8.1.0 would be a good idea too.)
>
i cant change the db installation. but thats another problem
> 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: t.markus@proventis.net
Subject: Re: out of memory in backup and restore
In-Reply-To: <45865A65.3050207@proventis.net>
References: <45826AD7.7050005@proventis.net> <bf54be870612150319x90ea963hf2b0c3443139ad3e@mail.gmail.com> <45828ED6.9020501@proventis.net> <9065.1166197474@sss.pgh.pa.us> <45865A65.3050207@proventis.net>
* 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