--- Sebastián Baioni <sebaioni-postgresql@yahoo.com.ar> escribió:
>
> --- Richard Huxton <dev@archonet.com> escribió:
>
> > Sebastián Baioni wrote:
> > > Hi,
> > > Some days ago we were having problems running pg_dump (v. 8.2.5.7260) from Windows XP SP2 to
> a
> > database in a sever PostgreSQL 8.2.5 on amd64-portbld-freebsd6.2.
> > > We thought the problem was solved but we are having problems again.
> > > Now we got an error:
> > > "cannot allocate memory for input buffer"
> > > The command was: "COPY public.sipat00 (sipasede, ... ) TO stdout;
> > >
> > > ¿Is this a memory problem?
> >
> > Well, yes you can't allocate memory.
> >
> > > ¿From server (FreeBSD) or from client PC (Windows XP)?
> >
> > Did you see the error on the client PC or the server?
> > What do the server logs show?
> > What was the memory usage on the client when this happened?
> >
> > --
> > Richard Huxton
> > Archonet Ltd
>
> The error was in the client PC, the command we used in a command line was: "C:\Program
> files\pgAdmin III\1.8\pg_dump.exe" -h mihost -p 5432 -U miuser -F c -v -b -f "C:\back\db.backup"
> db
> I contacted the Admin and told me there was no erros nor in the postgresql log nor in the server
> log.
> I don't know the memory usage on the client, I'll try to repeat the error and check it.
>
> Thank you
> Sebastián
>
I forgot to tell that the error was seen on the client but it was a response from the server:
pg_dump: Mensaje de error del servidor: cannot allocate memory for input buffer
pg_dump: El comando es: COPY public.sipat00 (sipasede, ...) TO stdout;
pg_dump: *** se abort¾ por un error
*Mensaje de error del servidor = Server's Error Message
*El comando es: The command is
*se abortó por un error: it was aborted because an error.
Los referentes más importantes en compra/ venta de autos se juntaron:
Demotores y Yahoo!
Ahora comprar o vender tu auto es más fácil. Vistá ar.autos.yahoo.com/