Re: pg_connect takes 3.0 seconds - Mailing list pgsql-performance

From Craig Ringer
Subject Re: pg_connect takes 3.0 seconds
Date
Msg-id 4B458FD0.8020205@postnewspapers.com.au
Whole thread Raw
In response to Re: pg_connect takes 3.0 seconds  (Dmitri Girski <mitek17@gmail.com>)
Responses Re: pg_connect takes 3.0 seconds  (Dave Crooke <dcrooke@gmail.com>)
List pgsql-performance
On 7/01/2010 10:44 AM, Dmitri Girski wrote:
> Hi everybody,
>
> Many thanks to everyone replied, I think we are on the right way.
> I've used tcpdump to generate the logs and there are a lot of dropped
> packets due to the bad checksum. Network guy is currently looking at the
> problem and most likely this is hardware issue.

Hang on a sec. You need to ignore bad checksums on *outbound* packets,
because many (most?) Ethernet drivers implement some level of TCP
offloading, and this will result in packet sniffers seeing invalid
checksums for transmitted packets - the checksums haven't been generated
by the NIC yet.

Unless you know for sure that your NIC doesn't do TSO, ignore bad
checksums on outbound packets from the local interface.

--
Craig Ringer

pgsql-performance by date:

Previous
From: Greg Smith
Date:
Subject: Re: Digesting explain analyze
Next
From: "Carlo Stonebanks"
Date:
Subject: Massive table (500M rows) update nightmare