Re: Can't make backup (again)

From: Richard Huxton <dev(at)archonet(dot)com>
To: sebaioni-postgresql(at)yahoo(dot)com(dot)ar
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Can't make backup (again)
Date: 2008-01-17 15:47:22
Message-ID: 478F788A.6020405@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sebastián Baioni wrote:
>> I contacted the Admin and told me there was no erros nor in the
>> postgresql log nor in the server log.

> 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.

If it is something server-side then there should be something in your
server logs.

However, if you're taking a backup, I would expect the input buffer to
be growing on the client rather than the server.

I think the Server's error message is "abortó por un error", the error
being out-of-memory on your client.

--
Richard Huxton
Archonet Ltd

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Hart 2008-01-17 16:03:43 Re: advocacy: drupal and PostgreSQL
Previous Message Scott Marlowe 2008-01-17 15:31:38 Re: Help with pre-loaded arbitrary key sequences