=?iso-8859-1?q?Sebasti=E1n=20Baioni?= <[EMAIL PROTECTED]> writes:
> 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 (si
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 b
--- Sebastián Baioni <[EMAIL PROTECTED]> escribió:
>
> --- Richard Huxton <[EMAIL PROTECTED]> 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
--- Richard Huxton <[EMAIL PROTECTED]> 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
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
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"
T
