Re: Strange \copy failure - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Strange \copy failure
Date
Msg-id 12982.993132132@sss.pgh.pa.us
Whole thread Raw
In response to Re: Strange \copy failure  (Steve Woodcock <swoodcock@scholastic.co.uk>)
List pgsql-bugs
Steve Woodcock <swoodcock@scholastic.co.uk> writes:
> (gdb) bt
> #0  0x4025fc62 in __libc_send () from /lib/libc.so.6
> #1  0x80c7ea2 in pq_flush ()
> #2  0x8139092 in elog ()
> #3  0x80a849c in DoCopy ()
> #4  0x80a7fba in DoCopy ()
> #5  0x80a751f in DoCopy ()
> #6  0x80fe500 in ProcessUtility ()

Hmm, it would seem the backend is trying to send an elog message to
psql, and psql isn't taking it.  I bet all those "line too long"
messages caught up with you.  I'm not sure that libpq is designed
to absorb NOTICE messages that come in during a COPY operation;
probably, if you get so many as to fill the kernel-level buffers for
the socket, you have a problem.

Anyone want to try to fix that?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Steve Woodcock
Date:
Subject: Re: Strange \copy failure
Next
From: "楊 慧泉"
Date:
Subject: about createdb err