| From: | Sarah Ewen <sarah(dot)ewen(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | pg_dump fails with socket_not_open |
| Date: | 2005-03-18 09:19:33 |
| Message-ID: | 953fae4f050318011972ec2ca1@mail.gmail.com |
| 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 - any pointers appreciated.
Thanks,
Sarah.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Stapleton | 2005-03-18 09:29:06 | Select Last n Rows Matching an Index Condition (and caches) |
| Previous Message | Rafael Martinez | 2005-03-18 08:41:28 | Re: pg_dump large-file support > 16GB |