pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedError while executing pg_dump "invalid memory alloc request size 4294967293"
5+ messages / 3 participants
[nested] [flat]
* Error while executing pg_dump "invalid memory alloc request size 4294967293"
@ 2008-05-22 13:47 Amit jain <amitjain.bit@gmail.com>
2008-05-23 03:23 ` Re: Error while executing pg_dump "invalid memory alloc request size 4294967293" Vishal Mailinglist <list@vishal.net.in>
2008-05-23 12:48 ` Re: [HACKERS] Error while executing pg_dump "invalid memory alloc request size 4294967293" Heikki Linnakangas <heikki@enterprisedb.com>
0 siblings, 2 replies; 5+ messages in thread
From: Amit jain @ 2008-05-22 13:47 UTC (permalink / raw)
To: tgl@sss.pgh.pa.us; pgsql-admin; pgsql-hackers@postgresql.org
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Error while executing pg_dump "invalid memory alloc request size 4294967293"
2008-05-22 13:47 Error while executing pg_dump "invalid memory alloc request size 4294967293" Amit jain <amitjain.bit@gmail.com>
@ 2008-05-23 03:23 ` Vishal Mailinglist <list@vishal.net.in>
2008-05-23 06:13 ` Re: Error while executing pg_dump "invalid memory alloc request size 4294967293" Amit jain <amitjain.bit@gmail.com>
1 sibling, 1 reply; 5+ messages in thread
From: Vishal Mailinglist @ 2008-05-23 03:23 UTC (permalink / raw)
To: Amit jain <amitjain.bit@gmail.com>; +Cc: tgl@sss.pgh.pa.us; pgsql-admin; pgsql-hackers@postgresql.org
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Error while executing pg_dump "invalid memory alloc request size 4294967293"
2008-05-22 13:47 Error while executing pg_dump "invalid memory alloc request size 4294967293" Amit jain <amitjain.bit@gmail.com>
2008-05-23 03:23 ` Re: Error while executing pg_dump "invalid memory alloc request size 4294967293" Vishal Mailinglist <list@vishal.net.in>
@ 2008-05-23 06:13 ` Amit jain <amitjain.bit@gmail.com>
2008-05-23 21:34 ` Re: Error while executing pg_dump "invalid memory alloc request size 4294967293" Vishal Mailinglist <list@vishal.net.in>
0 siblings, 1 reply; 5+ messages in thread
From: Amit jain @ 2008-05-23 06:13 UTC (permalink / raw)
To: Vishal Mailinglist <list@vishal.net.in>; +Cc: pgsql-hackers@postgresql.org; pgsql-admin; tgl@sss.pgh.pa.us
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Error while executing pg_dump "invalid memory alloc request size 4294967293"
2008-05-22 13:47 Error while executing pg_dump "invalid memory alloc request size 4294967293" Amit jain <amitjain.bit@gmail.com>
2008-05-23 03:23 ` Re: Error while executing pg_dump "invalid memory alloc request size 4294967293" Vishal Mailinglist <list@vishal.net.in>
2008-05-23 06:13 ` Re: Error while executing pg_dump "invalid memory alloc request size 4294967293" Amit jain <amitjain.bit@gmail.com>
@ 2008-05-23 21:34 ` Vishal Mailinglist <list@vishal.net.in>
0 siblings, 0 replies; 5+ messages in thread
From: Vishal Mailinglist @ 2008-05-23 21:34 UTC (permalink / raw)
To: Amit jain <amitjain.bit@gmail.com>; +Cc: pgsql-hackers@postgresql.org; pgsql-admin; tgl@sss.pgh.pa.us
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.
Yes try that . Though I dont think thats going to help. Just checking are
you using AMD server any chance .
Please provide complete config of your installation.
Hardware : what machine is it the process , RAM etc
Software : OS , PostgreSQL version
> 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.
Yes , shutdown PostgreSQL, copy the data folder and reinstall the server
and after initialisation restart the server. Before you attempt that make
sure you backup atleast the database folder.
Also during backup , post the log file to the community so they can look at
it.
> 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
>
>
>
--
Regards,
Vishal Kashyap.
Need help visit
http://help.vishal.net.in
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [HACKERS] Error while executing pg_dump "invalid memory alloc request size 4294967293"
2008-05-22 13:47 Error while executing pg_dump "invalid memory alloc request size 4294967293" Amit jain <amitjain.bit@gmail.com>
@ 2008-05-23 12:48 ` Heikki Linnakangas <heikki@enterprisedb.com>
1 sibling, 0 replies; 5+ messages in thread
From: Heikki Linnakangas @ 2008-05-23 12:48 UTC (permalink / raw)
To: Amit jain <amitjain.bit@gmail.com>; +Cc: tgl@sss.pgh.pa.us; pgsql-admin; pgsql-hackers@postgresql.org
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
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2008-05-23 21:34 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-05-22 13:47 Error while executing pg_dump "invalid memory alloc request size 4294967293" Amit jain <amitjain.bit@gmail.com>
2008-05-23 03:23 ` Vishal Mailinglist <list@vishal.net.in>
2008-05-23 06:13 ` Amit jain <amitjain.bit@gmail.com>
2008-05-23 21:34 ` Vishal Mailinglist <list@vishal.net.in>
2008-05-23 12:48 ` Heikki Linnakangas <heikki@enterprisedb.com>
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