pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Vishal Mailinglist <list@vishal.net.in>
To: Amit jain <amitjain.bit@gmail.com>
Cc: tgl@sss.pgh.pa.us
Cc: pgsql-admin@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: Error while executing pg_dump "invalid memory alloc request size 4294967293"
Date: Fri, 23 May 2008 08:53:23 +0530
Message-ID: <33632cf0805222023o208f4ac2i73c24a636e639760@mail.gmail.com> (raw)
In-Reply-To: <daf917830805220647u6deb00ddx899b96c5de7faadd@mail.gmail.com>
References: <daf917830805220647u6deb00ddx899b96c5de7faadd@mail.gmail.com>

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

view thread (5+ messages)  latest in thread

Message-ID: <33632cf0805222023o208f4ac2i73c24a636e639760@mail.gmail.com>
Permalink:  ../33632cf0805222023o208f4ac2i73c24a636e639760@mail.gmail.com/
Also on:    postgresql.org/message-id/33632cf0805222023o208f4ac2i73c24a636e639760@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: list@vishal.net.in, amitjain.bit@gmail.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
  Subject: Re: Error while executing pg_dump "invalid memory alloc request size 4294967293"
  In-Reply-To: <33632cf0805222023o208f4ac2i73c24a636e639760@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