Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 34E4B2E0077 for ; Fri, 23 May 2008 03:22:20 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 55350-02 for ; Fri, 23 May 2008 03:21:53 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by developer.postgresql.org (Postfix) with ESMTP id 9692C2E00BC for ; Fri, 23 May 2008 03:13:15 -0300 (ADT) Received: by yw-out-2324.google.com with SMTP id 3so257130ywj.73 for ; Thu, 22 May 2008 23:13:12 -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=KQEjiYf2F7Skgt91Kfz7oCwAHqOukXVv6Fcd/JtsBIc=; b=pE6oT1HR5Q+C5Qd485nDRLrtKyPizE2uY5u75SoUB8pAA+IeV4ugsKmJrnAqbFaGi+Kt5Zrzoao5Rg5Mz0AIm+vXWceNqafZp711227ofISi4JPTU4W6Xu47d74+Y8+ywAoQANvEbHl09LJ/JnSycdE4lv5aPjyPhSRAe6xFTJw= 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=VRRx/dSZr42wof/J3anRSKrwSu3cBKTaRE7/yhM4lwWHlumLTHyZh+uGgmGkcRzc/DayidUFpgCu0Les5RC1QwxHjA1+D+NGuMiVHRKk0dWv+ry0mUxJuuQS7ROZCayB7Z7Ck2e8YmjtLVA8nCqAlZzBUE6RCRBc7zmU/no/k+Y= Received: by 10.150.68.2 with SMTP id q2mr1339680yba.88.1211523192299; Thu, 22 May 2008 23:13:12 -0700 (PDT) Received: by 10.151.67.20 with HTTP; Thu, 22 May 2008 23:13:12 -0700 (PDT) Message-ID: Date: Fri, 23 May 2008 11:43:12 +0530 From: "Amit jain" To: "Vishal Mailinglist" Subject: Re: Error while executing pg_dump "invalid memory alloc request size 4294967293" Cc: pgsql-hackers@postgresql.org, pgsql-admin@postgresql.org, tgl@sss.pgh.pa.us In-Reply-To: <33632cf0805222023o208f4ac2i73c24a636e639760@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_565_2153959.1211523192122" References: <33632cf0805222023o208f4ac2i73c24a636e639760@mail.gmail.com> 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: 200805/193 X-Sequence-Number: 29277 ------=_Part_565_2153959.1211523192122 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, I have tried to taken backup while no one is connected. Should i change my RAM and then check it. Version are same of pg_dump and database version 8.1. Should I copy the data folder ? and then restore it with new installation or what do you mean to say kindly brief it please. I will be thankful to any help. thanks a lot. On Fri, May 23, 2008 at 8:53 AM, Vishal Mailinglist wrote: > Hi , > > Make sure no one is connected to the database while doing the back up. > Usually memory alloc error comes if its a bad RAM . > check the pg_dump version and your database version match (this could be a > guess) > try file level backup and restore into new database. > > > On 22/05/2008, Amit jain wrote: >> >> Hello All, >> >> We are using postgresql version 8.1 and our database size is 7gb. Ram Size >> is 2 GB. >> >> while trying to take backup through pg_dump i am getting following error. >> >> oka97: pg_dump amtdb > amtdb.out >> pg_dump: ERROR: invalid memory alloc request size 4294967293 >> pg_dump: SQL command to dump the contents of table "atbs2_logs" failed: >> PQendcopy() failed. >> pg_dump: Error message from server: ERROR: invalid memory alloc request >> size 4294967293 >> pg_dump: The command was: COPY public.atbs2_logs (sno, request_time, >> msisdn, phone_make, error_code, error_desc, reply_message, request_query, >> responce_time, request_type) TO stdout; >> >> When I tried to take a single table backup i.e is mentioned in the error >> named* "public.atbs2_logs" then again getting following error. >> * >> >> pg_dump: SQL command failed >> pg_dump: Error message from server: server closed the connection >> unexpectedly >> This probably means the server terminated abnormally >> before or while processing the request. >> pg_dump: The command was: FETCH 100 FROM _pg_dump_cursor >> >> >> So we are unable to take backup , we have tried the vacuum and reindex but >> not of any use. >> >> Kindly help us Any help would be highly appreciate. Thanx in Advance. >> >> >> Amit Jain >> >> +91-9818450022 >> >> >> >> >> >> >> > > > -- > Regards, > Vishal Kashyap. > Need help visit > http://help.vishal.net.in ------=_Part_565_2153959.1211523192122 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi,
I have tried to taken backup while no one is connected. Should i change my RAM and then check it. Version are same of pg_dump and database version 8.1.

Should I copy the data folder ? and then restore it with new installation or what do you mean to say kindly brief it please. I will be thankful to any help. thanks a lot.

On Fri, May 23, 2008 at 8:53 AM, Vishal Mailinglist <list@vishal.net.in> wrote:
Hi ,
 
Make sure no one is connected to the database while doing the back up. Usually memory alloc error comes if its a bad  RAM .
check the pg_dump version and your database version match (this could be a guess)
try file level backup and restore into new database.

 
On 22/05/2008, Amit jain <amitjain.bit@gmail.com> wrote:
Hello  All,

We are using postgresql version 8.1 and our database size is 7gb. Ram Size is 2 GB. 

while trying to take backup through pg_dump i am getting following error.

oka97:  pg_dump amtdb > amtdb.out
pg_dump: ERROR:  invalid memory alloc request size 4294967293
pg_dump: SQL command to dump the contents of table "atbs2_logs" failed: PQendcopy() failed.
pg_dump: Error message from server: ERROR:  invalid memory alloc request size 4294967293
pg_dump: The command was: COPY public.atbs2_logs (sno, request_time, msisdn, phone_make, error_code, error_desc, reply_message, request_query, responce_time, request_type) TO stdout;


When I tried to take a single table backup i.e is mentioned in the error named "public.atbs2_logs"  then again getting following error.

pg_dump: SQL command failed
pg_dump: Error message from server: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
pg_dump: The command was: FETCH 100 FROM _pg_dump_cursor



So we are unable to take backup , we have tried the vacuum and reindex but not of any use.

Kindly help us Any help would be highly appreciate. Thanx in Advance.



Amit Jain

+91-9818450022









--
Regards,
Vishal Kashyap.
Need help visit
http://help.vishal.net.in

------=_Part_565_2153959.1211523192122--