pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Amit jain <amitjain.bit@gmail.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: [HACKERS] pg_restore -d cipa /cipa/RAJASTHAN/RAJASTHAN/CIPABACKUP01_08_2008.TAR pg_restore: [archiver] out of memory
Date: Fri, 8 Aug 2008 12:01:40 +0530
Message-ID: <daf917830808072331v10e4e945uf964c907aaeac425@mail.gmail.com> (raw)
In-Reply-To: <48999E41.5090600@dunslane.net>
References: <daf917830808060536x5c2b996y5ce84a1c1c58071d@mail.gmail.com>
	<48999E41.5090600@dunslane.net>

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
>

view thread (3+ messages)

Message-ID: <daf917830808072331v10e4e945uf964c907aaeac425@mail.gmail.com>
Permalink:  ../daf917830808072331v10e4e945uf964c907aaeac425@mail.gmail.com/
Also on:    postgresql.org/message-id/daf917830808072331v10e4e945uf964c907aaeac425@mail.gmail.com

 · 

reply

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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: amitjain.bit@gmail.com, andrew@dunslane.net
  Subject: Re: [HACKERS] pg_restore -d cipa /cipa/RAJASTHAN/RAJASTHAN/CIPABACKUP01_08_2008.TAR pg_restore: [archiver] out of memory
  In-Reply-To: <daf917830808072331v10e4e945uf964c907aaeac425@mail.gmail.com>

* 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