Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 67A899FA173 for ; Fri, 15 Dec 2006 11:44:41 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 51317-09 for ; Fri, 15 Dec 2006 11:44:36 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 0F7129FA0FB for ; Fri, 15 Dec 2006 11:44:35 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kBFFiYRG009066; Fri, 15 Dec 2006 10:44:34 -0500 (EST) To: Thomas Markus cc: pgsql-admin@postgresql.org Subject: Re: out of memory in backup and restore In-reply-to: <45828ED6.9020501@proventis.net> References: <45826AD7.7050005@proventis.net> <45828ED6.9020501@proventis.net> Comments: In-reply-to Thomas Markus message dated "Fri, 15 Dec 2006 13:02:30 +0100" Date: Fri, 15 Dec 2006 10:44:34 -0500 Message-ID: <9065.1166197474@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/224 X-Sequence-Number: 24016 Thomas Markus 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. 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. > 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.) regards, tom lane