Re: pg_dump fails with socket_not_open

Sarah Ewen  writes:
> 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 (
> TO  stdout

Is this repeatable?  What shows up in the postmaster's log when it
happens?  What platform is this on, and what version of Postgres?

			regards, tom lane