pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dilipkumar <dilipkumar_parikh@sifycorp.com>
To: manjula hettiarachchi <manjula_55@yahoo.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Cc: postgresql-l <postgresql-l@groups.ittoolbox.com>
Subject: Re: pg_dump error
Date: Thu, 06 Jul 2006 17:59:11 +0530
Message-ID: <44AD0217.5060206@sifycorp.com> (raw)
In-Reply-To: <20060706122524.71421.qmail@web50302.mail.yahoo.com>
References: <20060706122524.71421.qmail@web50302.mail.yahoo.com>

Hi,

If you are trying to take a table dump try using this

pd_dump databasename -t tablename

if you are taking in the same server done mention as localhost just 
switch user as postgress and give the above command mentioned.

manjula hettiarachchi wrote:

>Hello List
>
>I am using postgresql 7.4.7 in a voip production
>setup.
>I have been using pg_dump -Fc for regular backing up.
>Since yesterday i am getting the following error for
>the command:
>
>root# pg_dump -h 'localhost' voipdb -t voipcall -Fc -f
>voipcall.bak
>
>The error is :
>
>pg_dump: ERROR:  invalid memory alloc request size
>4294967293
>pg_dump: SQL command to dump the contents of table
>"voipcall" failed: PQendcopy() failed.
>pg_dump: Error message from server: ERROR:  invalid
>memory alloc request size 4294967293
>pg_dump: The command was: COPY public.voipcall (id,
>accountid, .........., prefix) TO stdout;
>
>However when i tried to Vacuum analyze the same table
>its fine and no errors. Also the SQL access to the
>same table runs fine without any errors.
>
>Only the pg_dump is failing for this particular table.
>
>Can anyone suggest a method to fix this?
>
>Thanks in advance
>
>Manjula
>
>
>
>__________________________________________________
>Do You Yahoo!?
>Tired of spam?  Yahoo! Mail has the best spam protection around 
>http://mail.yahoo.com 
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: Don't 'kill -9' the postmaster
>
>  
>


-- 
Thanks & Regards,
Dilipkumar
DBA Support

********** DISCLAIMER **********
Information contained and transmitted by this E-MAIL is proprietary to 
Sify Limited and is intended for use only by the individual or entity to 
which it is addressed, and may contain information that is privileged, 
confidential or exempt from disclosure under applicable law. If this is a 
forwarded message, the content of this E-MAIL may not have been sent with 
the authority of the Company. If you are not the intended recipient, an 
agent of the intended recipient or a  person responsible for delivering the 
information to the named recipient,  you are notified that any use, 
distribution, transmission, printing, copying or dissemination of this 
information in any way or in any manner is strictly prohibited. If you have 
received this communication in error, please delete this mail & notify us 
immediately at admin@sifycorp.com

Watch India vs. England LIVE, Hot videos and more only on Sify Max! Click Here. www.sifymax.com

Get to see what's happening in your favourite City on Bangalore Live! www.bangalorelive.in




view thread (40+ messages)  latest in thread

Message-ID: <44AD0217.5060206@sifycorp.com>
Permalink:  ../44AD0217.5060206@sifycorp.com/
Also on:    postgresql.org/message-id/44AD0217.5060206@sifycorp.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: dilipkumar_parikh@sifycorp.com, manjula_55@yahoo.com, postgresql-l@groups.ittoolbox.com
  Subject: Re: pg_dump error
  In-Reply-To: <44AD0217.5060206@sifycorp.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