> "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 ta
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 se
Sarah Ewen <[EMAIL PROTECTED]> writes:
>> Is this repeatable? What shows up in the postmaster's log when it
>> happens? What platform is this on, and what version of Postgres?
> This is postgresql-7.4.6-1.FC2.2 running on RedHat Fedora Core 2.
> The logs don't reveal anything, and it happens co
Hi there Tom, thanks for your reply.
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
Sarah Ewen <[EMAIL PROTECTED]> 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() fai
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 ser
