X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 34AC89FB420 for ; Thu, 13 Jul 2006 14:12:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 26586-03 for ; Thu, 13 Jul 2006 14:12:15 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 35B739FB449 for ; Thu, 13 Jul 2006 14:11:58 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k6DHBuFb016045; Thu, 13 Jul 2006 13:11:56 -0400 (EDT) To: Michael Fuhr cc: Medora Schauer , Bruno Wolff III , postgresql Subject: Re: hyper slow after upgrade to 8.1.4 In-reply-to: <20060713135421.GA79008@winnie.fuhr.org> References: <1CA058827877644DAB54FB930FFA3B05A67A7A@lincoln.FAIRIND.FAIRFIELD.COM> <20060713135421.GA79008@winnie.fuhr.org> Comments: In-reply-to Michael Fuhr message dated "Thu, 13 Jul 2006 07:54:21 -0600" Date: Thu, 13 Jul 2006 13:11:56 -0400 Message-ID: <16044.1152810716@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/133 X-Sequence-Number: 19993 Michael Fuhr writes: > On Thu, Jul 13, 2006 at 08:22:46AM -0500, Medora Schauer wrote: >> Can it be that the connection delay is because first an IPv6 socket is >> trying to be established and when that fails an IPv4 socket is created? > A sniffer like tcpdump or ethereal might reveal why connecting is > so slow. I'd try strace'ing the client process first --- whatever is slow might not be exposed as TCP traffic. It does sound though that the problem is related to userland expecting IPv6 support that the kernel doesn't actually have. regards, tom lane