From: Michael Fuhr <mike@fuhr.org>
To: Medora Schauer <mschauer@fairfield.com>
Cc: Bruno Wolff III <bruno@wolff.to>
Cc: postgresql <pgsql-performance@postgresql.org>
Subject: Re: hyper slow after upgrade to 8.1.4
Date: Thu, 13 Jul 2006 07:54:21 -0600
Message-ID: <20060713135421.GA79008@winnie.fuhr.org> (raw)
In-Reply-To: <1CA058827877644DAB54FB930FFA3B05A67A7A@lincoln.FAIRIND.FAIRFIELD.COM>
References: <1CA058827877644DAB54FB930FFA3B05A67A7A@lincoln.FAIRIND.FAIRFIELD.COM>
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. The problem might be with DNS queries for AAAA (IPv6)
records prior to queries for A (IPv4) records; see this thread from
almost a year ago:
http://archives.postgresql.org/pgsql-general/2005-08/msg00216.php
--
Michael Fuhr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mike@fuhr.org, mschauer@fairfield.com, bruno@wolff.to
Subject: Re: hyper slow after upgrade to 8.1.4
In-Reply-To: <20060713135421.GA79008@winnie.fuhr.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox