| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | Medora Schauer <mschauer(at)fairfield(dot)com>, Bruno Wolff III <bruno(at)wolff(dot)to>, postgresql <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: hyper slow after upgrade to 8.1.4 |
| Date: | 2006-07-13 17:11:56 |
| Message-ID: | 16044.1152810716@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Michael Fuhr <mike(at)fuhr(dot)org> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-13 17:42:41 | Re: size of pg_dump files containing bytea values |
| Previous Message | Greg Stark | 2006-07-13 16:30:50 | Re: size of pg_dump files containing bytea values |