From: | Doug McNaught <doug(at)mcnaught(dot)org> |
---|---|
To: | Dave Steinberg <dave(at)redterror(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PGError: server closed the connection unexpectedly |
Date: | 2006-01-08 00:08:20 |
Message-ID: | 87bqyn8tu3.fsf@asmodeus.mcnaught.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dave Steinberg <dave(at)redterror(dot)net> writes:
>> You're not using the same PG connection from two different threads, or
>> fork()ing and trying to use the same connection in the parent and the
>> child, or anything like that?
>
> Aha! In the ruby code, I am forking! I'll make the child reconnect
> and see if that helps (I am almost sure this will fix it). This one I
> should have guessed - I dealt with similar stuff in perl somewhat
> recently.
Yay! I thought it might be something like that.
> The pg_dumpall problem... I'll crank the debug level and see if
> there's anything interesting there, and if so I'll post about it again.
You could also, if you have to, run the BSD equivalent of 'strace'
(ktrace?) against the backend that pg_dump is connected to, and see
what might be going on. 'strace' is the gun I pull out when logfiles
aren't working for me. :)
-Doug
From | Date | Subject | |
---|---|---|---|
Next Message | Marcos José Setim | 2006-01-08 00:12:47 | Create one prepared function |
Previous Message | Dave Steinberg | 2006-01-07 23:59:58 | Re: PGError: server closed the connection unexpectedly |