Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 0BA1A64FD00 for ; Fri, 8 Aug 2008 03:31:54 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 71784-08 for ; Fri, 8 Aug 2008 03:31:41 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by postgresql.org (Postfix) with ESMTP id 8773D64FCF6 for ; Fri, 8 Aug 2008 03:31:41 -0300 (ADT) Received: by fg-out-1718.google.com with SMTP id 16so649341fgg.23 for ; Thu, 07 Aug 2008 23:31:40 -0700 (PDT) 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:cc:in-reply-to:mime-version:content-type:references; bh=ptdGLzZtpYEZx8GtFUDGuvwktL0Jcvtote7WfwFlleU=; b=s0AYSqIr3FYzDYtYw80cG3CivUvOA7bmgi/Iv3p0UayTbr22iuHyD1r1HoIvW0gAes nueo6BOeaXmcXd9a7Gby70+VEmISrKe+H/pVlBe7X8NWh/TNz/ThFzMoP1mRbtOodb9b HsUhFE+MAPc69lfIT3JugL0Vc+e6CCDwDMicI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=rKSupsyRxaPPsgTLlqv3uy+Af+pXwTwyP+hOGqJgpKr7khqQAnbtoZWmk07vUceoh7 Ha6a4afWG/0g8SaKARLzvH/sA6UBSSx15nsTfX6UiRjtcxMRNJxf/LfJTeoefIMKd4wk h5TAN8oyAAn56fMMiRsP7ND6gxoP/mxzkRgkw= Received: by 10.86.59.18 with SMTP id h18mr391385fga.4.1218177100425; Thu, 07 Aug 2008 23:31:40 -0700 (PDT) Received: by 10.86.73.10 with HTTP; Thu, 7 Aug 2008 23:31:40 -0700 (PDT) Message-ID: Date: Fri, 8 Aug 2008 12:01:40 +0530 From: "Amit jain" To: "Andrew Dunstan" Subject: Re: [HACKERS] pg_restore -d cipa /cipa/RAJASTHAN/RAJASTHAN/CIPABACKUP01_08_2008.TAR pg_restore: [archiver] out of memory Cc: pgsql-admin@postgresql.org In-Reply-To: <48999E41.5090600@dunslane.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_95934_12683580.1218177100429" References: <48999E41.5090600@dunslane.net> 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: 200808/31 X-Sequence-Number: 29876 ------=_Part_95934_12683580.1218177100429 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanx for info I will take care of it in future. I have tried with all ulimit settings but still getting the same error. I am trying to restore this ba ckup at server side on so i tried with shared_buffer and shmmax, Why this error occured as the same backup day one before it is restoring fine but this particular is not getting restored. Hope for getting any resolution. Amit +91-9818450022 On Wed, Aug 6, 2008 at 6:21 PM, Andrew Dunstan wrote: > > > Amit jain wrote: > >> Dear All, >> >> I am having a backup file in tar format. While restoring it through >> pg_restore instantly i am getting an following error. >> *Command - pg_restore -d cipa >> /cipa/RAJASTHAN/RAJASTHAN/CIPABACKUP01_08_2008.TAR >> Error - pg_restore: [archiver] out of memory >> *I have increased shmmax , maintenace work memory but still i am getting >> the same error. >> >> 2. I have make all log_parameter to debug5 but still getting a single >> error -line while restoring not getting any log or debug info about it. >> >> Kindly help me out from this absurd behaviour of postgreSQL restoration >> process. >> Any help would be highly appreciated. Thanx in advance >> >> >> > Please do not cross-post to multiple lists like this. (Also, adding > addresses of individual hackers is not good netiquette). The -hackers list > is quite inappropriate for usage questions. > > It looks like the problem you have is that the client is running out of > memory, so changing the server's memory settings seems unlikely to have any > beneficial effect. Maybe you need to look at your ulimit settings. > > cheers > > andrew > ------=_Part_95934_12683580.1218177100429 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Thanx for info I will take care of it in future.

I have tried with all ulimit settings but still getting the same error. I am trying to restore this ba ckup at server side on so i tried with shared_buffer and shmmax,

Why this error occured as the same backup day one before it is restoring fine but this particular is not getting restored.

Hope for getting any resolution.

Amit
+91-9818450022




On Wed, Aug 6, 2008 at 6:21 PM, Andrew Dunstan <andrew@dunslane.net> wrote:


Amit jain wrote:
Dear All,

 I am having a backup file in tar format. While restoring it through pg_restore instantly i am getting an following error.
*Command - pg_restore -d cipa /cipa/RAJASTHAN/RAJASTHAN/CIPABACKUP01_08_2008.TAR
Error  - pg_restore: [archiver] out of memory
*I have increased shmmax , maintenace work memory but still i am getting the same error.

2. I have make all log_parameter to debug5 but still getting a single error -line while restoring not getting any log or debug info about it.

Kindly help me out from this absurd behaviour of postgreSQL restoration process.
Any help would be highly appreciated. Thanx in advance



Please do not cross-post to multiple lists like this. (Also, adding addresses of individual hackers is not good netiquette). The -hackers list is quite inappropriate for usage questions.

It looks like the problem you have is that the client is running out of memory, so changing the server's memory settings seems unlikely to have any beneficial effect. Maybe you need to look at your ulimit settings.

cheers

andrew

------=_Part_95934_12683580.1218177100429--