>>>>> "SE" == Sarah Ewen <[EMAIL PROTECTED]> writes:
SE> Hi there folks, SE> I've just had pg_dump fail on me for the first time ever, and I'm not SE> sure why. SE> It generates 24MB of dump before bombing out with: SE> pg_dump: socket not open SE> pg_dump: SQL command to dump the contents of table "activity_log" SE> failed: PQendcopy() failed. SE> pg_dump: Error message from server: socket not open SE> pg_dump: The command was: COPY public.activity_log (<bunch of columns> SE> TO stdout Funny.... I just saw this for the very first time *ever* as well, overnight. I was dumping from a PG 8.0.1 server to PG 8.0.1 client. I, however, saw some ethernet interface timeouts in my server logs, which is very concerning to me. So it probably wasn't PG's fault, but I'm not ruling anything out just yet... i do see a bunch of socket not open errors for some reporting clients with no corresponding ethernet timeouts, so the log information is either conflicting or incomplete. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-869-4449 x806 ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]