Re: pg_dump fails with socket_not_open

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sarah Ewen <sarah(at)thaum(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dump fails with socket_not_open
Date: 2005-03-19 16:21:49
Message-ID: 15897.1111249309@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sarah Ewen <sarah(at)thaum(dot)net> 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 (<bunch of columns>
> 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Stark 2005-03-19 17:03:14 Re: pseudo-serial values in dual primary key?
Previous Message Benjamin Smith 2005-03-19 09:43:07 pseudo-serial values in dual primary key?