Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 4272E64FD3D for ; Fri, 19 Dec 2008 04:00:48 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 20927-02 for ; Fri, 19 Dec 2008 04:00:45 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by mail.postgresql.org (Postfix) with ESMTP id E51EA64FD29 for ; Fri, 19 Dec 2008 04:00:38 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id j4so486581wah.19 for ; Fri, 19 Dec 2008 00:00:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=dYZXLMj3X73x+g++dZqmIV7Teu2i3s0e1ZG8wWMIGVM=; b=j9VKaTj2fYnJX2CpyIli3cxkfeM5IxX8InfnoCWyrclwPtMyuuaALjuuOU2a6l4kI4 YODbkIjJNuB0QT12V8EGvyv9KHG1vlMBiQf8mk7fuwdPDx5y6TrVSI2wq9F2OUO3Zis2 LT6RPYBzeBVY8Xcl+xY5spSueqnfsAo6FtNSk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=AMVO/NO7beMaEVLHbhjcUVnp9HS1fPjiiJifA4BPFerAFuQ/6DtM3BQn+KMrD13wDE n6HkbODGuHtnw4vHi/z0r4ancTQl1K7ooFPWyc+i/SG7EEcldAQdshRiOAhWKuzcmvUh wyxG6reQ88TvKF+SegllXzZAH3r0fpx/THFSo= Received: by 10.114.208.20 with SMTP id f20mr1693212wag.225.1229673636668; Fri, 19 Dec 2008 00:00:36 -0800 (PST) Received: by 10.114.185.17 with HTTP; Fri, 19 Dec 2008 00:00:36 -0800 (PST) Message-ID: Date: Fri, 19 Dec 2008 13:30:36 +0530 From: "sathiya psql" To: "Franck Routier" , pgsql-performance@postgresql.org Subject: Re: pg_restore : out of memory In-Reply-To: <1228399715.16894.22.camel@franck-laptop> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_19719_20410688.1229673636658" References: <1228399715.16894.22.camel@franck-laptop> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200812/171 X-Sequence-Number: 32207 ------=_Part_19719_20410688.1229673636658 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thu, Dec 4, 2008 at 7:38 PM, Franck Routier wrote: > Hi, > > I am trying to restore a table out of a dump, and I get an 'out of > memory' error. > > The table I want to restore is 5GB big. > > Here is the exact message : > > admaxg@goules:/home/backup-sas$ pg_restore -F c -a -d axabas -t cabmnt > axabas.dmp > pg_restore: [archiver (db)] Error while PROCESSING TOC: > pg_restore: [archiver (db)] Error from TOC entry 5492; 0 43701 TABLE > DATA cabmnt axabas > pg_restore: [archiver (db)] COPY failed: ERROR: out of memory > DETAIL: Failed on request of size 40. > CONTEXT: COPY cabmnt, line 9038995: "FHSJ CPTGEN RE > 200806_004 6.842725E7 6.842725E7 \N 7321100 1101 > \N > 00016 \N \N \N \N \N \N -1278.620..." > WARNING: errors ignored on restore: 1 > > Looking at the os level, the process is effectively eating all memory > (incl. swap), that is around 24 GB... > how are you ensuring that it eats up all memory.. post those outputs ? > > So, here is my question : is pg_restore supposed to eat all memory ? and > is there something I can do to prevent that ? > > Thanks, > > Franck > > > > -- > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance > ------=_Part_19719_20410688.1229673636658 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On Thu, Dec 4, 2008 at 7:38 PM, Franck Routier <franck.routier@axege.com> wrote:
Hi,

I am trying to restore a table out of a dump, and I get an 'out of
memory' error.

The table I want to restore is 5GB big.

Here is the exact message :

admaxg@goules:/home/backup-sas$ pg_restore -F c -a -d axabas -t cabmnt
axabas.dmp
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 5492; 0 43701 TABLE
DATA cabmnt axabas
pg_restore: [archiver (db)] COPY failed: ERROR:  out of memory
DETAIL:  Failed on request of size 40.
CONTEXT:  COPY cabmnt, line 9038995: "FHSJ    CPTGEN    RE
200806_004    6.842725E7    6.842725E7    \N    7321100    1101
\N
00016    \N    \N    \N    \N    \N    \N    -1278.620..."
WARNING: errors ignored on restore: 1

Looking at the os level, the process is effectively eating all memory
(incl. swap), that is around 24 GB...
how are you ensuring that it eats up all memory..

post those outputs ?

So, here is my question : is pg_restore supposed to eat all memory ? and
is there something I can do to prevent that ?

Thanks,

Franck



--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

------=_Part_19719_20410688.1229673636658--