From: Scott Marlowe <scott.marlowe@gmail.com>
To: Dmitri Girski <mitek17@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: pg_connect takes 3.0 seconds
Date: Wed, 6 Jan 2010 20:34:56 -0700
Message-ID: <dcc563d11001061934r1f220029v896ea63beae298e6@mail.gmail.com> (raw)
In-Reply-To: <daed64561001061844q528adafeke89b78adb868b15a@mail.gmail.com>
References: <daed64561001041812s602a3098l686f630d6448835f@mail.gmail.com>
<daed64561001061844q528adafeke89b78adb868b15a@mail.gmail.com>
On Wed, Jan 6, 2010 at 7:44 PM, Dmitri Girski <mitek17@gmail.com> 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.
95% of these problems are a bad NIC or a bad cable. Since cables are
easy to change I'd try those first, then NICs. Since lots of servers
have dual nics that's a pretty easy change too.
Every now and then it's a bad switch / router.
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: scott.marlowe@gmail.com, mitek17@gmail.com
Subject: Re: pg_connect takes 3.0 seconds
In-Reply-To: <dcc563d11001061934r1f220029v896ea63beae298e6@mail.gmail.com>
* 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