pg_dump fails with socket_not_open

From: Sarah Ewen <sarah(at)thaum(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: pg_dump fails with socket_not_open
Date: 2005-03-19 09:13:57
Message-ID: 423BED55.40301@thaum.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi there folks,

I've just had pg_dump fail on me for the first time ever, and I'm not
sure why.

It generates 24MB of dump before bombing out with:

pg_dump: socket not open
pg_dump: SQL command to dump the contents of table "activity_log"
failed: PQendcopy() failed.
pg_dump: Error message from server: socket not open
pg_dump: The command was: COPY public.activity_log (<bunch of columns>
TO stdout

Are there any common reasons for seeing this?

I'm fairly sure that the machine is ok hardware wise, and strangely
enough, pg_dumpall works, so it's really curiosity and to set my mind at
rest - any pointers appreciated.

Thanks,

Sarah.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Benjamin Smith 2005-03-19 09:43:07 pseudo-serial values in dual primary key?
Previous Message Thomas F.O'Connell 2005-03-19 07:16:23 Re: Select Last n Rows Matching an Index Condition (and caches)