Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 8AA306503D2; Wed, 6 Aug 2008 09:52:12 -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 98329-06-4; Wed, 6 Aug 2008 09:51:48 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from alexis.jtlnet.com (alexis.jtlnet.com [69.36.9.81]) by postgresql.org (Postfix) with ESMTP id 983BC64FFF8; Wed, 6 Aug 2008 09:51:21 -0300 (ADT) Received: from [192.168.10.103] (cpe-075-177-154-079.nc.res.rr.com [::ffff:75.177.154.79]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by alexis.jtlnet.com with esmtp; Wed, 06 Aug 2008 08:43:56 -0400 id 0008BBBD.48999C8D.00003F49 Message-ID: <48999E41.5090600@dunslane.net> Date: Wed, 06 Aug 2008 08:51:13 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text SeaMonkey/1.0.9 MIME-Version: 1.0 To: Amit jain CC: pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org, tgl@sss.pgh.pa.us Subject: Re: [HACKERS] pg_restore -d cipa /cipa/RAJASTHAN/RAJASTHAN/CIPABACKUP01_08_2008.TAR pg_restore: [archiver] out of memory References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200808/22 X-Sequence-Number: 29867 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