From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jeffrey Baker" <jwbaker(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Bug in libpq causes local clients to hang |
Date: | 2008-03-24 16:24:40 |
Message-ID: | 4897.1206375880@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Jeffrey Baker" <jwbaker(at)gmail(dot)com> writes:
> On Sun, Mar 23, 2008 at 8:35 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> If it works over TCP and not over Unix socket, it's a kernel bug.
>> The libpq code doesn't really know the difference after connection
>> setup.
> The same thought occurred to me, but it could also be a race condition
> which the unix socket is fast enough to trigger but the TCP socket is
> not fast enough to trigger. I'm peeking around in the code but
> nothing jumps out yet.
Fairly hard to believe given that you're talking about communication
between two sequential processes. Anyway I'd suggest that the first
thing to do is extract a reproducible test case. It'd be useful
to see if it hangs on other platforms...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Brendan Jurd | 2008-03-24 16:30:48 | Re: [PATCHES] Show INHERIT in \du |
Previous Message | Heikki Linnakangas | 2008-03-24 16:23:18 | Re: [GSoC] (Is it OK to choose items without % mark in theToDoList) && (is it an acceptable idea to build index on Flash Disk) |