thread-index: Aci8024Trylr48vUQfeiHjOl9vliEA==
Content-Class: urn:content-classes:message
Importance: normal
Message-ID: <4836BD02.3010008@enterprisedb.com>
Date: Fri, 23 May 2008 13:48:02 +0100
From: "Heikki Linnakangas" <heikki@enterprisedb.com>
Organization: EnterpriseDB
User-Agent: Mozilla-Thunderbird 2.0.0.12 (X11/20080420)
MIME-Version: 1.0
To: "Amit jain" <amitjain.bit@gmail.com>
Cc: <tgl@sss.pgh.pa.us>, <pgsql-admin@postgresql.org>,
	<pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] Error while executing pg_dump "invalid memory alloc
	request size 4294967293"
References: <daf917830805220647u6deb00ddx899b96c5de7faadd@mail.gmail.com>
In-Reply-To: <daf917830805220647u6deb00ddx899b96c5de7faadd@mail.gmail.com>
Content-Type: text/plain;
	format=flowed;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

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.

It seems to me that you have corrupted data in that table for some 
reason, perhaps bad hardware? I bet that a simple "SELECT * FROM 
atbs2_logs" will fail as well.

Which server version is this exactly? 8.1.what?

How far did the pg_dump get before the crash? Is there any output at all?

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com