Re: Bug in libpq causes local clients to hang

From: "Jeffrey Baker" <jwbaker(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Bug in libpq causes local clients to hang
Date: 2008-03-24 16:21:19
Message-ID: fd145f7d0803240921t34a8ea89x70a4c72945b7de91@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Mar 23, 2008 at 8:35 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Jeffrey Baker" <jwbaker(at)gmail(dot)com> writes:
> > You'll note that I'm using the DBD::Pg Perl interface. So far I've
> > never seen this happen with TCP connections, only with UNIX sockets.
>
> 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.

-jwb

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-03-24 16:22:07 Proposal: new ereport option "errdetail_log"
Previous Message Bruce Momjian 2008-03-24 16:06:01 Re: Better error message for select_common_type()