Skip site navigation (1) Skip section navigation (2)

FWD: [ADMIN] pg_dump error

From: "Guido Barosio" <gbarosio(at)gmail(dot)com>
To:
Cc: pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: FWD: [ADMIN] pg_dump error
Date: 2006-07-06 12:52:03
Message-ID: f7f6b4c70607060552m2682d5b2p969e7c70acc0e1d8@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-advocacy
How come?

Where does the "postgress" word comes from? I get mad when I read the double ss.
Progress Software ?! It's not that famous  / big / popular.

g.-

On 7/6/06, Dilipkumar <dilipkumar_parikh(at)sifycorp(dot)com> wrote:
> 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(at)sifycorp(dot)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
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>


-- 
Guido Barosio
-----------------------
http://www.globant.com
guido(dot)barosio(at)globant(dot)com

In response to

Responses

pgsql-admin by date

Next:From: Moritz BayerDate: 2006-07-06 21:14:25
Subject: Need Help with Logfile Entry
Previous:From: Christopher BrowneDate: 2006-07-06 12:42:17
Subject: Re: pgpool

pgsql-advocacy by date

Next:From: Robin GareusDate: 2006-07-06 14:09:26
Subject: Re: postgresql live-cd
Previous:From: Christopher BrowneDate: 2006-07-06 12:42:17
Subject: Re: pgpool

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group