=?iso-8859-1?q?Sebasti=E1n=20Baioni?= <sebaioni-postgresql@xxxxxxxxxxxx> 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 (sipasede, ...) TO stdout;
> pg_dump: *** se abort¾ por un error
No, that error text only appears in libpq, so it's happening on the
client side --- pg_dump just doesn't know the difference between an
error sent from the server and one generated within libpq.
My guess is that there's some extremely wide row(s) in your database.
The client-side libpq has to be able to buffer the widest row during
a COPY, and your client machine doesn't seem to be up to the task...
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
