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
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:
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.
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
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
No comments:
Post a Comment